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

Eclipse UML Generators/Specification/UserInterface/ConsistencyImprovement

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

UMLGen-JavaBuilder.png

and RTSJ is launched with context menus

UMLGen-Generate AutoJava.png

All generations can be launched in the same context menu: a menu "UML Generators".

UMLGen-ContextMenu.png

From UML elements

C generation is directly launched in the context menu. As Java generation, the "UML Generators" menu is added for consistency.

UMLGen-ContextMenuC-Before.png
UMLGen-ContextMenuC-after.png

Generation properties

C reverse actions

There are two menu actions to add and remove the C2UML nature from C projects. They currently are in the context menu "Convert" witch is used to convert projects in a nature. No update will be done for this.

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.

Back to the top