Ok, I'll start to move Preferences and PreferencesTest classes to demos, in package pivot.demos.preferences .
But at this point, this demo has lower priority (maybe for 1.3) than my other tasks on Pivot, right ? Because I'm thinking to implement a Demo like a TODO List handling, and if i get my first version, why not use the double backend strategy (File System or Web Start Persistence), so depending on the execution type any user can try different ways to save/load preferences ... ok ? In Eclipse demos project, I've defined an eclipse variable JAVAWS_LIB (or JAVA_WEBSTART_LIB or other ...) that points to javaws.jar , and a PLUGIN_LIB variable (or JAVA_PLUGIN_LIB or other ...) that points to plugin.jar , so any eclipse developer need only to define in its environment. What do you think on add these build path modifications also on Demos standard project file on subversion ? Bye, Sandro
