Hi Alain, this sounds very interesting. I have never been a big fan of the current "Preference Browser". I am now trying to grasp (still learning here) how this new "Pharo Preference Mechanism" works. It would be great if the mechanism could be explained in detail in something like the new Pharo By Example manual :)
Alain Plantec wrote: > > I've joined 4 packages : > - PrefCore contains PreferenceValue which is now the only mandatory class. > > 2 packages for testing: > - PrefProvider contains PrefProvider class which declares some preferences > - PrefUser contains PrefChangeListener (try PrefChangeListener test). > > 1 package for UI: > - PrefTool contains PreferenceCollector and PreferenceDefinition. They > are optional. > -- View this message in context: http://n2.nabble.com/Preference-refactoring-again-tp2403814p2407403.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
