Bug 510587 - [Palettes][DiaGen] the palette must not be generated by using GMF gen
Summary: [Palettes][DiaGen] the palette must not be generated by using GMF gen
Status: ASSIGNED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mickael ADAM CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 512343
  Show dependency tree
 
Reported: 2017-01-17 10:13 EST by Patrick Tessier CLA
Modified: 2017-08-03 04:30 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Tessier CLA 2017-01-17 10:13:37 EST
The palette must not be generated by using GMF gen. 
When a diagram is generated , the diagram must reference directly a model of palette.
Comment 1 Mickael ADAM CLA 2017-01-23 09:45:07 EST
The first task is to replace generation of palette definition in plugin xml from gmfgen by a generation of a palette configuration model with the extension point to declare it. The extension point to declare palette configuarion have to be extended to set the target editorId of the model.

In a second time when new Architecture framework will be deployed, a link between ViewPoint and palette shall be done. This have to be discuss.
Comment 2 Mickael ADAM CLA 2017-01-26 09:17:49 EST
new gerrit: https://git.eclipse.org/r/89092

Generate palette configuration model for:
	- class
	- communication
	- component
	- composite
	- deployement
	- profile
	- Usecase
	- activity
	- state machine

Hand made palette configuration model:
	- Interaction overview
	
Does not work for sequence and timing diagram: usage of custom Factory
Comment 3 Mickael ADAM CLA 2017-02-02 11:15:43 EST
Should I migrate palettes from sysml 1.1 ?
Comment 4 Eclipse Genie CLA 2017-02-13 11:42:51 EST
New Gerrit change created: https://git.eclipse.org/r/90974
Comment 5 Mickael ADAM CLA 2017-02-14 05:57:12 EST
The second patch is for sysml 1.1.

Since a refactor and a evolution of palette configuration plug-ins and metamodel is planned both patches is waiting before being rebased and updated.