Home » Modeling » Papyrus » Property View too small to display Meta-Attributes
| Property View too small to display Meta-Attributes [message #1775866] |
Tue, 07 November 2017 11:20  |
 Alexander Fuchs
Messages: 5
Registered: January 2015 |
Junior Member |
|
|
Hi,
we are using Papyrus (currently 3.1.0.201709130748) to edit an UML Model which makes use of custom Stereotypes provided in our custom profile.
We use the Papyrus Model Explorer to navigate the model.
We use the Profile tab in the Properties view to edit model elements.
Unfortunately, the window in the Profile tab which contains the Applied Stereotypes is very small. It can show only up to eight Properties of a Stereotype at the same time, but our Stereotypes can have up to 20. See attached screenshot.
This is quite a detriment to our productivity: We don't have the complete picture of the property settings at one glance, and we have to scroll quite often to find specific properties.
Is there a possibility to extend the size of this window?
We also tried a custom property view, as described in http://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.papyrus.views.properties.doc%2Ftarget%2Fgenerated-eclipse-help%2Fproperties-view.html&cp=79_1_0. Unfortunately, this view is to slow with our model: it easily takes up to ten seconds on first use, with similar pauses on further uses. Thus it is not that good for productivity eather. Furthermore, we have to regenerate it with each change of the profile.
Is there any better option we could use to edit the Stereotypes and their properties? Better as in: all properties visible at one glance and editable with a reasonable performance.
Thanks,
Alex
|
|
|
| Re: Property View too small to display Meta-Attributes [message #1775872 is a reply to message #1775866] |
Tue, 07 November 2017 12:43  |
Camille Letavernier
Messages: 952
Registered: February 2011 |
Senior Member |
|
|
Hi Alex,
There is no easy solution to this issue, but I can give you a few leads:
- The performance issue in Papyrus 3.1.x will be "mostly fixed" in 3.2.x (i.e. you'll get the same performances you did in 2.x, or even slightly faster, which is not 100% fluid but should be still be displayed in hundreds of milliseconds rather than tens of seconds). 3.2.x will be released in December this year
- You may split your properties in different tabs, to avoid having to load everything at the same time. This requires more clicks for the user, but if you have so many properties, I believe grouping would make sense anyway
- You may implement a custom properties tab. The main performance issue in generated Papyrus properties views is related to the layout (Which only gets worse with a high number of items). That's because the layout is generated more or less dynamically and has to work with minimal user intervention in many different cases; so it's easy to use but not so efficient. If you provide your own implementation, you can easily provide a simple and efficient layout. Papyrus uses the Eclipse Tabbed Properties View framework, so you can use the standard Eclipse extension points to implement something suited to your needs. If you mostly use primitive properties (Without references or lists), it should be relatively straightforward (Especially if you know a little bit about EMF already)
Although I don't recommend using a Nightly build, you can still try it out to see if it solves your performance issue:
http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/oxygen/
HTH,
Camille
Camille Letavernier
|
|
| | | |
| Re: Property View too small to display Meta-Attributes [message #1775884 is a reply to message #1775883] |
Tue, 07 November 2017 15:56 |
Camille Letavernier
Messages: 952
Registered: February 2011 |
Senior Member |
|
|
Hi Ed,
Quote:Maybe there is a fill layout bug.
Yes, I'm pretty sure there is :) In this case, the layout is custom to Papyrus Properties View, and this layout is not 100% satisfying. Since it's a dynamic layout designed to work with generated properties views, it requires minimal configuration (No layout data, etc.). One consequence is that it is not as efficient (In terms of performances and visual results) as hand-coded SWT layouts.
Alex, there may indeed be a performance bug, either in the properties view or in the profile itself. Please report a ticket on Bugzilla so we can investigate the problem. Also, please specify whether you are using a static or dynamic profile (Do you generate Java code from the profile?), and whether you use an external profile library (Are your Enums defined in a UML Model imported by the profile?).
Cheers,
Camille
Camille Letavernier
|
|
| |
Goto Forum:
Current Time: Tue Apr 16 23:54:42 GMT 2024
Powered by FUDForum. Page generated in 2.94017 seconds |
] 
Search
Help
Register
Login
Home
