> > Hehe. I've already done that twice now: > > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-March/006202.html > > prefTheme > <preference category: 'User Interface'> > ^ MASingleOptionDescription new > options: #( 'Vistary' 'Watery' 'Squeak' 'Soft Squeak' ); > reference: MAStringDescription new; > autoAccessor: 'theme'; > label: 'Theme'; > priority: 40; > beSorted; > yourself > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ >
What happened to trying to slim down the image? Do we really want to introduce a dependency on a large external library or gasp, include it in the core, just for managing preferences? I'd much rather see something simpler done with pragmas. Just because Magritte can be used for something doesn't mean it should. Just because Magritte is a meta model also doesn't invalidate all future uses of other meta models. If preferences ends up doing something like a small Magritte lite that looks kinda similar in some respects, it doesn't mean it was wrong to not use Magritte. Ramon Leon http://onsmalltalk.com
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
