I would like to still be careful about those contextual actions and not mix the global with the contextual ones.
I know.
But common sense is to have all possible actions in a tool with a visible representation (in toolbars, menus, others). Functionality accessible *just* through the contextual menus are not good (and you will see no serious GUI design guidelines recommend it… quite the oposite).
One example: I made a configurations browser replacement. It shows all packages in a list, with tags for filtering and another pane to show descriptions (btw… a readonly text panel also would be ok)…
Now, by selecting a configuration and right clicking, you can install it.
This is plain wrong.
Why?
Because the main purpose of such tool is to allow users to install.
So by making them live just in the context menu you are hiding (or at least making not obvious) the main interaction the tool has as a purpose.
Btw… I already reported this like 3 years ago, when I used Glamour to doing real life apps. This was the first observation I had each time I explained the system to users.
At the moment, I just made my extensions.
But now I’m making tools for Pharo, so I cannot just extend.
@Esteban: do you need these for lists or other presentations?
Lists, Tables, Trees… anything that can have a contextual menu with important interactions.
Esteban
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.chhttps://www.iam.unibe.ch/mailman/listinfo/moose-dev