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.
Papyrus/Neon Work Description/Improvements/Palette Configuration Edit UI
Contents
New Palette configuration models shall be editable with an advance UI
Context
The documentation describe the work in the Neon release on the improvement of the user interface permitting to edit EMF Palette configuration models.
The related bug of this work is the bug 482669
Requirement
New Palette configuration emf models shall be editable with an advance UI like the actual palette customization available on diagram. For the moment only a standard ecore editor is available.
| Index | Description |
|---|---|
| REQ_001 | New customization SHALL serialize custom palette to palette configuration Ecore models. |
| REQ_002 | The editor SHALL be the same than the existing one. |
| REQ_002.1 | Creation of local palette. |
| REQ_002.2 | Edition of palette deployed from plugin(read-only). |
| REQ_002.3 | Edition of palette deployed from workspace. |
| REQ_002.4 | Drop object from UML to the palette to add. |
| REQ_002.5 | Drop object from used profiles to the palette to add. |
| REQ_003 | Old XML palette model SHALL work and be editable. |
| REQ_004 | All palette definition SHALL be exportable. |
| REQ_005 | In a standalone editor mode an advance tab should be provide to display element descriptors. An import button should permits to load elementType model. The add button of element descriptors have to reference to this model's specialized type. |
Current state
WORK IN PROGRESS - Video coming soon