Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.uru
	1	+XWiki.als

Content

...	...	@@ -58,7 +58,7 @@
58	58	* {{code language="none"}}LayoutType{{/code}} declares the general type of layout an algorithm computes, e.g. //circular// or //orthogonal// layout. Again, the attributes {{code language="none"}}name{{/code}} and {{code language="none"}}description{{/code}} provide the name and additional textual information.
59	59
60	60	* (((
61		-{{code language="none"}}LayoutOption{{/code}} declares a layout option. The attribute {{code language="none"}}type{{/code}} defines the type of values you may assign to this option, e.g. boolean, string or enumeration values. Additionaly, the attribute {{code language="none"}}default{{/code}} may carry a default value which generally provides good layout results. As said before, a layout option is related to specific types of graph elements, specified by the attribute {{code language="none"}}appliesTo{{/code}}. It may be empty, meaning, an option can be applied to any element, or contain a comma separated list of compatible element types. The attribute {{code language="none"}}id{{/code}} declares the identifier of the layout option. You can use it to specify a layout option directly in the source graph by annotating a specific graph element. The way you realize the annotation is dependent on the model you use. For example, if you use a [[KGraph>>doc:KIELER.Home.Discontinued Projects.Infrastructure for Meta Layout (KIML).KGraph Meta Model.WebHome]] model, you could do it like the following listing shows:
	61	+{{code language="none"}}LayoutOption{{/code}} declares a layout option. The attribute {{code language="none"}}type{{/code}} defines the type of values you may assign to this option, e.g. boolean, string or enumeration values. Additionaly, the attribute {{code language="none"}}default{{/code}} may carry a default value which generally provides good layout results. As said before, a layout option is related to specific types of graph elements, specified by the attribute {{code language="none"}}appliesTo{{/code}}. It may be empty, meaning, an option can be applied to any element, or contain a comma separated list of compatible element types. The attribute {{code language="none"}}id{{/code}} declares the identifier of the layout option. You can use it to specify a layout option directly in the source graph by annotating a specific graph element. The way you realize the annotation is dependent on the model you use. For example, if you use a [[KGraph>>doc:Kieler.Discontinued Projects.Infrastructure for Meta Layout (KIML).KGraph Meta Model.WebHome]] model, you could do it like the following listing shows:
62	62
63	63	{{code theme="Eclipse" language="java"}}
64	64	// Retrieve the graph model somehow
...	...	@@ -83,7 +83,7 @@
83	83	shapeLayout.setProperty(algorithm, "de.cau.cs.kieler.graphviz.dot");
84	84	{{/code}}
85	85
86		-You could alternatively use the {{code language="none"}}options{{/code}} parameter of the {{code language="none"}}graphLayout{{/code}} operation to declare a specific layout algorithm, as you can see in the next listing. The {{code language="none"}}layoutServicePort{{/code}} instance the example uses resembles the //proxy// necessary to interact with the layout server. You will see how you can create such a proxy in [[How to use the service based layout in your project>>doc:How to Use the Service-Based Layout in Your Project]].
	86	+You could alternatively use the {{code language="none"}}options{{/code}} parameter of the {{code language="none"}}graphLayout{{/code}} operation to declare a specific layout algorithm, as you can see in the next listing. The {{code language="none"}}layoutServicePort{{/code}} instance the example uses resembles the //proxy// necessary to interact with the layout server. You will see how you can create such a proxy in [[How to use the service based layout in your project>>doc:KIELER.How to Use the Service-Based Layout in Your Project]].
87	87
88	88	{{code theme="Eclipse" language="java"}}
89	89	// Retrieve the graph model somehow