Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/Oxygen Work Description/Refactoring/PaletteDefinition"
(Created page with "==Palette Definition== Papyrus provides facilities to define easily domain specific palettes to be bound to the diagram editors. However, Papyrus provides two mecahnism to d...") |
|||
| Line 9: | Line 9: | ||
* improve the model-based palette definition framework to align with legacy implementations if required | * improve the model-based palette definition framework to align with legacy implementations if required | ||
* provide guidance and all the facilities to ease the migration from the deprecated framework to the new model-based | * provide guidance and all the facilities to ease the migration from the deprecated framework to the new model-based | ||
| + | |||
| + | === Associated tasks === | ||
| + | ====Main task==== | ||
| + | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=512343 Bug 512343 - |Palette| Papyrus Palette framework should be refactored ] | ||
| + | |||
| + | ====Related tasks==== | ||
| + | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=508750 Bug 508750 - |Toolsmiths| dispatching customization palette plugins in their own functional unit] | ||
| + | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=447262 Bug 447262 - |Documentation| No embedded documentation for Diagram Editor Palette Customization] | ||
| + | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=510587 Bug 510587 - |Palette| the palette must not be generated by using GMF gen] | ||
| + | *[https://bugs.eclipse.org/bugs/show_bug.cgi?id=510587 Bug 512110 - |Palette| We must a to possibility to override Tool programmaticaly] | ||
Revision as of 06:09, 17 February 2017
Palette Definition
Papyrus provides facilities to define easily domain specific palettes to be bound to the diagram editors.
However, Papyrus provides two mecahnism to do that. The first one was based on an ad hoc xml configuration file and it is now deprecated framework. The new framework is based on a model definition.
This tasks aims at:
- removing the deprecated framework from Papyrus
- replace extension-based definitions of raw diagram editors by a model-based definition
- improve the model-based palette definition framework to align with legacy implementations if required
- provide guidance and all the facilities to ease the migration from the deprecated framework to the new model-based
Associated tasks
Main task
Related tasks
- Bug 508750 - |Toolsmiths| dispatching customization palette plugins in their own functional unit
- Bug 447262 - |Documentation| No embedded documentation for Diagram Editor Palette Customization
- Bug 510587 - |Palette| the palette must not be generated by using GMF gen
- Bug 512110 - |Palette| We must a to possibility to override Tool programmaticaly