How is SwiXmL different from all the tens of other XML based GUI markup languages in Javaland?
Here's a list:
http://java-source.net/open-source/xml-user-interface-toolkits
The situation with these things is just as bad as with Java Webframeworks... new ones keep popping up right and left, but none brings any interesting features.
With SwiXml, I don't see any benefit, actually I think it's even worse off than some others, as it seems very specific to Swing (hence the name?) and I don't see anything interesting done with the layout.
As for GUI designers (the person, not the tool) working with the XML language is better than some GUI builder (the tool) for prototyping and polishing the design?
Sure... except that the designer has to learn the XML dialect and semantics of this particular language... then stumble over some problems, then search for non-existant documentation (many of these toolkits are half dead or badly documented), etc etc, and finally ends up spending
twice as much time fiddling with this than she would have handcoding the GUI, blindfolded with one hand tied behind their back...
I'm all for making GUI building easier, and decoupling logic from view is good practice... but XML GUI definition languages just add a problem, and don't offer a solution... yet? |
java.net RSS Feeds
