Swing Frameworks: Catch the Wave
"Open Source Convention". Isn't that a bit like "Anarchy Government"? Or "Military Intelligence"? Or "Personable Programmer"?
I've never spoken at an open source conference before. I wasn't sure what the
protocol was. Was I just supposed to propose an abstract and
then people in the audience would fill in the content? Or maybe I
was just supposed to talk with the audience about what the presentation
should be like eventually, and then set up a mailing list and a source code
repository for the future slides that we might create.
Or we could spend the hour debating the license of the presentation, and some of
the audience could walk out in protest.
As it was, I decided to go ahead write and deliver the content.
Maybe I can collaborate with the community on version 2.0 of the
presentation next time around.
My favorite part of the presentation was the Motivation slide, where I tried to
describe why these frameworks are so awesome for Swing developers. But don't
developers already find Swing programs easy enough to develop? Isn't
Swing development like a day at the beach?
A Day at the Beach
Beans Binding and the Application Framework will make Swing
development much easier. From the application-lifecycle capabilities that the
Application Framework offers, to Beans Binding's ability to
automatically connect an application's GUI with the data that drives it, to
seamless integration of these libraries with the IDE in NetBeans 6, Swing developers should have a
much easier time of it.
Swing frameworks: Catch the wave.