Skip to Content

Changes for page KIML Layout Options

Last modified by Alexander Schulz-Rosengarten on 2023/09/11 16:17
From version 24.1
edited by cds
on 2014/03/14 14:31
Change comment: There is no comment for this version
To version 20.1
edited by msp
on 2014/03/08 20:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cds
1 +XWiki.msp
Content
... ... @@ -35,7 +35,7 @@
35 35  Default
36 36  )))
37 37  |(((
38 -[[Alignment>>doc:||anchor="alignment"]]
38 +Alignment
39 39  )))|(((
40 40  de.cau.cs.kieler.alignment
41 41  )))|(((
... ... @@ -46,7 +46,7 @@
46 46  AUTOMATIC
47 47  )))
48 48  |(((
49 -[[Aspect Ratio>>doc:||anchor="aspectRatio"]]
49 +Aspect Ratio
50 50  )))|(((
51 51  de.cau.cs.kieler.aspectRatio
52 52  )))|(((
... ... @@ -133,22 +133,6 @@
133 133  )))|(((
134 134  false
135 135  )))
136 -|(% colspan="1" %)(% colspan="1" %)
137 -(((
138 -Label Side
139 -)))|(% colspan="1" %)(% colspan="1" %)
140 -(((
141 -de.cau.cs.kieler.labelSide
142 -)))|(% colspan="1" %)(% colspan="1" %)
143 -(((
144 -Enum
145 -)))|(% colspan="1" %)(% colspan="1" %)
146 -(((
147 -Parents
148 -)))|(% colspan="1" %)(% colspan="1" %)
149 -(((
150 -SMART
151 -)))
152 152  |(((
153 153  Label Spacing
154 154  )))|(((
... ... @@ -162,7 +162,7 @@
162 162  
163 163  )))
164 164  |(((
165 -[[Layout Hierarchy>>doc:||anchor="layoutHierarchy"]]
149 +Layout Hierarchy
166 166  )))|(((
167 167  de.cau.cs.kieler.layoutHierarchy
168 168  )))|(((
... ... @@ -397,7 +397,7 @@
397 397  )))
398 398  |(% colspan="1" %)(% colspan="1" %)
399 399  (((
400 -[[Comment Box>>doc:||anchor="commentBox"]]
384 +Comment Box
401 401  )))|(% colspan="1" %)(% colspan="1" %)
402 402  (((
403 403  de.cau.cs.kieler.commentBox
... ... @@ -483,7 +483,7 @@
483 483  )))
484 484  |(% colspan="1" %)(% colspan="1" %)
485 485  (((
486 -[[Hypernode>>doc:||anchor="hypernode"]]
470 +Hypernode
487 487  )))|(% colspan="1" %)(% colspan="1" %)
488 488  (((
489 489  de.cau.cs.kieler.hypernode
... ... @@ -581,7 +581,7 @@
581 581  )))
582 582  |(% colspan="1" %)(% colspan="1" %)
583 583  (((
584 -[[No Layout>>doc:||anchor="noLayout"]]
568 +No Layout
585 585  )))|(% colspan="1" %)(% colspan="1" %)
586 586  (((
587 587  de.cau.cs.kieler.noLayout
... ... @@ -677,22 +677,6 @@
677 677  )))
678 678  |(% colspan="1" %)(% colspan="1" %)
679 679  (((
680 -Thickness
681 -)))|(% colspan="1" %)(% colspan="1" %)
682 -(((
683 -de.cau.cs.kieler.thickness
684 -)))|(% colspan="1" %)(% colspan="1" %)
685 -(((
686 -Float
687 -)))|(% colspan="1" %)(% colspan="1" %)
688 -(((
689 -Edges
690 -)))|(% colspan="1" %)(% colspan="1" %)
691 -(((
692 -1.0
693 -)))
694 -|(% colspan="1" %)(% colspan="1" %)
695 -(((
696 696  Zoom to Fit
697 697  )))|(% colspan="1" %)(% colspan="1" %)
698 698  (((
... ... @@ -744,8 +744,6 @@
744 744  
745 745  = Detailed Documentation =
746 746  
747 -This section explains every layout option in more detail.
748 -
749 749  == The Most Important Options ==
750 750  
751 751  While most layout options are used to affect how the active layout algorithm computes concrete coordinates for the graph elements, there are some layout options that have a special role in KIML.
... ... @@ -754,13 +754,13 @@
754 754  
755 755  {{id name="layoutAlgorithm"/}}
756 756  
757 -The option with identifier {{code language="none"}}de.cau.cs.kieler.algorithm{{/code}} specifies which layout algorithm to use for a graph or subgraph. The value can be either the identifier of a layout algorithm or the identifier of a layout type. In the latter case the algorithm with highest priority of that type is applied. It is possible to set different values for this option on subgraphs of a hierarchical graph, where a subgraph is identified by a parent node. A layout algorithm is responsible to process only the direct content of a given parent node. An exception from this rule is made when the [[Layout Hierarchy>>doc:||anchor="layoutHierarchy"]] option is active.
723 +The option with identifier {{code language="none"}}de.cau.cs.kieler.algorithm{{/code}} specifies which layout algorithm to use for a graph or subgraph. The value can be either the identifier of a layout algorithm or the identifier of a layout type. In the latter case the algorithm with highest priority of that type is applied. It is possible to set different values for this option on subgraphs of a hierarchical graph, where a subgraph is identified by a parent node. A layout algorithm is responsible to process only the direct content of a given parent node. An exception from this rule is made when the Layout Hierarchy option is active.
758 758  
759 759  The following layout has been created by setting a force-based layout algorithm on the inner hierarchy level and a layer-based layout algorithm on the top level.
760 760  
761 761  [[image:attach:layout_algorithm.png]]
762 762  
763 -==== Available Algorithms and Libraries ====
729 +=== Available Algorithms and Libraries ===
764 764  
765 765  * **The [[KLay Project>>doc:Layout Algorithms (KLay)]]** - Java implementations of standard layout approaches, augmented with special processing of graph features such as ports and labels.
766 766  * **Randomizer** - Distributes the nodes randomly; not very useful, but it can show how important a good layout is for understanding a graph.
... ... @@ -771,7 +771,7 @@
771 771  * **OGDF** ((% style="color: rgb(0,0,0);" %)[[www.ogdf.net>>url:http://www.ogdf.net/||shape="rect"]](%%)) - A self-contained C++ class library for the automatic layout of diagrams. The version that is shipped with KIELER is compiled as an executable that reads files in OGML format and outputs the computed concrete layout.
772 772  * **Graphviz** ([[www.graphviz.org>>url:http://www.graphviz.org/||shape="rect"]]) - An open source graph visualization tool with several graph layout programs, web and interactive graphical interfaces, auxiliary tools, libraries, and language bindings. Graphviz needs to be installed separately in order to be used within KIELER, since it is called in a separate process using the DOT language for communication.
773 773  
774 -==== Predefined Layout Types ====
740 +=== Predefined Layout Types ===
775 775  
776 776  * **Layered** - The layer-based method emphasizes the direction of edges by pointing as many edges as possible into the same direction. The nodes are arranged in layers and then reordered such that the number of edge crossings is minimized. Afterwards, concrete coordinates are computed for the nodes and edge bend points.
777 777  * **Orthogonal** - Orthogonal methods follow the "topology-shape-metrics" approach, which first applies a planarization technique, resulting in a planar representation of the graph, then compute an orthogonal shape, and finally determine concrete coordinates for nodes and edge bend points by applying a compaction method.
... ... @@ -794,6 +794,15 @@
794 794  * **Use Case Diagram** - Use case diagrams as defined by the UML.
795 795  * **Unconnected Boxes** - Sets of nodes that have no connections and are treated as resizable boxes. This is related to mathematical [[packing problems>>url:http://en.wikipedia.org/wiki/Packing_problem||shape="rect"]]. Example: Regions in [[doc:SCCharts SyncCharts]].
796 796  
763 +== Other Options ==
764 +
765 +* **Layout Hierarchy** ({{code language="none"}}de.cau.cs.kieler.layoutHierarchy{{/code}}) - If this option is supported and active, the layout algorithm is requested to process the full hierarchy contained in the input node. This means that instead of executing another algorithm on each hierarchy level, all levels are arranged in a single algorithm execution.
766 +* **Hypernode** ({{code language="none"}}de.cau.cs.kieler.hypernode{{/code}}) - A node that is marked as hypernode has a special role in the graph structure, since all its incident edges are treated as parts of the same [[hyperedge>>url:http://en.wikipedia.org/wiki/Hypergraph||shape="rect"]]. Example: relation vertices in [[Ptolemy>>url:http://ptolemy.eecs.berkeley.edu/||shape="rect"]] models.
767 +* **Comment Box** ({{code language="none"}}de.cau.cs.kieler.commentBox{{/code}}) - A node that is marked as comment box is treated as a label that needs to be placed somewhere. This is different to normal node labels, which are usually regarded as fixed.
768 +* **No Layout** ({{code language="none"}}de.cau.cs.kieler.noLayout{{/code}}) - Elements that are marked with this option are excluded from layout. This is used to identify diagram objects that should not be regarded as graph elements.
769 +
770 +This section explains every layout option in more detail.
771 +
797 797  === Edge Routing ===
798 798  
799 799  {{id name="edgeRouting"/}}
... ... @@ -803,66 +803,14 @@
803 803  * POLYLINE
804 804  Edges consist of one or more segments defined by a list of bend points.
805 805  * ORTHOGONAL
806 -Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically.
807 -* SPLINES
808 -Edges are routed as splines (smooth curves).
781 +Edges are routed orthogonally, meaning that each segment of an edge runs either horizontally or vertically, but never at an angle.
782 +* SPLINE
783 +Edges are routed as splines (smooth curves). (% style="color: rgb(153,51,0);" %)**TODO:** Add more documentation on how the returned bend points are to be interpreted.
809 809  * UNDEFINED
810 -No particular edge routing style is selected. Usually this value points to the default setting of the selected layout algorithm.
785 +No particular edge routing style is selected. The result produced by the layout algorithm may be undefined.
811 811  
812 -[[image:attach:edge_routing.png]]
787 +(% style="color: rgb(153,51,0);" %)**TODO:** Add an image illustrating the different routing styles.
813 813  
814 -When used as layout option, the edge routing is set for a whole graph or subgraph, i.e. on a parent node. However, the property is additionally used for the output of the layout algorithm in order to mark individual edges. If the edge routing assigned to an edge is anything other than SPLINES, the bend points of that edge are interpreted with their normal meaning, i.e. straight lines are drawn between consecutive bend points. If, on the other hand, a layout algorithm marks an edge with the value SPLINES, the bend points have to be interpreted as control points for a series of cubic splines following this procedure:
815 -
816 -1. Start at the source point of the edge.
817 -1. As long as there are at least three bend points left:
818 -11. Draw a cubic spline segment to the third bend point with the other two bend points as control points.
819 -11. Use the third bend point as start point for the next segment.
820 -11. Consume the three bend points and proceed to the next segment.
821 -1. Check the number of remaining bend points:
822 -11. Two bend points – draw a cubic spline segment to the target point of the edge.
823 -11. One bend point – draw a quadratic spline segment to the target point of the edge.
824 -11. No bend point – draw a straight line to the target point of the edge.
825 -
826 -== Other Options ==
827 -
828 -=== Alignment ===
829 -
830 -{{id name="alignment"/}}
831 -
832 -Determines the alignment of a node in relation to other nodes of the same row or column. For layer-based algorithms, for instance, this option controls how a node is positioned inside its assigned layer.
833 -
834 -=== Aspect Ratio ===
835 -
836 -{{id name="aspectRatio"/}}
837 -
838 -The aspect ratio of a drawing is the ratio of its total width to its total height. This option gives some control over that ratio, although in most cases it is only interpreted as a hint on how to arrange multiple connected components, hence the actual aspect ratio will probably be different from what has been specified with the option.
839 -
840 -=== Comment Box ===
841 -
842 -{{id name="commentBox"/}}
843 -
844 -A node that is marked as comment box is treated as a label that needs to be placed somewhere. In contrast to normal node labels (modeled with a KLabel instance), comment boxes may have connections to other nodes, as in the following example.
845 -
846 -[[image:attach:comment_box.png]]
847 -
848 -=== (% style="line-height: 1.5625;" %)Hypernode(%%) ===
849 -
850 -{{id name="hypernode"/}}
851 -
852 -A node that is marked as hypernode has a special role in the graph structure, since all its incident edges are treated as parts of the same [[hyperedge>>url:http://en.wikipedia.org/wiki/Hypergraph||shape="rect"]]. Example: relation vertices in [[Ptolemy>>url:http://ptolemy.eecs.berkeley.edu/||shape="rect"]] models.
853 -
854 -=== Layout Hierarchy ===
855 -
856 -{{id name="layoutHierarchy"/}}
857 -
858 -If this option is supported and active, the layout algorithm is requested to process the full hierarchy contained in the input node. This means that instead of executing another algorithm on each hierarchy level, all levels are arranged in a single algorithm execution.
859 -
860 -=== No Layout ===
861 -
862 -{{id name="noLayout"/}}
863 -
864 -Elements that are marked with this option are excluded from layout. This is used to identify diagram objects that should not be regarded as graph elements.
865 -
866 866  === Port Offset ===
867 867  
868 868  {{id name="portOffset"/}}
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9470074
1 +9470014
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470074/KIML Layout Options
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470014/KIML Layout Options