Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334984 - [General] Papyrus should use the eclipse UI commands/menu/toolbars API rather than providing its own framework
Summary: [General] Papyrus should use the eclipse UI commands/menu/toolbars API rather...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 334262
Blocks: 317338 336518
  Show dependency tree
 
Reported: 2011-01-21 04:43 EST by Cedric Dumoulin CLA
Modified: 2014-03-25 15:42 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Dumoulin CLA 2011-01-21 04:43:55 EST 
Papyrus should use the Eclipse UI commmands/menu/toolbars API rather than providing its own API.
All Papyrus plugins should use this API to provide new menu/toolbars/contextual menu...
Plugins providing menu entry point should document them, and provides associated IDs.

The extensions points to use for declaring UI commands:
org.eclipse.ui.commands
org.eclipse.ui.handlers
org.eclipse.ui.menus

Eclipse Documentation:
- Platform Plug-in Developer Guide > Programmer's Guide > Plugging into the workbench > Basic workbench extension points using commands
Comment 1 Mathieu Velten CLA 2011-02-14 05:21:23 EST 
This has been fixed in rev 4018.
Comment 2 Mathieu Velten CLA 2011-02-14 05:23:34 EST 
reopen the bug since I am guessing it is not specific to navigation and some non standard menus are still there, please close it if not.
Comment 3 Camille Letavernier CLA 2014-03-25 15:42:54 EDT 
Almost everything is now using org.eclipse.ui.* extension points.

Specific subtasks should be opened when this is not the case

I close this one