Bug 514475 - [tool][Tracking] Adjust defaults names for models and RootElements when creating project/model
Summary: [tool][Tracking] Adjust defaults names for models and RootElements when creat...
Status: CLOSED FIXED
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Mac OS X
: P2 normal
Target Milestone: 1.0.0   Edit
Assignee: Christian Damus CLA
QA Contact: Peter Cigehn CLA
URL:
Whiteboard: depends_on_papyrus
Keywords: usability
Depends on: 471453
Blocks:
  Show dependency tree
 
Reported: 2017-03-30 08:37 EDT by Charles Rivet CLA
Modified: 2017-07-05 15:59 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Rivet CLA 2017-03-30 08:37:22 EDT
Currently, when creating a new Papyrus-RT project, the user has to enter three partially redundant pieces of information:
 1) Project name
 2) Model (file) name
 3) (model) RootElement name

A common pattern when Papyrus-RT users go through this is to have all three names the same. As such, the Model (file) name and (model) RootElement name should automatically be initialized to the project name.

The same holds true for a new model creation in an existing project. In that case, the model file can not have the same name as the project as there would be a conflict due to the previous rule. The user would have to pick a new model name and the RootElement would then also be set to the same value. (Depending on the current wizards implementation, this may need to be a separate bug).

A more generic approach would be to allow these rules to be overridden by a DSML's implementation - see Bug 471453
Comment 1 Christian Damus CLA 2017-05-25 10:15:01 EDT
The blocking Papyrus bug 471453 is now fixed.
Comment 2 Peter Cigehn CLA 2017-05-29 03:17:09 EDT
Verified to be fixed in the latest Papyrus-RT build (#719), based on the latest Papyrus Oxygen build (#3777). The name of the model file and the root element of the model is now picked up from the parent container. In case of an already existing model file with the same name as the parent container the model is simply proposed to be named "model" (with an additional number suffix in case of a name clash).

Leaving in state verified fixed, and Charles can close (or reopen if needed).
Comment 3 Charles Rivet CLA 2017-07-05 15:59:15 EDT
Closing