2016-12-28 18:12 GMT+01:00 Ben Coman <btc@openinworld.com>:

* multiple code pane tabs - cool
* multi-selection is cool (but I need to trial how it works out in practice)
* automatic selection of items similar to last selection - I've been
meaning to ask this for Nautilus for a while.
* pinning modified pane code panes is a nice approach. It would be
nice to pin any pane.
* packages pane - it would be nice for the test-result-icon to appear
on left like the other panes. The folder icon would seem reasonable
place to substitute.

Nice feature to show variables in the protocol pane and references in
the method list pane.�� But it says "Class variables" while these are
"Instance Variables"

Because Class variables are also accessible from instance side and you want to see what methods are used it.

But I agree it should not be here by default. Actually it will be not here if Object will not define any class variable. But Object has DependantFields. Browser probably should ignore it.

Now structure of variables view is the same as when you click on Variables button in Nautilus.

So you think existence of "Class variables" is also confusing because it looks like parent group for instance variables?

��

Now I wonder if we can do without the Methods/Vars buttons by having
the following top level tree items. Also as a newbie before developing
the instinct to *know* which instance/class-side I was on, I got burnt
a few times following tutorials accidentally putting methods on the
wrong side.�� It would be interesting to try deprecating the
Inst-Side/Class-Side buttons, and have something like the following
items...
+ instance-side methods
�� - accessing
�� - initialization
�� - extensions
�� - GT-InspectorExtensions
+ class-side methods
�� - instance creation
�� - extensions
+ variables
�� - instance variables
�� - class variables
�� - class instance variables

It could be good or not.

Problem with this approach is same as why we use 4-column panes instead of single tree menu for everything like other IDE does.

We don't want to scroll to achieve some group element.��

Imaging that you browse some morph subclass which have a lot of protocols. You are in some middle protocol and not see parent expanded group in list. And now you want to look at class side or variables. Tree view will force you to scroll instead of simple press on switch button like it is now.

��

The "inherited methods" tree-item might be better as a pull down menu
at the bottom of the pane, level with "Filter..." since visually it is
confusing seeming that protocols like "accessing" are a sub-item of
"inherited methods".

But it is not expanded and indentation of both items are same.��

Also you can select "inherited methods" as any other group and see all inherited methods together without using visibility checkbox.