Hi,On Mon, Sep 15, 2014 at 11:27 AM, Thierry Goubier <thierry.goubier@gmail.com> wrote:Hi,I'm accustomed to the smart suggestion stuff as I implemented it, makes it very easy to drill down in code...What I use a lot:
Right mouse button on a global, select 'Browse' : inspect the class variable or open a browser on the class (depending on what it is). Also valid in a class #subclass: display in the browser, to browse the super class.Implementors / sendors of / accesses to instance var under right mouse button: open a full browser showing all the resulting methods (and not a message list :( ). Also works in the string containing instance variable names in a class definition pane.Double click on a package / class -> open a browser scoped to that package / class (where all search operations are limited to that scope).Ctrl+F -> open the finder toolbar on top of the browser, with reduced gui (no package choice) : result of the finder will appear in a new browser, and finder is scoped by the initial browser scope.So, when I end up in Nautilus, I just find myself very clumsy looking around (which is not good for my self-esteem ;) ) Not forgetting the fact that opening a Nautilus browser takes a lot longer.Are you comparing with the AltBrowser?
�In Moose also, GTInspector is slow.What is slow?
�Take it as a different experience on the GUI side; I know I invest a lot in the motor skill part of the GUI, and this has an effect when I switch platform.It seems to me that you are not comparing the Moose image with the Pharo image, right? What are you comparing with? Can I look at these changes?
Cheers,Doru�Thierry�--"Every thing has its own flow"