I'm working on something that I think is very similar to what
you are describing- check out:

	http://www.canis.uiuc.edu/~tyrrell/Squeak/Personal/UI

This is a series of screenshots from an early version of my system.


> I feel the same problem as you.
> I want to navigate easily and quickly and I can't.
> 
> I've been developing a dynamic context menu for browsers.
> Where the context depends on the kind of browser and the "kind" of selected
> object.
> In hierarchy browsers, the method and class panes have a fix contextual
> menu; they are ok. But I want a similar behavior in the text part.
> In a text pane, the kind of selected objects could be a method, a class,
> etc.
> The different occurrences of text panes are in inspectors, workspaces and
> hierarchy browsers. In each of them you want some special behavior on the
> selected objects.
> 
> For example, in the text pane of a hierarchy browser, if you paint (select)
> a word that the user knows is a selector, a popup could let you copy,
> paste, see its implementors, senders; I mean things related with the method
> on that area.
> In the same way, painting an object or a class, you open a popup, it could
> let you scan the references of the class, you can browse it in a new
> window, you can see what messages the class define, you can see the
> different versions of a class (if you are using ENVY for example).
> Painting an object in an inspector, the options presented in a menu could
> be scan its referenced objects, browse its class.
> The idea is to interpret the objects hidden in the text. To release the
> user from the responsibility of knowing what kind of things he could do
> with the object. Showing objects allows to reflect the selected object
> behavior in the context of the workbench that you are using.
> 
> I didn?t implemented it in Squeak, I don?t have much time to do it. If
> someone is interested in implementing it in Squeak, I?m willing to help.
> 
> best regards,
> 
> Francisco