Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Papyrus/Oxygen Work Description/Refactoring/PaletteDefinition"

Line 10: Line 10:
 
* provide guidance and all the facilities to ease the migration from the deprecated framework to the new model-based
 
* provide guidance and all the facilities to ease the migration from the deprecated framework to the new model-based
  
=== Associated tasks ===
+
== Associated tasks ==
====Main task====
+
===Main task===
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=512343 Bug 512343 - |Palette| Papyrus Palette framework should be refactored ]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=512343 Bug 512343 - |Palette| Papyrus Palette framework should be refactored ]
  
====Related tasks====
+
===Related tasks===
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=508750 Bug 508750 - |Toolsmiths| dispatching customization palette plugins in their own functional unit]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=508750 Bug 508750 - |Toolsmiths| dispatching customization palette plugins in their own functional unit]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=447262 Bug 447262 - |Documentation| No embedded documentation for Diagram Editor Palette Customization]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=447262 Bug 447262 - |Documentation| No embedded documentation for Diagram Editor Palette Customization]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=510587 Bug 510587 - |Palette| the palette must not be generated by using GMF gen]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=510587 Bug 510587 - |Palette| the palette must not be generated by using GMF gen]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=510587 Bug 512110 - |Palette| We must a to possibility to override Tool programmaticaly]
 
*[https://bugs.eclipse.org/bugs/show_bug.cgi?id=510587 Bug 512110 - |Palette| We must a to possibility to override Tool programmaticaly]
 +
 +
==Steps done==
 +
 +
#Remove old framework classes in:
 +
#:- oep.uml.diagram.common.service
 +
#:- oep.uml.diagram.common.service.palette
 +
#Move palette framework classes
 +
#:''from''
 +
#:- oep.uml.diagram.common.part
 +
#:- oep.uml.diagram.common.service
 +
#:- oep.uml.diagram.common.service.palette
 +
#:''to''
 +
#:- oep.infra.gmfdiag.common.service.palette
 +
#Move palette configuration model
 +
#:''from''
 +
#:- oep.uml.diagram.paletteconfiguration
 +
#:''to''
 +
#:- oep.infra.gmfdiag.paletteconfiguration
 +
#Move palette extension points
 +
#:''from''
 +
#:- oep.uml.diagram.common.paletteCustomization
 +
#:- oep.uml.diagram.common.paletteDefinition
 +
#:''to''
 +
#:- oep.infra.gmfdiag.common.paletteCustomization
 +
#:- oep.infra.gmfdiag.common.paletteDefinition
 +
#Delete plug-ins
 +
#:- org.eclipse.papyrus.customization.paletteconfiguration Plug-in
 +
#:: The plug-in seems not to be usefull. It juste declare facet profile for model explorer...with some query.
 +
#:- org.eclipse.papyrus.uml.diagram.css.palette
 +
#:: The plug-in was used to implement a post action to add css style to an element
 +
#:- org.eclipse.papyrus.uml.diagram.common.aspectToolProvider extension point
 +
#Move files
 +
#:- from uml to infra for oep...paletteconfiguration… plug-in
 +
#:- from customization to toolsmith for org.eclipse.papyrus.customization.palette
 +
#Update paletteConfiguration metamodel
 +
#:- Add entryClassName String property at ElementDescriptor Class.
 +
#:- Replace elementTypeId by elementType references.
 +
#Migrate Palette
 +
#:- UML
 +
#:- SYSML
 +
#Update JUnit Tests
 +
#Create new tests
 +
#:- JUnit
 +
#:- RcpTT
 +
 +
==Regression==
 +
*Manage of required profiles of palette need uml dependencies which have been removed '''FIXME'''

Revision as of 06:27, 17 February 2017

Palette Definition

Papyrus provides facilities to define easily domain specific palettes to be bound to the diagram editors.

However, Papyrus provides two mecahnism to do that. The first one was based on an ad hoc xml configuration file and it is now deprecated framework. The new framework is based on a model definition.

This tasks aims at:

  • removing the deprecated framework from Papyrus
  • replace extension-based definitions of raw diagram editors by a model-based definition
  • improve the model-based palette definition framework to align with legacy implementations if required
  • provide guidance and all the facilities to ease the migration from the deprecated framework to the new model-based

Associated tasks

Main task

Related tasks

Steps done

  1. Remove old framework classes in:
    - oep.uml.diagram.common.service
    - oep.uml.diagram.common.service.palette
  2. Move palette framework classes
    from
    - oep.uml.diagram.common.part
    - oep.uml.diagram.common.service
    - oep.uml.diagram.common.service.palette
    to
    - oep.infra.gmfdiag.common.service.palette
  3. Move palette configuration model
    from
    - oep.uml.diagram.paletteconfiguration
    to
    - oep.infra.gmfdiag.paletteconfiguration
  4. Move palette extension points
    from
    - oep.uml.diagram.common.paletteCustomization
    - oep.uml.diagram.common.paletteDefinition
    to
    - oep.infra.gmfdiag.common.paletteCustomization
    - oep.infra.gmfdiag.common.paletteDefinition
  5. Delete plug-ins
    - org.eclipse.papyrus.customization.paletteconfiguration Plug-in
    The plug-in seems not to be usefull. It juste declare facet profile for model explorer...with some query.
    - org.eclipse.papyrus.uml.diagram.css.palette
    The plug-in was used to implement a post action to add css style to an element
    - org.eclipse.papyrus.uml.diagram.common.aspectToolProvider extension point
  6. Move files
    - from uml to infra for oep...paletteconfiguration… plug-in
    - from customization to toolsmith for org.eclipse.papyrus.customization.palette
  7. Update paletteConfiguration metamodel
    - Add entryClassName String property at ElementDescriptor Class.
    - Replace elementTypeId by elementType references.
  8. Migrate Palette
    - UML
    - SYSML
  9. Update JUnit Tests
  10. Create new tests
    - JUnit
    - RcpTT

Regression

  • Manage of required profiles of palette need uml dependencies which have been removed FIXME

Back to the top