Community
Participate
Working Groups
All Toolsmiths plugins should contribute to a given Toolsmiths menu under Papyrus
New Gerrit change created: https://git.eclipse.org/r/85205
Waiting for a toolsmiths menu contribution
There is no main menu relatives to Toolsmiths, Developer or Addons. It will be create to create those in order to help developer to add their own contributions.
Created attachment 268361 [details] Initial proposal for Papyrus Menu
Created attachment 268362 [details] Initial proposal for popup/new child
Some reflections regarding the proposals. Since I am not fully sure that I understand the complete context for the change, and with which focus it is supposed to have it is a bit hard to provide feedback, e.g. is the focus to improve for (possibly naive) end-users, or is the focus on structuring things for (possibly really) advanced users like developers and tool-smiths?. Since the bug is written on the Toolsmiths component I first thought that it was only related to the Papyrus for Toolsmiths, but looking at the screen shots it looks like it will impact also any of the end-user configurations of Papyrus. If I only look at this from an end-user perspective, possibly a naive end-user, I wonder if it such good to move the current commands down onto a "basic actions" submenu. They will then be more "obscured" and it will be harder to use them (you need to move the mouse more when selecting from a submenu). For the top level menu, I really think that any "basic actions" should be available directly on the top level itself (as they are today). Also this about "basic actions" vs. "addons". How will a (possibly naive) end-user know what is considered "basic action" vs. "addons"? I think that it is perfectly okay to have the submenus for developers and tool-smiths on separate submenus, since those are advanced users that know how find their ways around in the tool. But for end-users I am not sure that this is appropriate. When it comes to the popup menu in the model explorer, I am not sure at all that the same kind of structure on the top level menu should be used (and definitively not the same set of menu choices). On the context menu it becomes even more important if and where such submenus are to be used, since it will be even harder to find and select menus on submenus, far down. For example: If the "basic actions" (whatever those are), really are "basic" and used very often, then it should really be placed higher up on the context menu (the rule should be that the more often a menu is used, the higher up on the context menu it should be placed, and the more seldom it is used, it should be placed further down).
