Eclipse and SWT

29 August, 2003

Despite my earlier protestations ([It] just confuses me with its perspectives and workspaces and completely idiosyncratic method of working with projects), I’ve persevered with Eclipse and it seems OK at the moment. I was mainly swayed by its CVS integration, which is good, and I’ve finally understood that Eclipse is only a project editor, not a text editor, which is how I’d been trying to use it before. In fact, its basic text editing is probably its weakest aspect. Eclipse is written for editing Java, so where’s the JSP support? Why is it so hard to find out which shortcuts keys are already mapped to? Little things like these are really putting me off, and need to get sorted. Yes I know it’s open source and all that bollocks, but if you think I’ve got time to wade through hundreds of thousands of lines of source to try and implement what someone else should be being paid to do then you’re very much mistaken.

Oh, and copy and paste is broken; both within Eclipse and with other applications. Very unimpressive.

In developing an SWT app I’ve needed to be able to bring up a webpage, and so far I’ve been using the method Eugene Bayley provided for launching the default browser. Today sees the release of Milestone 3 and with it a new SWT Browser widget (check out what the FAQ says about it and a code snippet).

Nice stuff. I like SWT. Initially it seemed a lot simpler to me than Swing, but I think that’s probably more to do with the very easy to read SWT tutorials I learnt it from, whereas I learnt Swing the hard way – using JBuilder and then seeing what code it generated. I’m not sure if one is actually better than the other, after all Swing provides a native look and feel too.

Nevertheless, SWT is currently my Java UI of choice. I’d prefer to be able to use Thinlet I think, and whilst I can knock up fairly complex UIs in little time using its ace XUL (thanks mainly to my experience playing with Leigh Dodds’ Foaf-a-matic mk 2 I can’t always quite get the functionality I need.

Using Thinlet though, has shown me how quick and easy it can be to use XML to define your UI. Sometime last week I set about searching for an XUL for SWT.

I found two possibilities JellySWT (there’s also a JellySwing for generating Swing interfaces) and Luxor. I haven’t evaluated either of them at all yet, but licensing seems relevant – Luxor is GPL whereas JellySWT is Apache License. Also, JellySWT runs out of Maven (which I’m sure is nice, but which failed my five minute test when I tried it eight months ago).

Overall I suspect I’ll try JellySWT, I think it looks the better of the two, but let me know if I’m barking up the wrong tree. 🙂

The main links I picked up whilst searching:

See other posts tagged with general and all posts made in August 2003.