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.
Papyrus/Neon Work Description/NewFeature/Editor Page Management
Overview
In the Luna release, a long-standing problem in Team sharing of Papyrus models was fixed: that the information about which diagrams and tables were open and how they were laid out in the editor was shared with everyone, so that any changes to the organization of editor pages implied changes in the project checkout. This was fixed by moving the layout information from the *.di resource into a private *.sash resource in the workspace metadata area.
However, as a result, now whenever a user first encounters a model that has diagrams and tables in it, or even if it doesn't, the editor opens up blank. On most platforms, it looks even broken, as a grey canvas (depending on which workbench part has the input focus). This is a confusing first experience with the editor and is unchanged in the Mars release.
Bugs
Two bugs specifically address the problems with the current editor presentation:
Two other bugs are related to the overall editor management concern, and are included in the scope of this feature:
- 434983 - Provide a mechanism to move the editor layout model to either the *.di (Legacy) or hidden *.sash resource (1.0)
- 312473 - Remember last opened diagram
Requirements
- [in progress] R1 The editor SHALL provide a "welcome" page for accessibility and usability.
- R1.1 The Welcome Page SHALL be shown whenever there are no other pages (diagrams, tables, etc.) open. It cannot be closed if it is the last page open, and it is opened automatically when the last page is closed.
- R1.2 The Welcome Page SHOULD provide hyperlinks to the diagrams and tables that may be opened from the notation resource.
- R1.3 The Welcome Page MAY show relationships to other modelling resources, such as applied profiles, referenced library models, loaded and unloaded controlled units, etc.
- R1.4 The Welcome Page MAY show other statistics, such as count of validation problems by severity, counts of elements and stereotype applications, perhaps even number of distinct changes since the last version committed to the repository.
- R1.5 The Welcome Page SHALL be extensible, allowing plug-ins to contribute content. For example, the CDO Integration layer should be able to contribute a pane that shows the number of remote sessions currently editing the same model, and more.
- [in progress] R2 The editor SHALL provide for the option of whether the page layout is shared.
- R2.1 The editor SHALL provide a toggle option, possibly in the Welcome Page, that switches between shared (in the *.di resource) layout and private (in the *.sash resource) layout.
- R2.2 Papyrus SHOULD provide a model export action that puts the current private page layout information (if not already shared in the *.di resource) in the exported *.di resource
- R2.3 The editor SHOULD prompt the user to move layout information into the private *.sash resource on first opening a model
- [in progress] 'R3 The editor SHALL record the currently open editor page in the layout information when it is stored in the private workspace metadata.
- R3.1 The editor WON'T record the open page when the layout is shared
Design
This section presents UI and logical design of the feature.
Welcome Page Wireframes
This section presents some wireframe sketches of the Papyrus editor's Welcome Page.
images here