Stéphane Ducasse a écrit : >>> I don't want an extra package just with the settings for every package >>> >> I write. Also I don't want to have unreferenced classes in any of my >> packages. >> > > But how can you then remove setting preference from your package? > Magic? but so far I do not see how. > > Package 1 > my app + class var for preferences (but no reference to > preferences) > > Package 1-Pref > reference to setting > > so that I can remove Package1-pref when we remove preferences. > This is exactly what I would like to do for the migration from old preferences to the new setting framework in the core. But, as far as I understand, Lukas does'nt want to be constrained to introduce a "Package 1-Pref" package. This is why he prefers the builder pattern. Then, only at the price of one argument, even if setting declarations are implemented in "Package 1", no class dependency is introduced. I still prefer the 2 packages solution, even with the builder pattern because I think it is better to be able to remove all setting declaration methods and eventually some class variable if the setting package is removed. But ok, let's go for this refactoring ! :) Cheers Alain
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
