+1 Please leave out the new inspector. Inspectors should be simple, and the explorer does a nice job of presenting a recursive tree; that's enough IMHO.
One inspector change I did like was a port to Dolphin of VW's (???) "diving inspector." Double clicking on items did not open a new inspector; it simply changed the model of the current inspector. There was a context menu item to inspect which *did* open a new inspector, so nothing was lost and most of the time, it did exactly what was intended.
________________________________________
From:
[hidden email] [
[hidden email]] On Behalf Of Marcus Denker [
[hidden email]]
Sent: Sunday, September 05, 2010 11:50 AM
To:
[hidden email]
Subject: Re: [Pharo-project] [update 1.1] #11412
On Sep 5, 2010, at 5:44 PM, Tudor Girba wrote:
> Sounds cool. Will there be a Pharo 1.1.1 release?
>
>
Yes, as soon as possible...
the idea is to first do a core with all the small things people found.
The idea here is to just collect what is fixed. Not fix more.
(there can always be a 1.1.2 later... no need to no do the next tiny thing)
Then do a 1.1 main image, here we can use the latest OB/RB from Lukas.
Another thing I think we should do it to not add the newInspector this time.
Marcus
--
Marcus Denker --
http://www.marcusdenker.deINRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
