Bug 507530 - [Tooling] Improve the properties view for a capsule
Summary: [Tooling] Improve the properties view for a capsule
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:
Blocks:
 
Reported: 2016-11-15 04:57 EST by Peter Cigehn CLA
Modified: 2017-02-23 04:04 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cigehn CLA 2016-11-15 04:57:38 EST
The current customization of the properties view for a capsule only contains the name on the "Real Time" tab. It is proposed that whenever capsule will be visualized in a class diagram style, then four compartments shall be provided on a capsule: attributes, operations, capsule parts and ports. Considering this the corresponding lists shall preferably be provided in the properties view for a capsule.

It probably should be elaborated if the new approach of using tables, with columns providing inline editing of the individual properties for attributes, operations, capsule parts and ports. Compare with  the current table for protocol messages of a protocol and for triggers of transition.

If the inline editing of the attributes, operations, capsule parts and ports becomes too complex, then the current approach with using the "pen"-button which brings up a dedicated edit dialog might be sufficient. Especially if we consider the complex relations between properties of a port.

These tables with attributes, operations, capsule parts and ports shall of course consider inheritance, redefinition and exclusion as indicated by Bug 507529.

The tables could either be placed on the UML-RT tab itself, but that could make the contents of that tab to be too big. Another approach could be to use sub-tabs similar to the Language tab on the root element of a model, which is structured as a nested sub-tab of the UML-RT tab. Maybe it woule be beneficial to have one such nested sub-tab for attributes, operations, capsule parts and ports.
Comment 1 Charles Rivet CLA 2016-11-16 14:30:47 EST
Potentially as part of a UX sprint/MVP