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?"
Hi Tudor,
Thanks for the detailed article. I don't use Spotter (yet) but for the GTDebugger I want to say that buttons in the right upper corner makes me feel uncomfortable... in part because I am very used to buttons at the middle, and part because debugger operations are central to the debugger and should be bigger or more visible. Is this button bar fixed in GTDebugger? Can be changed with preference?
Hernán
2016-02-16 19:02 GMT-03:00 Tudor Girba tudor@tudorgirba.com:
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?"
Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Hi Tudor,
Tudor Girba tudor@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: 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.
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 damien.cassou@inria.fr wrote:
Hi Tudor,
Tudor Girba tudor@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: 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:
people start deactivating some extensions through the Settings
they write their Settings in a file so the settings are available for
all images
- in this file, settings are deactivated with Smalltalk code that send
setting-specific messages to specific objects
- you decide to remove an extension and remove the corresponding
setting method
- 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."
Le 17/2/16 15:04, Tudor Girba a écrit :
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.
it should probably be moved to use ston for serialisation.
Cheers, Doru
On Feb 17, 2016, at 2:14 PM, Damien Cassou damien.cassou@inria.fr wrote:
Hi Tudor,
Tudor Girba tudor@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: 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:
people start deactivating some extensions through the Settings
they write their Settings in a file so the settings are available for
all images
- in this file, settings are deactivated with Smalltalk code that send
setting-specific messages to specific objects
- you decide to remove an extension and remove the corresponding
setting method
- 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 Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
Pretty cool!
Alexandre
On Feb 16, 2016, at 7:02 PM, Tudor Girba tudor@tudorgirba.com 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 -
Damien Cassou -
Hernán Morales Durand -
stepharo -
Tudor Girba