Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -1,3 +1,9 @@
	1	+{{warning}}
	2	+We haven't finished writing this page yet.
	3	+{{/warning}}
	4	+
	5	+
	6	+
1	1	This page describes how layout options are applied by KIML during the layout process. After having read this, you should be able to answer the following questions:
2	2
3	3	* What are //layout options//?
...	...	@@ -16,7 +16,7 @@
16	16
17	17	= Layout Options and What They Are Good For =
18	18
19		-Even the most basic layout algorithm has some settings for you to play with. This might be something as simple as the space left between different nodes, or something as complex as changing how node labels are placed and how that influences the size of each node. Each such setting must be registered with KIML as a //layout option//, and each algorithm must specify exactly which of these options it supports. Registering a layout option is done through one of KIML's extension points and can look like this:
	25	+Even the most basic layout algorithm provides some settings for you to play with. This might be something as simple as the space left between different nodes, or something as complex as changing how node labels are placed and how that influences the size of each node. Each such setting must be registered with KIML as a //layout option//, and each algorithm must specify exactly which of these options it supports. Registering a layout option is done through one of KIML's extension points and can look like this:
20	20
21	21	{{code language="html/xml"}}
22	22	<extension point="de.cau.cs.kieler.kiml.layoutProviders">
...	...	@@ -73,13 +73,53 @@
73	73
74	74	= (% style="line-height: 1.4285715;" %)The Layout Options Manager(%%) =
75	75
76		-{{warning title="ToDo"}}
77		-Write this section.
78		-{{/warning}}
	82	+(% style="line-height: 1.4285715;" %)By now, we have an idea of what layout options do and why they are important in the first place. However, we haven't looked at how layout options end up on KGraph elements yet. This is where the [[{{code language="none"}}LayoutOptionsManager{{/code}}>>url:http://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/pragmatics/browse/plugins/de.cau.cs.kieler.kiml.ui/src/de/cau/cs/kieler/kiml/ui/service/LayoutOptionManager.java||shape="rect"]] comes in.
79	79
80		-(% style="line-height: 1.4285715;" %)
	84	+{{tip}}
	85	+The [[KIML page>>doc:Infrastructure for Meta Layout (KIML)]] has a high-level explanation of what happens when during the layout process. To take a look at it if you haven't already – it will make the following concepts easier to understand.
	86	+{{/tip}}
81	81
	88	+(% style="line-height: 1.4285715;" %)After a layout manager has finished turning a given diagram into its KGraph representation, the layout options manager is asked to enrich the KGraph elements with layout options. The option values can come from different sources: the user might have set some using the layout view; there might be some defaults for certain kinds of diagrams; or the programmer might have decided to attach some layout options to certain elements for just this one layout run. Whatever the source, the options manager is in charge of collecting all these layout option values and making sure they find their way to the correct KGraph element. To start off with a clean plate, it first makes sure there are no layout options attached to the KGraph elements. It then does two things: collect every eligible source of layout options, and transfer layout options to the correct KGraph elements. Sounds easy enough.
82	82
	90	+(% style="line-height: 1.4285715;" %)The question remains how the layout options sources work. Each source is represented by a class that implements the [[{{code language="none"}}ILayoutConfig{{/code}}>>url:https://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/pragmatics/browse/plugins/de.cau.cs.kieler.kiml/src/de/cau/cs/kieler/kiml/config/ILayoutConfig.java||shape="rect"]] interface, called a //layout configuration//. KIML currently provides the following layout configurations, each representing a particular source of layout options:
	91	+
	92	+* {{code language="none"}}DefaultLayoutConfig{{/code}} – Sets fixed default values defined for layout options.
	93	+* {{code language="none"}}EclipseLayoutConfig{{/code}} – Users can define default layout options to be set on elements that meet certain criteria via the KIML preference page. This layout configuration takes these options and applies them.
	94	+* {{code language="none"}}SemanticLayoutConfig{{/code}} – ???
	95	+* {{code language="none"}}GmfLayoutConfig{{/code}} / {{code language="none"}}GraphitiLayoutConfig{{/code}} – These configurations apply layout options set by the user in the layout view or stored in the notation model file of a diagram.
	96	+* {{code language="none"}}VolatileLayoutConfig{{/code}} – A configuration whose only purpose it is to make sure certain layout options are set on certain diagram elements in a particular layout run.
	97	+
	98	+The options manager collects all available and applicable layout configurations and sorts them by priority (incidentally, the configurations were sorted by increasing priority just now). For every graph element, each configuration is asked to provide layout options, starting with the default layout configuration and working through the priority chain.
	99	+
	100	+== A Few Details on Layout Configurations ==
	101	+
	102	+What we just learned is a bit of a simplification of what happens. The layout options manager not only asks each layout configuration to provide layout options for each graph element. Before we look at the details, let's take a look at the methods each layout configuration provides:
	103	+
	104	+{{code language="java"}}
	105	+public interface ILayoutConfig {
	106	+ int getPriority();
	107	+
	108	+ void enrich(LayoutContext context);
	109	+
	110	+ Object getValue(LayoutOptionData<?> optionData, LayoutContext context);
	111	+
	112	+ void transferValues(KLayoutData layoutData, LayoutContext context);
	113	+}
	114	+{{/code}}
	115	+
	116	+It is not hard to guess what {{code language="none"}}getPriority(){{/code}} does: it returns the priority a given layout configuration has. If two layout configurations set a layout option to different values on a given graph element, the value set by the configuration with lower priority gets overwritten. The other three methods look a bit more obscure, so we have to provide more details on what the options manager does, exactly.
	117	+
	118	+ENRICHING (+ WHAT IS A LAYOUT CONTEXT)
	119	+
	120	+TRANSFERRING
	121	+
	122	+GETVALUE (for the layout view?)
	123	+
	124	+== (% style="line-height: 1.4285715;" %)Implementing a Layout Configuration(%%) ==
	125	+
	126	+(% style="line-height: 1.4285715;" %)deciding what options are applicable depending on the context object; setting the options;
	127	+
	128	+
83	83	= (% style="line-height: 1.4285715;" %)Programmatically Setting Layout Options(%%) =
84	84
85	85	{{warning title="ToDo"}}

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-7700947
	1	+7700957

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7700947/Working With Layout Options
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7700957/Working With Layout Options