Thanks for raising this issue up. Indeed, we should find a solution here. Does anyone have any thoughts about this? Doru On Wed, Nov 27, 2013 at 12:09 PM, Torsten Bergmann <astares@gmx.de> wrote:
In Pharo 3.0 there is a new class "ConfigurationOf" which I can subclass for my configurations.
But then my config is not loadable in Pharo 2.0.
The problem is that when people migrate the configs often are adopted for Pharo30 and still work for Pharo20.
So one can use this new shiny common superclass only for new Pharo 3.0 configs onwards or is there a backport planned ...
Also the "+Config" button in the MetacelloBrowser of Pharo 3.0 does not use this new ConfigurationOf class. It still generates code
Object subclass: #ConfigurationOfFoo
instead of
ConfigurationOf subclass: #ConfigurationOfFoo
Bug or by intention?
Bye T.
-- www.tudorgirba.com "Every thing has its own flow"