Simply Sweet Components slides
June 7, 2009
Here are the slides for my JavaOne 2009 presentation, Simply Sweet Components, TS-4559 (read the abstract). Enjoy!
 |
Keynote version (the format I authored the presentation in) |
 |
QuickTime version (with full animations) |
 |
PDF version (with notes, but no animations) |
To get the most out of the presentation, I’d recommend clicking through the QuickTime version (the one with the animations), with the PDF version up on the side (which has the notes).
Exploding Pixels 
June 8, 2009 at 11:52 am
Thank you for sharing this.
A video of this presentation would have been great…
June 8, 2009 at 12:05 pm
Hi Pepe,
Sun will release the audio of the presentation eventually.
-Ken
June 8, 2009 at 5:07 pm
Nice presentation. Very informative. Any idea on when the next version of the library is released?
cheers
June 8, 2009 at 11:54 pm
Thanks Amar. I was shooting to release 0.9.5 around JavaOne, but that didn’t happen — probably within the next month.
-Ken
June 9, 2009 at 5:47 am
Thanks Ken. Will this new version include all of the enhancements mentioned in the issues? I want to get the approval from my team to use this library in a product that we want to redesign and providing the enhancements would strengthen my hand.
cheers
Amar
June 8, 2009 at 6:02 pm
Saw the presentation live at JavaOne, nice job, was really good I thought.
June 8, 2009 at 11:55 pm
Thanks Keilly!
June 9, 2009 at 8:45 am
Very nice presentation, exactly what I came up with making lots of custom swing components for a long time.
Say my hello to Dima Skavish :)
June 9, 2009 at 9:45 am
Thanks Kirill K.!
June 9, 2009 at 9:43 am
Hi Amar,
I’m not sure which issues that are still open will get fixed for 0.9.5 — you can email me your most pressing issues.
-Ken
June 9, 2009 at 4:17 pm
Interesting presentation. I guess I’m so used to the hundreds of methods that I wasn’t phased by their presence. But you make a compelling point; I’ll be more mindful of this in the future.
On the other hand, a lot of the time I end up writing “hackish” fixes for bugs/issues, and I end up overriding or using obscure methods that a cleaner API wouldn’t make available. (You could argue these fixes shouldn’t be necessary in the first place, though.)
June 9, 2009 at 5:32 pm
Hey Jeremy,
You guessed it — if there are methods exposed that you’re overriding to work-around an issue, that means there is a fundamental flaw in the design.
When an API is developed internally, it’s relatively easy to find the author and talk about your needs as an API consumer. I certainly understand, though, that this communication becomes very difficult when the issues needing work-arounds are in external APIs.
-Ken
June 9, 2009 at 6:40 pm
Awesome post! I am sick of making custom Swing components too. Thanks a bunch for sharing your work with these APIs. I will surely be using them a lot more in the upcoming months.
June 9, 2009 at 6:55 pm
Thanks Matt! Hopefully other developers will see the light!
June 15, 2009 at 2:20 pm
Great post, very actual.
May I propose another way of ‘injecting’ functionality to components: The visitor pattern.
If each component implements a visitor access, then we can add functionality by creating new visitors: e.g. IconVisitor, ColorVisitor, …
July 16, 2009 at 10:11 pm
[…] of the people I met at JavaOne, Ken Orr has just posted the slides to his ‘Simply Sweet Components’ presentation. Definitely well worth checking […]