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/Mars Work Description/NewFeature/Modeling Assistants"
(Added new demo) |
(→Bugzilla) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
The requirements for Modeling Assistants in the Papyrus diagram editors, addressable in the Mars release, are | The requirements for Modeling Assistants in the Papyrus diagram editors, addressable in the Mars release, are | ||
| − | * '''R1''' assistants provided by a diagram {{req|shall}} be described by a model | + | * {{task-done}} {{strikeover|'''R1''' assistants provided by a diagram {{req|shall}} be described by a model}} |
| − | * '''R2''' the assistants model {{req|shall}} be initially generated ("seeded") from a UML Profile | + | * {{task-done}} {{strikeover|'''R2''' the assistants model {{req|shall}} be initially generated ("seeded") from a UML Profile}} |
| − | * '''R3''' the assistants model {{req|should}}, as much as possible, be unified/aligned with the models for diagram palette customization and Model Explorer "new child" menu customization inasmuch as all three of these mechanisms are, in general terms, different manifestations of tools for creating new model elements | + | * {{task-omitted}} {{bug|459510}} '''R3''' the assistants model {{req|should}}, as much as possible, be unified/aligned with the models for diagram palette customization and Model Explorer "new child" menu customization inasmuch as all three of these mechanisms are, in general terms, different manifestations of tools for creating new model elements |
** '''R3.1''' the modeling assistants {{req|shall}} provide the same "new child" menu as the Model Explorer in the context of diagrams | ** '''R3.1''' the modeling assistants {{req|shall}} provide the same "new child" menu as the Model Explorer in the context of diagrams | ||
*** '''R3.1.1''' which {{req|may}} be further filtered by restrictions of the visualization | *** '''R3.1.1''' which {{req|may}} be further filtered by restrictions of the visualization | ||
| − | * '''R4''' a lightweight customization mechanism {{req|may}} be included that promotes "favourites" in the tool palette as modeling assistants | + | * {{task-omitted}} {{bug|459509}} '''R4''' a lightweight customization mechanism {{req|may}} be included that promotes "favourites" in the tool palette as modeling assistants |
| − | * '''R5''' hyperlinks and the hyperlink creation tool {{req|shall}} continue to be presented in the popup bar, in addition to the element creation tools specified by the assistant model | + | * {{task-done}} {{strikeover|'''R5''' hyperlinks and the hyperlink creation tool {{req|shall}} continue to be presented in the popup bar, in addition to the element creation tools specified by the assistant model}} |
| − | * '''R6''' the standard UML diagrams provided by Papyrus {{req|shall}} provide assistant models for core editing functionality | + | * {{task-inprogress}} '''R6''' the standard UML diagrams provided by Papyrus {{req|shall}} provide assistant models for core editing functionality |
** '''R6.1''' the assistant model for each diagram {{req|should}} be generated from the diagram's GMF Generator model, unless it can better be generated from the diagram's ''Chaos II'' element-types configuration model | ** '''R6.1''' the assistant model for each diagram {{req|should}} be generated from the diagram's GMF Generator model, unless it can better be generated from the diagram's ''Chaos II'' element-types configuration model | ||
| Line 21: | Line 21: | ||
The main bugzilla enhancement item tracking progress of this feature is | The main bugzilla enhancement item tracking progress of this feature is | ||
| − | * | + | * {{bugstrike|451230}} |
| + | |||
| + | Deferred requirements: | ||
| + | |||
| + | * {{bug|459509}} | ||
| + | * {{bug|459510}} | ||
===Demonstration Videos=== | ===Demonstration Videos=== | ||
Latest revision as of 19:55, 9 February 2015
Contents
Modeling Assistants Customization for UML Profiles
This page presents the requirements and design notes for Modeling Assistants in the diagram editors, customizable for DSMLs based on UML Profiles.
Requirements
The requirements for Modeling Assistants in the Papyrus diagram editors, addressable in the Mars release, are
- [done] R1 assistants provided by a diagram SHALL be described by a model
- [done] R2 the assistants model SHALL be initially generated ("seeded") from a UML Profile
- [omitted] bug 459510 R3 the assistants model SHOULD, as much as possible, be unified/aligned with the models for diagram palette customization and Model Explorer "new child" menu customization inasmuch as all three of these mechanisms are, in general terms, different manifestations of tools for creating new model elements
- R3.1 the modeling assistants SHALL provide the same "new child" menu as the Model Explorer in the context of diagrams
- R3.1.1 which MAY be further filtered by restrictions of the visualization
- R3.1 the modeling assistants SHALL provide the same "new child" menu as the Model Explorer in the context of diagrams
- [omitted] bug 459509 R4 a lightweight customization mechanism MAY be included that promotes "favourites" in the tool palette as modeling assistants
- [done] R5 hyperlinks and the hyperlink creation tool SHALL continue to be presented in the popup bar, in addition to the element creation tools specified by the assistant model
- [in progress] R6 the standard UML diagrams provided by Papyrus SHALL provide assistant models for core editing functionality
- R6.1 the assistant model for each diagram SHOULD be generated from the diagram's GMF Generator model, unless it can better be generated from the diagram's Chaos II element-types configuration model
Bugzilla
The main bugzilla enhancement item tracking progress of this feature is
Deferred requirements:
Demonstration Videos
The progress of development of this feature is recorded in a series of videos, here:
- First prototype of basic diagram assistants
- Defining element types for diagram assistants specific to a UML Profile
- Generation of diagram assistants model for a UML Profile targeting a particular diagram
- Generation of diagram assistants model for a UML Profile not targeting any particular diagram, but UML generally
- Generating a diagram assistants model for unprofiled UML, targeting a particular diagram's visual types
- Context-sensitive activation of diagram assistants for UML Profiles