On Aug 27, 2009, at 3:13 PM, Lukas Renggli wrote: >> - A setting with value is an instance of SettingValue or of one of >> its >> subclasses. Such a setting holds a useful global system parameter and >> is made persistent: it is stored in a class variable which is >> initialized by the method that declares the setting. > > I think the problem with this proposal is that it mixes the model (the > value of the setting) and the meta-model (the model of the setting).
can you show me where? because alain payed attention that we do not have the dependency with > This is problematic because then all code depends on the settings > package and when reading/writing settings application code must be > aware of the indirection introduced through the setting. I see. Let us reply alain and we talk about that at ESUG satruday or sunday. > Why isn't a setting simply a variable local to the package, and the > setting-description a separate object (method) that can also be > packaged separately? it is. Normally alain is transforming all preferences into class variable of the package then I imagine that we should describe the setting so that a browser can browse and change the value of the setting. The flow should be local to the class and not going via a global like Preference. So probably the setting description should be class extension. But there is something I should understand deeper. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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
