Hi sven

This is not the same. I do not need a menu or a button.

I took the class of the instance as an example.

Check deeply what I mentioned:

��� - you have text

��� - what can we do on text usually: edit, change and more important use it to query the system

��� hyperfast (and here suddenly we cannot we can select edit the text but not use shortcut to navigate no senders/imp/class).

This is a question of interface and the uniformity of the interface (this is like the grab icon in mac for file on the window).

In Pharo in any text pane of the tools we can query and this is an important property.

For example I can select a comment in the monticello pane and browse look for code - no need for Spotter.

The text is under my nose and I can get to the class instantaneously.

Now if the vision of Pharo is not to follow this tradition to immediate and superclose access to code, let me know

because this is an important (crucial) aspect for me and I used it all the time.

Stef

You can already do that: click the icon at the top right of the window 'Browse':

On 09 Aug 2016, at 19:23, stepharo <stepharo@free.fr> wrote:

Here is my scenario.

I have a field that contains aCZWhatever

the inspector shows me a list


field aCZWhatever

I can edit the aCZWhatever since I can click on it and get an input fiedl (or what I thought is an�input field).

I can select CZWhatever but I cannot do browse on it. So I have to use Spotter.


Stef