Summary

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

Details

Page properties

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5	The central operation of KWebS is {{code language="none"}}graphLayout{{/code}}, which is shown in the listing below. It calculates the layout of a graph that you deliver in serial notation as the {{code language="none"}}serializedGraph{{/code}} parameter. This parameter is declaring a general serial notation. The server has to know the underlying meta model and form of serialization, therefore, you have to define the //format// you used to submit your graph with the {{code language="none"}}informat{{/code}} parameter. In general, when the server has calculated the layout, it delivers the graph for which the layout was calculated in the same format that you chose to submit your source graph. Alternatively, you can define a different output format with the parameter {{code language="none"}}outformat{{/code}} and the server performs the necessary translation.
6	6
7		-There is a [[wiki page>>doc:Kieler.Discontinued Projects.Web Services (KWebS).Graph Formats.WebHome]] explaining the currently supported graph formats.
	7	+There is a [[wiki page>>doc:KIELER.Discontinued Projects.Web Services (KWebS).Graph Formats.WebHome]] explaining the currently supported graph formats.
8	8
9	9	{{code theme="Eclipse" language="java"}}
10	10	/**
...	...	@@ -45,7 +45,7 @@
45	45	String getServiceData();
46	46	{{/code}}
47	47
48		-When you use this operation, you receive a XML notation of the meta data. It is based on an //Ecore// meta model named //ServiceData//, which is shown by the next figure, and reuses the structure of the extension point {{code language="none"}}layoutProviders{{/code}} of [[KIML>>doc:Kieler.Discontinued Projects.Infrastructure for Meta Layout (KIML).WebHome]].
	48	+When you use this operation, you receive a XML notation of the meta data. It is based on an //Ecore// meta model named //ServiceData//, which is shown by the next figure, and reuses the structure of the extension point {{code language="none"}}layoutProviders{{/code}} of [[KIML>>doc:KIELER.Discontinued Projects.Infrastructure for Meta Layout (KIML).WebHome]].
49	49
50	50	[[image:attach:ServiceData.png]]
51	51
...	...	@@ -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.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