XML dialects for user interface (specially for Swing user intefaces) are not new. And it's not fair to compare them to Web MVC frameworks. Those frameworks add a lot of code by themselves and ease a web developer life, while XML GUI dialects for Swing just add a different syntax for working with Swing components and layours. You won't write less code, you won't have new features (like Struts declarative validators) , you get just a more manageable code that does the same things the same way.
What I cant't underst is why Java has yet so poor support for those. He have years of experience with Gnome, whete libglade XML are the preferred ways to develop GUIs, with support from the official GUI builder, Glade.
a Swing XML dialect is so simple that there's no reason there shouldn't be a standard dialect defined by a JSR and the run-time support as part of standard JavaSE. And this standard should be the prefered way to work with visual GUI builders from any IDE.
The lack of those (standard XML dialect, implemented as part of Java SE and supported by all major IDEs) is a sad sign that sometimes the JCP donesn't serve the Java user and developer community interests, but the tool vendor interest. They have nothing to gains from that kind of standard, which would make it easy to migrate from an IDE to another. |
java.net RSS Feeds
