The problem is also when you rename a class. Having explicit class name is a problem. Damien C we wwna to extract and revisit the configuration approach of pillar to offer a nice way to support configurations. Now it is based on Ston and it will make the approach based on a little package. So for now ignore error is the best way. Stef Le 12/3/15 20:29, Juraj Kubelka a écrit :

Hi,

If I export settings from Settings Browser in Moose 5.1 and then open Pharo 4.0 image, it raises an error "GTGenericStackDebugger not found in SystemDictionary”.

The problem is a setting: (Smalltalk at: #GTGenericStackDebugger) perform: #enableStackColoring: with: (true)

which apparently does not exists in Pharo 4.0.

I think if we want to share settings between images, it should ignore any setting that raise an error, right?

Thanks! Juraj