2013/8/28 Damien Cassou <damien.cassou@gmail.com>:
On Wed, Aug 28, 2013 at 12:29 AM, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
Is there a way I can browse the whole class hierarchy in the SystemBrowser? I mean, a big tree with Object (or ProtoObject as its root) without having to filter branches it by categories.
why are you using the SystemBrowser? Which version of Pharo are you using?
I click in the world morph, and the menu says "System Browser". It open Nautilus though. The version is: Pharo2.0 of 7 March 2013 update 20600
in Nautilus, browse to the Object class, and click "hierarchy".
It does what I want. I mean, I can see the whole hierarchy. But isn't this procedure more like a workaround? I mean... 1. Find Class 2. Type Object 3. Click Hierarchy And that wouldn't be too bad, but... 4. ...as soon as I click in another class name (outside of the Kernel-Objects category, grayed) it takes A LOT(*) to switch to the selected class. (*) In terms of responsiveness, compared to switching to another class in the same category which is slick.
I have two groups of categories (one starting with T and the other one with G) and the names are too separated in the list. Clicking back and forth is a real hassle.
In Nautilus, you have two options: - to get 1 browser for T* and 1 for G*: select all packages starting with T, right click, and select "browse scoped". Do the same with packages starting with G
- to get 1 browser for both T* and G*: select all packages starting with T, right click, "Add in group...", "create group", give it a name. Select all packages starting with G, right click, "Add in group...", select the group you created.
The groups options is the closest I found to what I wanted. Thank you! It needs maintenance though, everytime I add a class It must be added to the group. Am I asking for something too esoteric? I worked long time with other Smalltalk dialects and it takes a while to get used to each one ergonomy and tools, but the class browser/system browser is, usually, the most straightforward tool in the environment. Does exist a "best practices" guide for Pharo? Thank you again!