This post originated from an RSS feed registered with Java Buzz
by Scott Delap.
Original Post: SWT Happens: A Look at SWT vs Swing
Feed Title: ClientJava.com
Feed URL: http://www.clientjava.com/archives/wireless_mobile.rdf
Feed Description: Client/Desktop Related Java Development
HackNot has a very lengthy well written piece on a programmer's experiences using SWT after previous experience with Swing. I'm sure the proponents on each side of the Swing/SWT debate can find issues with the comments made. The article is full of links to other resources as well as quotes such as the following in regard to SWT:
If you stop to think about it, we support 5 different operating systems using totally different code bases and somehow knit together and implement a portable API to all of them and we do this for free. It's a full time job, 24-7
While the article is pro Swing overall, I think it raises many valid questions to be considered when comparing SWT and Swing.
SWT Happens I have been working with Swing intermittently for the last seven years, and with SWT exclusively for the last four months. Under the terms of a new contract, I was required to use SWT to implement the client to a J2EE price tracking system for a major retailer. Before applying for the role, I was told that the organization had already decided that the client would be implemented in Java, and to use SWT instead of Swing. Since my very first contact with the organisation I have been trying to discover the origin of that decision, and the reasoning behind it. To date, I have been unable to discover any rational reason for choosing SWT over its obvious competitor, Swing...
Previous Topic
