Why you could not save the selector you should send to your components.... A layer on top does not imply that component should call you but after you can do what you want to represent load and save data. So your remark is wrong.
Stef >> It would be nice to redesign completely preferences. >> Did you read the thread >> Re: [Pharo-project] About Preference Flow >> of 4 of Feb ? >> >> Summary here >> >> Instead of having the current situation ie >> >> MyTool>>doSomething >> >> .... >> Preferences useNewDiffTool >> ifTrue: [kjlhkjhjkh ] >> ifFalse: [nkjhkjkjhkj] >> >> >> and not been able to remove the preferences (or that the >> preference is >> just a configuration layer). >> >> I would like to have the preference made that way >> >> MyTool class>>useNewDiff >> >> MyTool class>> useOldDiff >> >> **NO REFERENCE TO PREFERENCE IN THE METHOD FLOW!!!! >> >> >> Preferences useNewDiffTool >> MyTool useNewDiff > > One issue with this is that, from what I can tell, it does not > permit you to save preferences outside the image. I think it > would be really great if my preferences for Polymorph theme and > fonts and browser look and feel would be read from a standard > place and applied whenever I loaded up the latest Pharo image. I > don't see a way to have that and also make Preferences optional. > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
