| Tool settings: How to cutomise Properties View [message #1580611] |
Fri, 23 January 2015 10:57  |
Eclipse User |
|
|
|
Hi there,
I heard the possibility to create a specific properties view.
Can you help me understand how this customisation works ?
I would like to create a specific tab to access to limited properties, how can I do that ?
Eventually, I would like to hide some tabs of the properties view. Is it possible ?
Thank you for your support !
Regards,
Philip
|
|
|
| Re: Tool settings: How to cutomise Properties View [message #1580838 is a reply to message #1580611] |
Fri, 23 January 2015 13:56  |
| Eclipse User |
|
|
|
Hi, Philip,
The Papyrus documentation accessed through the Eclipse Help menu
provides a good deal of information about Properties view customization.
You can certainly add new tabs; I'm not sure about suppressing existing
properties. The documentation should help to answer these questions,
otherwise this is the place to ask.
HTH,
Christian
On 2015-01-23 15:57:57 +0000, Philip LOUCOPOULOS said:
> Hi there,
>
> I heard the possibility to create a specific properties view.
> Can you help me understand how this customisation works ?
>
> I would like to create a specific tab to access to limited properties,
> how can I do that ?
>
> Eventually, I would like to hide some tabs of the properties view. Is
> it possible ?
>
> Thank you for your support !
>
> Regards,
>
> Philip
|
|
|
| Re: Tool settings: How to cutomise Properties View [message #1589875 is a reply to message #1580838] |
Wed, 28 January 2015 13:05 |
| Eclipse User |
|
|
|
Hi,
Quote:Eventually, I would like to hide some tabs of the properties view. Is it possible ?
There are different ways.
The simple one is to disable the properties view configuration which provides the tab (e.g. UML). This can be done in the Preferences > Papyrus > Properties View. Note that different configurations can contribute to the same Tab, so in some cases, you may need to disable several configurations. It is not possible to disable part of a configuration, so this may also hide more than one tab (For example, disabling UML will remove both the UML and the Profile tab)
The more complex one is to rely on the Override mechanism of Views, to disable a specific part of a Configuration.
Another option:
- Disable the configuration completely
- Make a copy of this configuration (In the properties view: "View Menu" > "Customize properties view" > "Copy..." > Edit the copy), then go to the preferences to enable this copy
- Tweak the copy to hide/remove only what you need
(Yes, it is easier to add new properties than to hide existing ones!  )
Regards,
Camille
|
|
|
|
|
| Re: Tool settings: How to cutomise Properties View [message #1592964 is a reply to message #1591376] |
Fri, 30 January 2015 05:33 |
| Eclipse User |
|
|
|
Thanks for these explanations. Customisation of the properties view is not easy to use and to obtain simplified and customised tabs.
Maybe I should reformulate my needs:
From the UML tab of the property view, is it possible to just hide the Is abstract, Is active, Is leaf and the Visibility ?
As I don't see the interest of them, I can imagine to have them hidden for a simple user.
Or the other case, what are Is abstract, Is active, Is leaf and the Visibility used for ?
Thank you
Attachment: Capture.PNG
(Size: 16.79KB, Downloaded 173 times)
[Updated on: Fri, 30 January 2015 05:39] by Moderator |
|
|
| Re: Tool settings: How to cutomise Properties View [message #1593244 is a reply to message #1592964] |
Fri, 30 January 2015 09:00 |
| Eclipse User |
|
|
|
Hi Philip,
isAbstract = true indicates that the class is abstract, i.e., it can not have instances.
isActive =true indicates that the class is active, i.e., an object of that class commences its execution when it is instantiated ("has its own thread of control"). How that object reacts to stimuli is typically described by an "onwedBehaviour" (activity or state machine). If isActive=false, an object of that class needs to exist in the context of another object and its behavior are operations that are called by its container.
isLeaf=true indicates that the class can not have any more redefinition, i.e., it can not be sub-classed.
Visibility is used to constrain accessability of elements to a namespace. For example, a visibility of "package" indicates that a class can only be used by elements in its container package. This is useful, for example, for traceability to check for access violations.
|
|
|
Powered by
FUDForum. Page generated in 0.04296 seconds
Home