Yes, you are right for confusion. I will rename extended types plugins with no diagram inside.
Rémi
De : Cedric Dumoulin [mailto:cedric.dumoulin@xxxxxxx]
Envoyé : mardi 29 mars 2011 14:09
À : Papyrus Project list
Cc : SCHNEKENBURGER Remi 211865
Objet : Re: [mdt-papyrus.dev] Commit in Incoming folder
Hi,
For my point of view, all plugins starting with 'oep.diagram' should go into 'uml' folder (and not core folder).
So, in your proposal, either the targetted folder (core) is wrong, or the proposed plugin names (oep.diagram) :-).
It seems that this is the namespace 'diagram' that lead to confusion. This namespace is already used for uml diagrams.
Cedric
SCHNEKENBURGER Remi 211865 wrote:
Hi all,
Some new plugins have been commited in the incoming folder. The main purpose is to improve the handling of the palette tools and modeling assistant in Papyrus :
Configuration using emf models instead of dedicated framework for palette configuration, to ease the extension of the pre/post actions
handling better the actions for elements created by the palette and modeling assistant. What is done yet is to modify the element after it has been created semantically and graphically. Semantic actions are now handled directly after element creation and before graphical creation
Generic integration and configuration of EMF Facet queries in Papyrus. It is now possible to define the configuration of an emf facet query and to evaluate it in the tool. It is also possible to test queries with parameters.
Description of the plugins:
org.eclipse.papyrus.core.queries
Target folder: core
Short description
Generic integration of the queries in Papyrus. This plugin allows to evaluate queries everywhere in Papyrus, from the util class QueryUtils, and contains some converters for data values.
org.eclipse.papyrus.core.queries.configuration(.edit(or))
Target folder: core
Short description
Definition of the metamodel for emf facet queries configuration, for queries with parameter values.
org.eclipse.papyrus.diagram.extendedtypes(.edit(or))
Target folder: core
Short description
Definition of extended element types, with an extended element type registry. This allow definition and registration of new element types that contains pre/post actions and pre-validation (boolean queries that checks if the element can be created in the current context)
org.eclipse.papyrus.diagram.extendedtypes.emf(.edit(or))
Target folder: core
Short description
Configuration of post actions for emf-based extended element types. Basically, it defines the post action to set semantic values to a newly created emf element.
org.eclipse.papyrus.diagram.extendedtypes.uml(.edit(or))
Target folder: uml
Short description
Configuration of post actions for uml-based extended element types. Basically, it defines the post action to apply stereotypes and set stereotypes property values to a newly created uml element.
org.eclipse.papyrus.diagram.paletteconfiguration(.edit(or))
Target folder: core
Short description
Configuration of palettes that should replace the previous framework, based on xml models.
Cheers,
Rémi
-----------------------
Remi Schnekenburger
+33 (0)1 69 08 48 48 - remi.schnekenburger@xxxxxx
CEA LIST, Laboratoire d’Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE), Point Courrier 94, Gif-sur-Yvette, F-91191 France
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
