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 "Eclipse UML Generators/Specification/UserInterface/ConsistencyImprovement"
| Line 22: | Line 22: | ||
== Detailed Specification == | == Detailed Specification == | ||
| − | === Launch generation | + | === Launch generation=== |
Java and RTSJ generation are launched on UML files and C generation is launched on UML Elements (classes, packages...). | Java and RTSJ generation are launched on UML files and C generation is launched on UML Elements (classes, packages...). | ||
| − | ==== From UML model | + | ==== From UML model ==== |
| − | Currently, Java is generated with an Acceleo launcher | + | Currently, Java is generated with an Acceleo launcher [[Image:UMLGen-JavaBuilder.png|thumb|center|668px]] |
| − | [[Image: | + | |
| − | and RTSJ is launched with context menus | + | and RTSJ is launched with context menus [[Image:UMLGen-Generate AutoJava.png|thumb|center|668px]] |
| − | [[Image:UMLGen-Generate AutoJava.png|thumb|center|668px]] | + | |
=== Context menus | === Context menus | ||
Revision as of 05:03, 29 October 2014
Contents
Evolution Specification: User interface consistency improvement
Current status is DRAFT
Preamble
This is a proposal to improve the user interface consistency.
Relevant tickets:
- Bug 449080 - User interface consistency improvement
Introduction
The goal of this ticket is to make the user interface coherent for all the possible generations:
- context menus;
- generation builders;
- properties pages;
- preferences pages.
Detailed Specification
Launch generation
Java and RTSJ generation are launched on UML files and C generation is launched on UML Elements (classes, packages...).
From UML model
Currently, Java is generated with an Acceleo launcher and RTSJ is launched with context menus
=== Context menus Context menus are used on:
- UML file to launch Java and RTSJ generation;
- UML elements to launch C generation;
- C project to add and remove the C2UML nature.
Backward Compatibility and Migration Paths
Metamodel Changes
This evolution does not change any meta-models.
API Changes
This evolution does not change any API.
User Interface Changes
Read the Sirius User Manual to learn how to handle these interfaces.
Specifically, have a look on the use of Modeling Projects and Representations concepts and the handle of the Diagram Editors.
Documentation Changes
A new user manual should be made.
Tests and Non-regression strategy
This part of the document should describe the strategy to use to correctly test the evolution and guarantee the non-regression.
Implementation choices and tradeoffs
Any important tradeoff or choice made during the implementation should be referenced here with pros/cons leading to the final decision.