Hi I think the idea of adapter classes for Swing model data would be somewhat useful, but most Swing programmers don't seem to bother to actually implement these interfaces themselves.
Visual consistency is a double edged sword. If things are obviously different, people live with it, but once you start down the road towards consistency, users will get pickier and pickier. I would rather we simply focussed on improving the Pivot L&F - for example, the default fonts are completely wrong on my desktop. -- Noel Greg Brown wrote: > Hi all, > > One of the things I have been focusing on for Pivot 2.0 is trying to make it > easier for Swing developers to transition to Pivot. For example, > DesktopApplicationContext now supports multiple (optionally modal) top-level > frame windows, and it is now much easier to use Pivot components within an > existing Swing application: > > http://svn.apache.org/repos/asf/pivot/trunk/examples/src/org/apache/pivot/examples/displays/ > > http://svn.apache.org/repos/asf/pivot/trunk/examples/src/org/apache/pivot/examples/swing/ > > Another idea I had was to create a "Pivot" L&F for Swing. This L&F would > mimic the appearance of the Terra theme, to help provide visual consistency > for applications that use both Pivot and Swing. I also thought it might be > useful to provide adapter classes for Swing model data (primarily ListModel, > TableModel,TreeModel, and SpinnerModel). These would allow developers to > begin using Pivot components without needing to rewrite all of their > application internals. > > What do you think? Would such features be useful to a Swing developer? Might > they help convince developers to consider moving applications from Swing to > Pivot? > > Thanks for your feedback, > Greg >
