Bugzilla – Full Text Bug Listing
| Summary: | Properties and location of applied profiles not displayed / known. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Toni Siljamäki <toni.siljamaki> | ||||||||
| Component: | Views | Assignee: | Camille Letavernier <cletavernier> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||
| Severity: | major | ||||||||||
| Priority: | P1 | CC: | papyrus-bugs, rschnekenburger | ||||||||
| Version: | 0.10.0 | ||||||||||
| Target Milestone: | SR1 | ||||||||||
| Hardware: | All | ||||||||||
| OS: | All | ||||||||||
| Whiteboard: | |||||||||||
| Bug Depends on: | |||||||||||
| Bug Blocks: | 408491, 415211 | ||||||||||
| Attachments: |
|
||||||||||
This should be seen an implicit but default part of MigrateReq - 1, and especially when migrating models based on proprietary profiles. In those cases Bug 408491 is also highly important. What I propose in a first time is to enrich the displayed label of the Profile, to have e.g. something like that: <ProfileName> [v major.minor.micro] [(Has changed, consider reapplying)] [(From <URI>) In a second time, we may have an additional "?" button (e.g. 'Details'), opening a dialog with all the profile properties (e.g. Description, Author, ...) See sample attachment in following comment Created attachment 232452 [details]
Sample profile labels
Sample Screenshot of profiles, with version number and URI (location)
Created attachment 232698 [details]
Another sample .gif
Yes, that may do the trick, that is, the most important information
displayed by default, plus some additional "details" button.
Your example looks a bit "packed" with text. The profile tab e.g for classes
has some additional whitespace characters to separate different info.
Another approach could be to introduce columns for Name, Version etc.
Fixed in r11757. The main profile properties (Name, Location and Version) are now displayed in separate columns. > Fixed in r11757.
This commit occurred during the SVN to GIT migration. Thus, it has not been properly migrated.
Committed again on GIT in:
7c16035bf95ccd93cf556e8f08f6fe6fb82d9008
Just tested this using the N201308190044 nightly build and I can confirm that it works as described in Comment 5 for both local and "registered" profiles. Regarding the additional "details" button described in Comment 2 see also the newly reported Bug 415211. The "details" are the same in both cases, but I cannot tell which bug that depends on which, and they are related. |
Created attachment 231135 [details] Slide with clarifying details See attached slide for info. Currently, not any of the properties of applied profiles are displayed. This means that the user have no idea which version it has, only the name of it, so there is no way to confirm that a model applies the "correct" version of a profile. The user also have no idea where the applied profile is located, that is, if it's a local profile in the workspace/project or a profile registered in the runtime.