This post originated from an RSS feed registered with Java Buzz
by Scott Delap.
Original Post: Do we need another UI framework?
Feed Title: ClientJava.com
Feed URL: http://www.clientjava.com/archives/wireless_mobile.rdf
Feed Description: Client/Desktop Related Java Development
Do we need another UI framework? ...The only area, where Java positions are weak, is desktop application development. It is hard to decline this as I do not know of many desktop applications written in Java, except tools for Java developers. ..Usual Swing and SWT discussions point me to the answer: developers and customers experience problems with these frameworks.
In my opinion this piece does not make a convincing argument. It raises a number of points that are open for debate. Speed is mentioned as a key factor with Swing. I would be curious to see what the speed differences were in terms of raw numbers compared to native OS actions. I'm also not sure that building a new framework on top of SWT solves major problems. Tweaking the OO structure of interacting with SWT is fine. However, this isn't going to completely solve the subclassing issue that is mentioned for instance. If your framework is build on SWT, then it is ultimately going to be the lowest common denominator.