Stef, I had an open mind about it at first, but after having to retreat to an older image for a while and then seeing it again, (I respect you guys too much to soften this) I want no part of it (though I will look at improvements you want us to try).
The choice of a simple inspector and the explorer is hard to beat - I can easily toggle between them with a right click. Anything that tries to do a shotgun wedding of the two ideas is a loser IMHO. I do some expensive computation, and I use a fair amount of lazy initialization, network proxies, etc. to soften the blow. There are times when the explorer is an expensive way to go. The new inspector will likely suffer the same problem, and I find it a serious step backward from explorer. The new inspector reminds me of something I wrote for browsing Dolphin code, IIRC at a package level. It was helpful, but not all that much, so I would use it only when I _really_ got lost. The mission was different, but I suspect the fate of the new inspector would be the same - I might use at times if it were offered by say control-shift-i vs. control-i for the regular inspector, but I prefer the existing tools. Just my 2 asCents. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stéphane Ducasse Sent: Wednesday, October 21, 2009 8:55 AM To: Pharo Development Subject: [Pharo-project] feedback about the "new inspector" Hi guys we tried to use and force you to use the new inspector and it does not fly that well. I'm sure that frederick is open to suggestion so please send your remarks. Here were mine :) Stef Hello Stef, here what is really strange and annoying is that we cannot see the collection elements in the right pane Now it is fixed. on the left Elements is confusing. because this is not clear the relationship with array, firstInd.... It shows only elements of any kind of collection (it is simply a collect: [:o | o] on the collection). on the right this is also frustrating that we cannot modify, touch the elements. Ok... but you can expand the Elements, select the element you want to change, put the new value in the description pane and accept it. I'm not sure that we want to see the class (in an expandable manner). For the methods may be you want to stop and show the methods but expandabel may be by defualt you should not show the class and methods as expandable and have a menu entry doing that (expand) I'm not sure to understand what you want. For me the NewInspector it is a like an infinite inspector: if you want to go into an object, you can. So if you want to inspect a class or the methods, you should have the possibility to do it. Fréd _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
