Eclipse Community Forums: Papyrus » Share custom palettes

Home » Modeling » Papyrus » Share custom palettes(palette status)

Share custom palettes [message #1748068]

Fri, 18 November 2016 05:35

Eclipse User

Hey Papyrus community
There are several ways to create palettes in Papyrus :
- from edit palette
- using view points

first question :
- do the features available in edit palette are available through viewpoints ?

Then I have created papyrus theme, palette using edit palette tool. What is the best/recommended way to share these customization (palette.xml in metadata, ...) ? Oomph ? zip and share workspace ? extension point ?

If I miss a documentation page about this I'm sorry Sad

Re: Share custom palettes [message #1748077 is a reply to message #1748068]

Fri, 18 November 2016 05:57

Eclipse User

hi,

In which version did your works ?

A way to customize palette is to create a new PaletteConfiguration model. After you can use it through an extension point. I don't know exactly how to do it with viewpoint, sorry.
In oxygen, when you create a new palette configuration model with Palette > Right click > customize: this tool now create palette configuration model with associated element type model. There is a button to export it to workspace.
The use of palette.xml is deprecated.

HTH

Mickaël

Re: Share custom palettes [message #1748079 is a reply to message #1748077]

Fri, 18 November 2016 05:59

Eclipse User

Papyrus 2.0.1
I will try the papyrus configuration model, but I did not find way to add aspect actions on them

Re: Share custom palettes [message #1748095 is a reply to message #1748079]

Fri, 18 November 2016 07:56

Eclipse User

If I'me correct, aspect actions was associated to palette.xml. Now action must passed by element type framework, with for example helper advice .

The tools available in oxygen permits to generate necessary files: https://youtu.be/3_SZLt8ehQY

Re: Share custom palettes [message #1748096 is a reply to message #1748095]

Fri, 18 November 2016 08:01

Eclipse User

OK thank you for the link. can i use Oxygen to define my palette and distribute it to a neon installation ?

Re: Share custom palettes [message #1748097 is a reply to message #1748096]

Fri, 18 November 2016 08:06

Eclipse User

no, there is some changes at the element type metamodel. References between specialized type are now href and not done with a string id. You can try it to have an idea of the structure but it will not be compliant with 2.0

Re: Share custom palettes [message #1748332 is a reply to message #1748097]

Tue, 22 November 2016 05:28

Eclipse User

Hi Tristan,

You will find the code that update neon element type to oxygen here
org.eclipse.papyrus\plugins\developer\org.eclipse.papyrus.dev.types\src\org\eclipse\papyrus\dev\types\handlers\MigrateSpecializations.java

It should be easy to switch some code between line 110-125, to have something that downgrade your files.

Benoit

Re: Share custom palettes [message #1748642 is a reply to message #1748332]

Fri, 25 November 2016 11:05

Eclipse User

Hi,

Just one remark concerning the original question. If it is not the case for Oxygen (I didn't check yet), it would be excellent to couple the PaletteConfiguration model capabilities with the View Point framework. It would really make sense. In the latest release (Neon), this framework is still working with former XML palettes, considered as deprecated.

Re: Share custom palettes [message #1748645 is a reply to message #1748642]

Fri, 25 November 2016 11:37

Eclipse User

Good news: apparently, for Oxygen it is possible to reference *.paletteconfiguration models from a view point configuration (seen in Papyrus-RT)

Re: Share custom palettes [message #1748646 is a reply to message #1748642]

Fri, 25 November 2016 11:39

Eclipse User

Good news: apparently, for Oxygen it is possible to reference *.paletteconfiguration models from a view point configuration (seen in Papyrus-RT)

Re: Share custom palettes [message #1748649 is a reply to message #1748332]

Fri, 25 November 2016 11:58

Eclipse User

and by the way @Benoit, thank you for the link !