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.
Difference between revisions of "Papyrus/Toolsmith/Project Builder"
| Line 2: | Line 2: | ||
This page describes the Papyrus Plug-in Builder features. This builder can be applied to an Eclipse Plug-in contributing Papyrus Toolsmiths customizations, to ensure its well-formedness. | This page describes the Papyrus Plug-in Builder features. This builder can be applied to an Eclipse Plug-in contributing Papyrus Toolsmiths customizations, to ensure its well-formedness. | ||
| + | |||
| + | == Profiles == | ||
| + | |||
| + | TODO: Configure the plug-in to deploy a profile; static profile vs dynamic profile; validation rules | ||
| + | |||
| + | == ElementTypes == | ||
| + | |||
| + | TODO: Generate *.elementtypesconfiguration model from a Profile; validation rules | ||
| + | |||
| + | In Papyrus, the creation and edition of element relies on the GMF Runtime "ElementTypes" API. An ElementType is a higher-level concept on top of EMF EClasses, used for creation and edition of inter-related elements (Such as base UML Elements, Stereotyped UML Elements, or multiple related UML Element such as Associations + AssociationEnds). | ||
| + | |||
| + | For custom UML Profiles, Papyrus provides a tool to automatically generate an "ElementTypesConfiguration" model from a Profile. This model will contain one ElementType (SpecializationType) for each Stereotype in the profile, which can be used to create Stereotyped Elements (e.g. from the Palette). This model can also be used to add rules ("Advices") that will be invoked when the element is modified. | ||
| + | |||
| + | === Creation === | ||
| + | |||
| + | To generate the *.elementtypesconfiguration model from an existing Profile: | ||
| + | |||
| + | * Open the Profile with the Papyrus Editor | ||
| + | * In the Model Explorer, right click on the Profile > Generate Tooling Model > Element Types... | ||
| + | * Specify an for the ElementTypeSet and select the target folder | ||
| + | * Press Finish | ||
| + | |||
| + | If the folder is part of an Eclipse Plug-in, the Wizard will configure the plug-in automatically (Adding extension points, required plug-in dependencies, ...) | ||
| + | |||
| + | === Validation === | ||
| + | ==== Model Rules ==== | ||
| + | ==== Builder Rules ==== | ||
[[Category:Papyrus]] | [[Category:Papyrus]] | ||
Revision as of 10:10, 23 November 2020
Contents
Toolsmiths Project Builder (Work-in-progress)
This page describes the Papyrus Plug-in Builder features. This builder can be applied to an Eclipse Plug-in contributing Papyrus Toolsmiths customizations, to ensure its well-formedness.
Profiles
TODO: Configure the plug-in to deploy a profile; static profile vs dynamic profile; validation rules
ElementTypes
TODO: Generate *.elementtypesconfiguration model from a Profile; validation rules
In Papyrus, the creation and edition of element relies on the GMF Runtime "ElementTypes" API. An ElementType is a higher-level concept on top of EMF EClasses, used for creation and edition of inter-related elements (Such as base UML Elements, Stereotyped UML Elements, or multiple related UML Element such as Associations + AssociationEnds).
For custom UML Profiles, Papyrus provides a tool to automatically generate an "ElementTypesConfiguration" model from a Profile. This model will contain one ElementType (SpecializationType) for each Stereotype in the profile, which can be used to create Stereotyped Elements (e.g. from the Palette). This model can also be used to add rules ("Advices") that will be invoked when the element is modified.
Creation
To generate the *.elementtypesconfiguration model from an existing Profile:
- Open the Profile with the Papyrus Editor
- In the Model Explorer, right click on the Profile > Generate Tooling Model > Element Types...
- Specify an for the ElementTypeSet and select the target folder
- Press Finish
If the folder is part of an Eclipse Plug-in, the Wizard will configure the plug-in automatically (Adding extension points, required plug-in dependencies, ...)