I just talked with Franck and we agree on trying to move most of those functionality to a toolbar⦠letâs hope this solves our small problem :) Esteban
On 03 Aug 2015, at 01:06, Stephan Eggermont <stephan@stack.nl> wrote:
On 01/08/15 13:25, Franck Warlouzet wrote:
Hello,
Yes it looks a little bit 'lite' but we did not want to have 2 buttons with the same look but two different kinds of actions. Hierarchy button changes the window itself and variable and scoped open a new menu or window.
I agree about the class side button.
Every button in the Nautilus browser has lots of improvement potential.
It should be visually clear where a button applies to. Scoped applies to the package pane, Variables to the class pane, Hierarchy/Flat to the class pane, Class side to the methods and methods category pane and comments to the text pane. The location of the buttons could reflect that.
It should be visually clear if a button represents a direct action, an indirect action, shows a menu, represents a state change action or the current state or opens a menu
The buttons should have hover texts explaining what the button does and when it is (and not) applicable.
A button should react to left-click only, not to right-click (or with a menu to right click).
And then there are also some Rubric widgets in the text pane that behave somewhat like buttons.
And now for something completely different: Why are the variables shown in reversed order? I rarely look for users of DependentFields
Stephan