Skip to main content

Swing needs to be

faster
52% (418 votes)
better looking
33% (265 votes)
something else
9% (73 votes)
just what it is
5% (41 votes)
Total votes: 797

Comments

Swing

For me there are three major points that need to be adressed in Swing: 1. Design flaws: Even for a seasoned Swing developer there are far to many flaws in the API, just to mention one: when using a JList always use the DefaultListModel do not use setListData, if you do you're screwed. Similar problems for JTable, JComboBox,... In order to do the "right" thing you really have to dig into the source code of these classes. This should not ne necessary. Another thing I never understood is why one needs to implement all this custom drawing code when putting custom objects in a JTree or JTable. These classes should be able to handle the drawing of these objects without custom drawing code since that's already implemented in these custom objects. 2. Speed. No comments needed her I guess. 3. Far more frequent updates to the Swing library. In essence it still the same old code dating back 4 years ago. If Sun would have put the same effort in Swing as in, for example, XML support, this toolkit would be out of this world by now.

Look and Feel

Does anyone ever think that when Sun talk of "Look and Feel" that they're really just talking about "Look"? I often get frustrated with Swing GUIs (in addition to the points mentioned above) by the fact that often the usual shortcut keys and so on don't work by default. This isn't something VB developers have to concern themselves with. Another point is that often Swing is lauded by its designers for being extremely flexible. I would ask whether or not this is a good thing. I'm not convinced that it is. The toolkit should make it illegal to build bad user interfaces (or at least some higher-level facade to the toolkit); it shouldn't allow you to build complicated, non-standard GUIs. The other major point is that other than speed, none of this stuff has got significantly better in the last 5 years! I'm glad SWT is around; if for nothing else than to give the guys at Sun something to think about.. They need to get their act together on the GUI.

Less bugs, more features

Isn't it fast enough these days, JVM start up time aside? Metal Ocean looks alright to me, and the Windows PL&F is, I'm told, quite reasonable these days. Other than the notable performance and PL&F implementation improvements, Swing does seem somewhat abandoned. One thing you can guarantee will happen when you start writting some Swing code is that you'll come across bugs. New features since the initial release are sparse. SpringLayout is pretty much useless. Even the first Swing Tutorial SpringLayout trivial example is wonky. HTML is still a poor implementation handling a stone age version. I'm told RTF support is likewise. JFormattedTextField appears to just wipe its contents if the user typoed - that's user friendly. We're still lacking widgets for friendly formatted data (although document filters help), tree tables, etc. Perhaps it's not surprising given where the users of Java are. At aguess a weblog about Swing will get a third the hits o

Less bugs, more features

Speed is a lot better - but no it's still not fast enough for most people.... and Metal Ocean still makes apps using it look like crap.

Less bugs, more features.

Isn't it fast enough these days, JVM start up time aside? Metal Ocean looks alright to me, and the Windows PL&F is, I'm told, quite reasonable these days. Other than the notable performance and PL&F implementation improvements, Swing does seem somewhat abandoned. One thing you can guarantee will happen when you start writing some Swing code is that you'll come across bugs. New features since the initial release are sparse. SpringLayout is pretty much useless. Even the first Swing Tutorial SpringLayout trivial example is wonky. HTML is still a poor implementation handling a stone age version. I'm told RTF support is likewise. JFormattedTextField appears to just wipe its contents if the user typoed - that's user friendly. We're still lacking widgets for friendly formatted data (although document filters help), tree tables, etc. Perhaps it's not surprising given where the users of Java are. At a guess, a weblog about Swing will get a third the hits of a similar weblog on some trendy aspect of J2EE.

Metal sucks

Looks in general isn't really a big issue because of changable look and feel, but Sun has to figure out that Metal and any derivative of their metal feel - makes any Java app look like a cheap piece of crap. (Rave might be a cool name, but when most developers take a look at the actual app - most of them will be wondering why in the world Sun's IDE looks like total garbage compared to 99.9% of the other Java IDEs.) Then again I'm not surprised considering this is the same company that came up with CDE. Hopefully speed will be improved in 1.5 because of JOGL....

none of the above

My vote would be for "Easier to use".