Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336518 - [General] All Papyrus plugins should use the UI Commands Framework
Summary: [General] All Papyrus plugins should use the UI Commands Framework
Status: CLOSED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 309958 334984 336505
Blocks:
  Show dependency tree
 
Reported: 2011-02-07 10:11 EST by Cedric Dumoulin CLA
Modified: 2013-03-25 09:00 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cedric Dumoulin CLA 2011-02-07 10:11:28 EST
Whenever a Papyrus plugin need to contribute to menu, context menu, toolbar, coolbar, ... it should use the Eclipse UI commands frameworks.

More info on the framework can be found here:
 - http://wiki.eclipse.org/Command_Core_Expressions
 - http://wiki.eclipse.org/Platform_Command_Framework
 - http://www.vogella.de/articles/EclipseCommands/article.html

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

Papyrus shall provides a up-to-date list of its extension points, ISourceProviders and other useful extensions helpful for menu contributions.
Comment 1 Camille Letavernier CLA 2013-03-25 09:00:23 EDT
Most papyrus-specific commands have been replaced with commands/handlers/menus. I close this task.