gtoolkit 3.10 overview

> On Feb 16, 2016, at 7:02 PM, Tudor Girba <[hidden email]> wrote:
>
> Hi,
>
> I promised to send a summary of the larger changes that came with the recent integration of GToolkit 3.10. Here it is:
> http://www.humane-assessment.com/blog/gtoolkit-3-10/
>
> Please let us know what you think.
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "What is more important: To be happy, or to make happy?"
>
>

> On Feb 17, 2016, at 2:14 PM, Damien Cassou <[hidden email]> wrote:
>
> Hi Tudor,
>
> Tudor Girba <[hidden email]> writes:
>
>> I promised to send a summary of the larger changes that came with the recent integration of GToolkit 3.10. Here it is:
>> http://www.humane-assessment.com/blog/gtoolkit-3-10/
>
> 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
> http://damiencassou.seasidehosting.st
>
> "Success is the ability to go from one failure to another without
> losing enthusiasm." --Winston Churchill

>
> Cheers,
> Doru
>
>
>> On Feb 17, 2016, at 2:14 PM, Damien Cassou <[hidden email]> wrote:
>>
>> Hi Tudor,
>>
>> Tudor Girba <[hidden email]> writes:
>>
>>> I promised to send a summary of the larger changes that came with the recent integration of GToolkit 3.10. Here it is:
>>> http://www.humane-assessment.com/blog/gtoolkit-3-10/
>> 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
>> http://damiencassou.seasidehosting.st
>>
>> "Success is the ability to go from one failure to another without
>> losing enthusiasm." --Winston Churchill
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Value is always contextual."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.list.inf.unibe.ch/listinfo/moose-dev
>