|
|
| (11 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | | + | to be deleted |
| − | This page is dedicated to gather discussions on potential evolution of Papyrus.
| + | |
| − | | + | |
| − | == Architecture refactoring ==
| + | |
| − | | + | |
| − | * [[Papyrus/Photon Work Description/Architecture refactoring/Papyrus SDK|Papyrus SDK]]
| + | |
| − | | + | |
| − | = Usability related issues =
| + | |
| − | | + | |
| − | This part presents and discusses some noticeable usability related issues or defects of the current releases.
| + | |
| − | | + | |
| − | Papyrus version: 4.2
| + | |
| − | Model type: UML
| + | |
| − | | + | |
| − | == General ==
| + | |
| − | | + | |
| − | === The Lengthy Menu of New Child (right-clicked) ===
| + | |
| − | | + | |
| − | ==== Problem Description ====
| + | |
| − | | + | |
| − | The menu list of New Child is too long to browse through.
| + | |
| − | | + | |
| − | For example, every time you want to create a new use case (unfortunately it's at the bottom of the menu) directly in the model explorer (not from in a use case diagram), you have to browse and scroll down the lengthy, complex list by pressing the downward arrow repeatedly, tedious operation.
| + | |
| − | | + | |
| − | [[File:NewChildPopup UseCase.png|800px]]
| + | |
| − | | + | |
| − | The same situation happens when creating a new package. You have to scroll down by pressing the arrow many times when the menuitem Package does not appear on the first screen.
| + | |
| − | | + | |
| − | ==== Possible Solutions ====
| + | |
| − | | + | |
| − | * Provide a new quick access (shortcuts) panel at the top in the 'New Child' menu for most frequently-created (or primary) items, e.g. Actor, Class, Model, Package and Use Case, etc.
| + | |
| − | * An alternative way is providing a History panel in the menu to record items most recently created by the user, hence enabling quick access to them by just one click without scrolling.
| + | |
| − | * Besides the lengthy alphabetical listing, group items into semantical categories to greatly shorten the list, and move those less-created (or secondary) ones into lower-level submenus.
| + | |
| − | | + | |
| − | == Sequence Diagram ==
| + | |
| − | | + | |
| − | === Failed to hide/remove unnecessary guard icons in combined fragments ===
| + | |
| − | | + | |
| − | ==== Problem Description ====
| + | |
| − | | + | |
| − | [[File:CombinedFragment_GuardIcon.png|500px]]
| + | |
| − | | + | |
| − | No any apparent way can be found to hide or remove the guard icons (as shown above, red circled) in combined fragments. Seemingly superfluous, they are not normative, and inconsistent with plain-style drawings (merely simple forms in black and white without any colors or unnecessary decorations).
| + | |
| − | | + | |
| − | ==== Possible Solutions ====
| + | |
| − | | + | |
| − | * Could there be a handy project, model and/or diagram level mechanism (by configuration and/or switching) to turn on/off guard icons in all the combined fragments in any relevant diagram?
| + | |
| − | | + | |
| − | ...
| + | |
