Always be careful when you ask for something to be pulled into core. Any API, even something as simple as Painters, becomes frozen the minute it is added to core. Any core api must be 100% backward compatible, must not break any existing code, and can only be updated on the release schedule of the JDK. (which is something like every 2 years at this point). All just so you don't have to add a tiny jar to your app. Most of the things people ask to add to core would be better done as libraries. This includes most of the swing extensions. You are correct that Painters are a tiny bit of API, which is all the more reason to just add it to your app as a separate jar. You don't need to add all of SwingX, just the parts you need.
- Josh On Nov 25, 2008, at 12:10 PM, mikaelgrev wrote: > > >> Two years later I still think it was the right choice. We now have >> better ways of doing the things we were trying to accomplish; with >> projects like the Nimbus L&F, JavaFX, and the JXLayeredPane. > > I you use one of those things, that is... Which is how many percent of > the developers? 5? > > I don't mean to be rude, but there is a big difference if 5% gets the > chance to use it or if 95% get the chance as would've been the case > with Swing. Sun engineers always wants us to add this and that to our > projects so solve some simple thing but don't seem to understand that > all those jars really add up to the download. I would never dream of > adding swingx.jar just to get JXLayeredPane, to get painters, for > instance. Painters is a 1k thing and you shouldn't have to add more > than that to get it. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
