Wayne Beaton's blog

Wayne Beaton's picture

Integrating Firefox with RCP

I was asked a question today about whether or not Eclipse RCP can integrate with Firefox. The short answer is “yes”. The longer answer is “what do you mean by ‘integrate’?”.

Read More
Wayne Beaton's picture

Who is using SWT?

If you’re using RCP or even Eclipse itself, you’re using SWT. So… who’s using SWT? Lots of folks are. Ian Skerrett gave some examples of folks using RCP (and SWT by extension) in an blog entry several months back.

Read More
Wayne Beaton's picture

Extending RCP beyond the desktop

I guess that the name “Rich Client Platform” should be a tip-off that applications built using RCP technology can extend beyond the desktop. Essentially… if you have a client, it seems that you should probably also have a server.

Read More
Wayne Beaton's picture

SWT samples and documentation

Check out the SWT site for some screen shots of many of the widgets included with SWT. Be sure to take a look at the snippets page for help on using ’em.

Read More
Wayne Beaton's picture

Scavenging, borrowing, and blatantly copying code

In my previous posting, I suggested that “scavenging, borrowing, and blatantly copy code” is the staple of modern software development; this is, of course, true. However, there are caveats to consider, both legal and technical.

Read More
Wayne Beaton's picture

Time isn’t free

In response to my Friday posting, RefuX said “Linux is cheap if your time is free”. This statement is, of course, absolutely correct. However a similar statement about the cost of your time can be made about operating systems that you have to pay for.

Read More
Wayne Beaton's picture

Eclipse in 64 bits

I’ve been given this pretty cool Linux desktop system to play with. It wasn’t until I started to download Eclipse 3.1 that I realized it was a 64 bit installation (the Eclipse download page detects the operating system). Cool, I thought. The system even came with a Java Runtime Environment (JRE) installed, so I was good to go. Or so I thought.

Read More