Orthogonal Layout
An orthogonal layout is a multi-purpose layout provider for undirected models. It produces compact drawings with no overlaps, few crossings, and few bends.
An orthogonal layout is useful for models that use database schema, system management, and software engineering.
- Layout style—choose one of the following styles:
Normal (default)—Node sizes will not be changed by this layout. The drawing will contain very few bends.
Box—Nodes are resized according to the number and position of their neighbors to reduce the overall number of bends.
Fixed Box—Similar to Box but retains original entity sizes.
Fixed Mixed—Similar to Mixed but retains original entity sizes.
Mixed—Resembles Box but resizes all entities to equal size. Introduces additional bends and routes the last relationship segment of these relationships non-orthogonally to their adjacent entities.
Normal Tree—Similar to Normal but larger subtrees are processed using a specialized tree layout algorithm, which is better suited for tree-like structures than the original orthogonal layout style.
Uniform—All entity sizes will be changed to equal size before the model is processed.
-
Reduce relationship crossings—Reduces the overall number of relationship crossings. The cost for the reduction is increased execution time of the layout.
-
Length reduction—Reduces the overall relationship lengths. The cost for the reduction is an increased execution time of the layout algorithm.
- Consider entity labels—Guarantees that entity labels will not overlap entities in the model.
- Layout style—See description above.
- Grid spacing—Defines the virtual grid spacing used by the layout algorithm. Each entity will be placed in such a way that its center point lies on a grid point. Edges will be routed in such a way that their segments lie on grid lines, if the terminal entities of the relationships allow to place the ports accordingly. Note that this option is only guaranteed to be obeyed for Normal layout style.
- Reduce relationship crossings—See description above.
- Length reduction—See description above.
- Minimize bends—Avoids helical arrangement of chains of entities.
- Use randomization—Increases overall layout quality with high probability. The cost for this layout optimization is increased execution time and non-deterministic results for subsequent layout invocations.
- Use face maximization—
- Use existing layout as a sketch—Interprets the initial model layout as a sketch of the resulting orthogonal layout. The layout algorithm tries to "orthogonalize" the given sketch without making too much modifications in respect to the original drawing
- Consider entity labels—See description above.
- Edge labeling—choose one of the following styles: None (default)—No labels will appear on selected relationships. Generic—Finds label positions for the labels from a given model so that they, ideally, do not overlap with each other or with model elements. It does so without altering entities or relationships in any way. Integrated (default)—used in conjunction with layout style "Normal." Taken into consideration when determining both entity placement and relationship path generation. With this strategy it is guaranteed that no relationship label will overlap other objects in the diagram.
- Edge label mode(inactive when "None" is selected for Labeling)—choose one of the following styles:
As Is (default)—Retains labels as they are; they will not be altered.
Center—Places labels in the center of the relationships.
Side (default)—Places labels on the side of the relationships.
Free—Allows for unspecified label positions.