Le 17/2/16 15:04, Tudor Girba a écrit :
Indeed, the settings sending unknown messages is a problem, but that is a problem that is
not related to Spotter. If you get it with Spotter settings, you will get it with all
other settings as well. The settings mechanism should be more robust in my opinion.
it should probably be moved to use ston for serialisation.
> On Feb 17, 2016, at 2:14 PM, Damien Cassou <damien.cassou(a)inria.fr> wrote:
> Hi Tudor,
> Tudor Girba <tudor(a)tudorgirba.com> writes:
>> I promised to send a summary of the larger changes that came with the recent
integration of GToolkit 3.10. Here it is:
> thank you for the detailed changelog. Please pay attention to the
> Settings system. I have the impression that what you did might forbid
> you to remove any extension in the future. What I see happening is that:
> 1. people start deactivating some extensions through the Settings
> 2. they write their Settings in a file so the settings are available for
> all images
> 3. in this file, settings are deactivated with Smalltalk code that send
> setting-specific messages to specific objects
> 4. you decide to remove an extension and remove the corresponding
> setting method
> 5. the user downloads the new Pharo and gets an error because his
> setting file sends messages that are not understood anymore.
> Damien Cassou
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill
"Value is always contextual."
Moose-dev mailing list