Its already that time of year again to start writing up all your great ideas for Java One Desktop talks for next year. Its only two and a half weeks till they close for submissions so hurry up. Click here for details for paper submission.
I am planning on submitting a talk on Nimbus and the new Nimbus Designer tool. Covering:
- Using Nimbus L&F in your applications
- Designing for cross-platform, how to design your application to look good on all platforms
- Customizing Nimbus
- Creating new look and feels using the designer tool based on Nimbus
- Creating your own components with Nimbus L&F themeing support
- Designing the look for your own components using the deisgner tool
Might have too much to cover in a hour, don’t want to scare you all off. Any thoughts on what topics you think are the most important/intresting in case I need to cut bits out or anything I didn’t mention here?
I am interested in a follow up to the spar talk you gave last year. Your had the insight that osgi plus jide docking is pretty much an rcp long before the current osgi frenzy.
I would have posted this on https://spar.dev.java.net/ but I guess that web site requires me to join the project first? I presume it is widely known within Sun that the current web site is really annoying?
Anyway, what are your current thoughts on the OSGi Swing approach? Please could you fix up the code so it compiles?
It seems like we have JSR296 for easy apps and we have NetBeans and Eclipse at the other extreme but there is a gap in the middle. I doubt NetBeans will ever support osgi and JSR277 is not going to ship for a while. Eclipse is always going to be SWT based. So I think there is a need for another way to architect big Swing apps.
I look forward to looking more at Nimbus but my biggest concern has always been how to architect complicated Swing apps. Every time a Swing book comes out it starts with ‘this is a JLabel’ and after 500 pages you get to ‘this is a JTable’. There is never any discussion on how to architect a 500+kloc app.