Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » Papyrus » Presentation of customized stereotype shapes in diagrams
Presentation of customized stereotype shapes in diagrams [message #1589615] Wed, 28 January 2015 14:57 Go to next message
Thomas Wiman is currently offline Thomas WimanFriend
Messages: 53
Registered: June 2012
Location: Stockholm , Sweden

I have managed to display shapes (svg-files) defined on classifier stereotypes as element compartments or as shape decorations in UML diagrams in Papyrus v1.0.1 (Luna release).

However, I canĀ“t find a way to only display the shapes in a diagram without any surrounding element "box", preferrable above or encapsulating the element name similar to how actor and use case shapes are presented.

Is it possible to display only the shapes, in v1.0.1 without a need for deeper (programmatic) customizations, or are there any plans for supporting it in future releases? If not, are there some guidelines available on how to do that kind of classifier presentation customization.

A related question: is it possible to hide the textual keywords displayed within guillmets for standard elements, for example <<component>> for component elements?

Thomas Wiman
MetaModelAgent Product Manager
Re: Presentation of customized stereotype shapes in diagrams [message #1589809 is a reply to message #1589615] Wed, 28 January 2015 17:17 Go to previous messageGo to next message
Camille Letavernier is currently offline Camille LetavernierFriend
Messages: 926
Registered: February 2011
Senior Member
Hi Thomas,

Have a look at the CSS Properties described in the documentation (Help Contents > Papyrus Guide > Use Guide > CSS Stylesheets > Style Properties > Second table of properties, related to "advanced" customization). Even more such properties are coming in Mars (Papyrus 1.1) but are not included in the documentation yet. Especially, the following properties can be interesting (Luna + Mars):

displayName: true | false; /* Hide the label */
displayBorder: true | false; /* Hide the borders */
transparency: 100; /* Hide the Background */
displayTag: true | false; /* Only for predefined UML Tags such as <<Component>>; not for stereotypes */

We currently don't allow modification of these properties outside a CSS stylesheet (= no dedicated properties view), but we're considering the addition of an "Advanced Appearance" tab in the properties view in Mars (Although hidden by default).

Additional style properties available in Mars are described here:

Edit: I forgot to mention the rules to hide all Compartments, except the Symbol:

/* Hide all compartments... */
Compartment {
    visible: false; 

/* ...except the symbol compartment (SVG Image) */
    visible: true; 


Camille Letavernier

[Updated on: Wed, 28 January 2015 17:20]

Report message to a moderator

Re: Presentation of customized stereotype shapes in diagrams [message #1591094 is a reply to message #1589809] Thu, 29 January 2015 10:09 Go to previous messageGo to next message
Patrik Jonsson is currently offline Patrik JonssonFriend
Messages: 18
Registered: January 2015
Junior Member
Hi Camille
I am responding on behalf of my esteemed colleague Thomas Wiman.
We started trying to use the css on both the Luna (SR 1.a (4.4.1)) and Mars M4. We were able to successfully change font color and some other properties using the .css.
However, we also tried to use the displayTag for a Component in order to remove the <<Component>> tag, but failed in this.

Here is our .css
Component {
fontColor: blue;
bold: true;

Version: Mars Milestone 4 (4.5.0M4)
Build id: 20141217-1924

Please advice,

Re: Presentation of customized stereotype shapes in diagrams [message #1738566 is a reply to message #1589615] Wed, 20 July 2016 22:11 Go to previous message
Ian Scott is currently offline Ian ScottFriend
Messages: 1
Registered: April 2016
Junior Member
Hi Patrik,

Your original post was a long time ago, but I have just come across a similar issue with "displayTag"...

It seems like the tool responds to "displayTags" < notice the plural. This is either a documentation defect, or since a UML element should only have one tag then possibly an implementation issue...
Previous Topic:Return-type multiplicity field is empty
Next Topic:Allocation of Activities/Actions to blocks in SysML
Goto Forum:

Current Time: Fri Jul 03 17:56:56 GMT 2020

Powered by FUDForum. Page generated in 0.02157 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top