On Tue, Mar 03, 2009 at 06:58:26PM +0100, Alexandre Bergel wrote:
This will probably work and seems reasonable in a general context. However, for our situation, I feel these are on different levels. Preferences should be defined and taken into account in Pharo-core, meaning without Magritte.
Hmm. I'd think pharo-core would not have preferences. I was just suggesting it; it seems that once you implement enough to have generic boolean, string, or enumerable preferences, you basically have a watered-down magritte anyway. And who's to say we won't want a generic timezone, email address, or url preference in the future? Magritte can do those without having to rewrite string parsing/verification into every class. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/