gtoolkit 3.10 overview

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

gtoolkit 3.10 overview

Tudor Girba-2
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?"


Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] gtoolkit 3.10 overview

Damien Cassou-2
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

Reply | Threaded
Open this post in threaded view
|

Re: gtoolkit 3.10 overview

abergel
In reply to this post by Tudor Girba-2
Pretty cool!

Alexandre


> 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?"
>
>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] gtoolkit 3.10 overview

Tudor Girba-2
In reply to this post by Damien Cassou-2
Hi,

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.

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."