I haven't used this new inspector much, but so far I'm not thrilled either.
As a concrete example, do "Undeclared inspect". In the old dictionary inspector I get all the keys in the left pane and the selected key's value in the right pane. It is simple but it provides the info I need. In the new inspector there is too much stuff that I don't care about, like class and methods. Why would I want to look at the class Dictionary or at the bytecodes of a method of this class? Sometimes I do, but in this case I know how to get there in other ways. Btw, what I don't understand is why the keys of the dictionary are all displayed in square brackets. It somehow suggests that these are blocks, but they are plain symbols. Also I miss menu items. For instance, in the old dictionary inspector there is a menu item "reference" that you get by right clicking on a key. In the example of inspecting the undeclared dictionary, this item is key to find where the undeclared bindings come from. Also I miss the menu item "Chase pointers". Hence, as an improvement I suggest to remove all Class and Methods entries in the trees and check the lost menu items. Cheers, Adrian On Oct 21, 2009, at 15:54 , Stéphane Ducasse wrote: > 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
