| Re: [mdt-papyrus.dev] Paletteconfiguration model migration |
|
Hi Mickaël, Nice to have this new editor. I’m currently trying to update the palettes for SysML 1.4 in oxygen branch. Some comments:
-
The usual “Right Click > New element” isn’t available (at least on my machine)
-
I have an empty _expression_ properties section that seems useless
-
I didn’t manage to create/add an element in the Actions properties section
-
When editing an icon, the popup open with org.eclipse.uml2.uml.editicons as default bundle. I get an exception saying that this bundle is unknown. Are these expected behaviors? Known bugs? Do you have a script to update the palette? Manual update is tedious for palette with a lot of elements. Regards, Benoît De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Mickael ADAM Hi team, As you maybe have seen, palette framework have occurred a refactor.
The main goals of the refactor was to: -
Use the paletteconfiguration model as palette provider for all diagram -
Remove old “aspect Palette” framework. -
Move all palette framework from uml plugins to
infra plugins. A detail of changes and the state of progression can be find here [1]. One of the change is to directly refer element types by a reference instead of the use of
elementtypeid. So the metamodel have changed and models require a migration. Extension point id to define palette have also change to
org.eclipse.papyrus.infra.gmfdiag.common.paletteDefinition A tool is not yet available but you can find an easy way to do it here [2]. If you encounter any problems do not hesitate to contact me. Mickaël. [1] -
https://wiki.eclipse.org/Papyrus/Oxygen_Work_Description/Refactoring/PaletteDefinition [2] -
https://wiki.eclipse.org/Papyrus/Migration_Guide/Oxygen#PaletteConfiguration_model |