Community
Participate
Working Groups
Currently, the granularity of the DOM Model associated to the notation Model doesn't allow for manipulating the labels. The CSS Engine shall support the following labels: - Floatting labels (e.g. the 5 labels of an Association) - Labels in List Compartments (e.g. Property) It shall support both visibility, and mask-managed labels. For example, we wan't to be able to write the following stylesheet: Class > Compartment[type=attribute] > Property { label: visibility name type; /* + p1 : String */ } Note that the mask-managed labels is only a set of booleans. It is not ordered. This example would be equivalent to: label: type visibility name; /* + p1 : String */ For floating labels, we want to be able to write: Association > Property:roleLabel1, Association > Property:roleLabel2 { visible: false; /* hidden */ } Association > Property:multiplicityLabel1, Association > Property:multiplicityLabel2 { visible:true; label: visibility name type multiplicity; /* +class1 : Class1 [1] */ } (Note that in these two examples, the actual selectors might be slightly different, because of N-ary associations. More complex selectors might be required to distinguish each association end).
*** Bug 419405 has been marked as a duplicate of this bug. ***
Shapes labels must also be covered. For example, it should be possible to hide the label of a Class. This is especially useful when displaying elements as symbols (with only the Symbols compartment visible).
I've pushed the initial contribution in a4609aa. The framework is not complete. Especially: - Not all labels are supported (They need to be configured one by one, each time there is a Mask-based label configuration) - SysML Diagrams rely on a different mechanism and do not support masks yet The commit has not been pushed to master. Instead, it is in a specific branch (bugs/417396-CSSLabels) - The Label element has been added to the DOM Model - Label visibility is supported (visible: true | false) - Association, Operation and Properties are properly supported in Class Diagram Example: Port > Label { visible: false; } Operation { label: visibility name "return type"; } TODO: - Support all Mask-based label display - Generate notation types mappings for all diagrams (To avoid manipulating computer-types from CSS Stylesheets) - Adapt the SysML Diagram labels framework to support CSS
A new contribution is available in commit 2c374bf. The following points have been solved: - Support all Mask-based label display - Adapt the SysML Diagram labels framework to support CSS TODO: - Generate notation types mappings for all diagrams (To avoid manipulating computer-types from CSS Stylesheets) - Move the mask managed edit policy from the label node to the top-level node for shapes (Because label nodes are no longer selectable) - Some preference pages need to be either fixed or fully removed (Some of them currently throw exceptions) - Some initial values are forced (Especially for labels visibility), which is not compatible with the CSS framework (Forced values have a higher priority than CSS-computed values, so CSS is never used). Workaround: use the "Default style" button to remove forced values. This contributions introduces major API changes in the mask-managed API (For both SysML and UML diagrams, which rely on two different frameworks). The configuration doesn't rely on bitmasks anymore. Instead, we now use collections of strings, which are much easier to manipulate from stylesheets. The constants values have changed (from integer to strings). The masks are no longer configurable from the preferences. Example: Operation { maskLabel: visibility name type; } The contribution is not yet merged to master. It is in a separate feature branch (bugs/417396-CSSLabels)
The CSS-Labels branch has been merged to master (Between M5 and M6) Update of the current state: > - Generate notation types mappings for all diagrams (To avoid manipulating computer-types from CSS Stylesheets) > - Some preference pages need to be either fixed or fully removed (Some of them currently throw exceptions) > - Some initial values are forced (Especially for labels visibility), which is not compatible with the CSS framework (Forced values have a higher priority than CSS-computed values, so CSS is never used). Done Todo: > - Move the mask managed edit policy from the label node to the top-level node for shapes (Because label nodes are no longer selectable)
I close this task I've opened a specific entry for this: > Todo: > > - Move the mask managed edit policy from the label node to the top-level node for shapes (Because label nodes are no longer selectable) See Bug 431443
This bug should be reopened. See bug 464240.
