SwingXBuilder FAQ
Today was the official end of coding for my Google Summer of Code project. For those who haven't been following my progress, here are the quick points you should know.
What is it?
SwingXBuilder is to Swing as SwingBuilder is to Swing. It provides a means to build a user interface using a hierarchical tree based structure.
Why did you make it?
It was sponspored by Google for the Google Summer of Code 2007. The official coding period ends on August 20, 2007.
Is there anything special I need to do to my user interfaces to port them from SwingBuilder to the SwingXBuilder?
For the most part no. All Swing components are available in SwingXBuilder. For the components that have SwingX versions, you will have to use the property classicSwing to use the Swing version.
Sounds cool. Where can I see some demos?
Edit: Demos no longer live. Links to them removed.
30Boxes Viewer Blog Entry (requires an api key and auth token from 30Boxes)
The full source is included in the Subversion tree.
What about documentation?
Check out http://groovy.codehaus.org/SwingXBuilder
Is it being used in production applications?
Yes. In July, I ported a Java console application for my 9-5 to Groovy using SwingXBuilder to make the interfaces.