Bug 511829 - [Tooling] Introduce a specific Papyrus-RT perspective
Summary: [Tooling] Introduce a specific Papyrus-RT perspective
Status: NEW
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 494288
Blocks:
  Show dependency tree
 
Reported: 2017-02-07 06:50 EST by Peter Cigehn CLA
Modified: 2017-06-08 09:04 EDT (History)
2 users (show)

See Also:


Attachments
Screen shot showing a proposed perspective layout (115.86 KB, image/png)
2017-02-07 06:50 EST, Peter Cigehn CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cigehn CLA 2017-02-07 06:50:18 EST
Created attachment 266693 [details]
Screen shot showing a proposed perspective layout

With the introduction of the code snippet view, as tracked by Bug 494288, the need for a specific Papyrus-RT perspective with an adjusted layout is needed.

One of the fundamental aspects of the separate code snippet view is that is shall be possible to have the properties view and the code snippet view visible at the same time, i.e. they probably need to be located in different "view stacks".

In the attached screen shot, there is a proposed layout, based on the corresponding layout used in the legacy tooling. The proposal uses the new Documentation view available in the Oyxygen version of base Papyrus. This is also a separate view, very similar to the code snippet view.

So layout keeps the properties view and the code snippet view (examplified with the Documentation view) is kept in two "view stacks" at the bottom. The outline view, earlier in the left bottom corner is moved to the right of the editor area (as it is in the legacy tooling's layout).

The details can of course be further elaborated, but the core aspect of this proposal is two separate "view stacks" where the properties view is shown next to the code snippet view. Exactly which views goes into which of these two stacks can probably be tweaked if needed.

When we get improved integration with CDT and support for generating problem markers in model for code-generation/compilation faults, it probably needs to be elaborated if the standard problems view shall be include by default as well (as it is in the legacy tooling).
Comment 1 Charles Rivet CLA 2017-04-19 15:35:31 EDT
Moved to future - very easy for users to create their own perspective and need to understand the new viewpoint capabilities.
Comment 2 Charles Rivet CLA 2017-06-08 09:04:44 EDT
(In reply to Charles Rivet from comment #1)
> Moved to future - very easy for users to create their own perspective and
> need to understand the new viewpoint capabilities.

Something else to take into account is the Papyrus IC's composability requirement for the Papyrus product line, which would require the coexistence of multiple perspectives and switching between depending on context.