That's the occasion for me to post the content of my talk on "JSR-296 Swing AppFramework from the trenches".
The full content (in PPT format) is here (I have just removed the Jazoon template stuff). If you don't have PowerPoint, here is a PDF version (unfortunately without the original animations). Unfortunately I could find no way to convert it to ODP format (for OpenOffice users) without big losses in animations but also in diagrams (most of them got terribly ugly after conversion). I am afraid I'll have to give up on that one (if anyone can convert the original PPT to ODP please email me the result and I'll post it here).
If you want to have an idea of the content before download, here is the agenda:
- Introduction
- why do we need a Swing framework
- what is JSR-296? what does it bring (in a nutshell)?
- about the presented applications
- Application Lifecycle
- standard application lifecycle
- adding dependency injection (Spring, Hivemind, Guice)
- adding docking capability (MyDoggy)
- tips & pitfalls
- Resources & I18N
- resource injection principles
- what about JTable?
- tips & pitfalls
- Actions & Tasks
- a better, more responsive, javax.swing.Action
- where should I put my @Action?
- when should I use a Task?
- what about Exception handling?
- tips & pitfalls
- Persistent Session State
- state restoration (or users' happiness)
- what is stored? what is not? where?
- tips & pitfalls
- What is missing for a complete GUI framework?
- GUI framework architecture
- Example: EL4J Swing stack
- Future
- JSR-296 standpoint
- what's likely to change?
Still, I believe that Swing is a better platform for GUI development than many others (not just talking about Java here), and developers will still use it for a couple of years more (maybe not in pure Java, though, other options exist: Groovy, Scala). Wait and see...
Enjoy!
Posts
