Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 197828

Summary: [Editors] Context menu arrangement need to be consistent
Product: [Eclipse Project] PDE Reporter: Noam Chitayat <noam.chitayat>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
(Awful) Mockup of the new standard context menu convention. none

Description Noam Chitayat CLA 2007-07-25 11:53:33 EDT 
Build ID: I20070717-1020

Yesterday, we created a standard for context menu arrangement for PDE editors. The editors now need to conform to the standard, which requires that common actions (New/Add, Clipboard ops, Delete/Remove) appear at the top of the context menu when applicable, with other, domain-specific actions (i.e. Preview) appearing below them.

The "New"/"Add" submenu should be context-sensitive: if you right-click on an object and open the submenu, you should only see items that can be children of the object you right-clicked. If no items are applicable, the New menu should not appear at all. (See Schema Editor and Cheatsheet editors for correct behaviour)

The "Delete" option should always appear when a specific object or group of objects is right-clicked. If it is not applicable, it should appear disabled. PDE editors already follow this convention in many cases.
Comment 1 Noam Chitayat CLA 2007-07-25 11:59:35 EDT 
Created attachment 74586 [details]
(Awful) Mockup of the new standard context menu convention.

The ordering and separation of Delete and the clipboard operations should match the ordering in the "Edit" toolbar menu.

Note that this mockup shows the standard as it would appear with both bug 197816 and bug 197821 fixed.
Comment 2 Noam Chitayat CLA 2007-07-25 12:22:00 EDT 
I propose that we open separate bugs for each editor that violates this standard, since there are separate context menu implementations. That way, the fixes are incremental and the reviews can be more focused on specific areas.
Comment 3 Brian Bauman CLA 2007-07-25 12:34:21 EDT 
I love the idea of consistency.  This should definitely help usability of the context menus.  

When updating the context menus, we should also try to assign numnonics for any (context menu) items which are missing them.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:35 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 5 Julian Honnen CLA 2019-09-09 02:44:12 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.