>> 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.
indeed. But I do not see how the magritte description** pattern would work for preferences. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
