So, it doesn't save you from the complexity of the LayoutManagers (which, with some moderate experience, are not THAT complex).
It requires an external file that is not checked at compile time
It requires you to learn not only the methods and interface of the Java classes for the Swing components, but the XML attributes of the same. Now I have to know TWO APIs when reading code.
The code to implement the examples would be far simpler than the XML crud required by this tool. I can't believe anyone would PREFER to have their code spread out all over the place. What is the obsession with removing things from code. are .java files in such short supply that we must remove as many things from them as possible? Is the step of compiling so hallowed and precious that it must not be done unless absolutely necessary? |
java.net RSS Feeds
