| Re: [mdt-papyrus.dev] Paletteconfiguration model migration |
|
Ok, I start it now. Mickaël De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de GERARD Sebastien You can first do the transformation this morning and it to Benoit who is waiting for for it. Then you can push it on the interoperability repo. Thanks Envoyé depuis mon smartphone Samsung Galaxy. -------- Message d'origine -------- De : Mickael ADAM <mickael.adam@xxxxxxxxxxx>
Date : 28/04/2017 09:37 (GMT+01:00)
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Paletteconfiguration model migration
Hi, Ok, it will be done as soon as possible. It will not be a script, but a migration tool in the interoperability repository as Nicolas has done with sysml migration. The transformation will not be
complex, but I have to learn about the papyrus interoperability framework. If anybody has another way/language/tools to do it quickly, but I think this is the proper way to do it. I should start the migration tool today. Mickaël De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de GERARD Sebastien If the time to do the script is short (I assume it is), please do it ASAP in order to unblock Benoit. Thanks Envoyé depuis mon smartphone Samsung Galaxy. -------- Message d'origine -------- De : Mickael ADAM <mickael.adam@xxxxxxxxxxx>
Date : 27/04/2017 14:20 (GMT+01:00)
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Paletteconfiguration model migration
>works but I have around 400 elements. Outch, indeed it will take time. >Do you know when the script will be available? I don’t know, If I have time I will do that next week, as soon as I finish my current works and the actions tab fix. Mickaël. De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit Yes 0.7. The part “6.
For each tool, add elementType which corresponds to the elementTypeIds in the original file. Past its id in the search field is a easy way to find the corresponding element
type.” works but I have around 400 elements. Do you know when the script will be available? De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Mickael ADAM Which kind of palette do you used before ? If it was paletteconfiguration 0.7 version, you can easily migrate it:
https://wiki.eclipse.org/Papyrus/Migration_Guide/Oxygen#PaletteConfiguration_model A tool
is not available yet but should be done. For others tool definition, there is no planed tool. You’re right, the right click should be implemented.
De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit Hi, You missed the most crucial question
J ð
Is there a script to update the palette? See below some answer : >The usual “Right Click > New element” isn’t available (at least on my machine)
ð
Yes but in big files, contextual menu (Right click) is faster than scrolling to the top. >I have an empty _expression_ properties section that seems useless I don’t see what you mean, I don’t see any empty _expression_ in property view.
ð
As stated by Peter, should be fixed by
https://git.eclipse.org/r/#/c/95844/ >I didn’t manage to create/add an element in the Actions properties section Actions was initially managed to work with the “customize…” menu from diagram>palette>customize…>edit palette. I’m currently on that to do working the “actions” parts in the “standalone” palette editor. Some restriction will be necessary, for example, all element types of the tool should not be read only
to permit the add of the advices. > 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. I don’t have the issue in my case, but as Rémi says, this maybe coming from a serialize issue. I have to fix this to be sure that there is a ‘/’ when I concate bundle id with icon path. Regards, Benoît De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de Mickael ADAM Hi Benoit, See below some answer : >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 don’t see what you mean, I don’t see any empty _expression_ in property view. >I didn’t manage to create/add an element in the Actions properties section Actions was initially managed to work with the “customize…” menu from diagram>palette>customize…>edit palette. I’m currently on that to do working the “actions” parts in the “standalone” palette editor. Some restriction will be necessary, for example, all element types of the tool should not be read only
to permit the add of the advices. > 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. I don’t have the issue in my case, but as Rémi says, this maybe coming from a serialize issue. I have to fix this to be sure that there is a ‘/’ when I concate bundle id with icon path. Thanks for the feedback. Mickaël. De :
mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de MAGGI Benoit 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 |
