Summary

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

Details

Page properties

Content

...	...	@@ -109,10 +109,8 @@
109	109
110	110	= (% style="line-height: 1.4285715;" %)Programmatically Setting Layout Options(%%) =
111	111
	112	+{{id name="programmatic-config"/}}
112	112
113		-
114		-{{id name="programmatic-config"/}}\\
115		-
116	116	(% style="line-height: 1.4285715;" %)So with all these layout configurators available, how do you actually go about setting values for layout options programmatically? Well, as always: it depends.
117	117
118	118	== (% style="line-height: 1.4285715;" %)Using the Extension Point(%%) ==
...	...	@@ -168,4 +168,35 @@
168	168
169	169	A further use of diagram types is for the selection of layout algorithms: a layout algorithm may declare that is is especially suited to process diagrams of certain type //t//. If the diagram type //t// is assigned to a diagram viewer, the most suitable layout algorithm is chosen automatically for that viewer.
170	170
	169	+=== semanticConfig ===
	170	+
	171	+A {{code language="none"}}semanticConfig{{/code}} element registers a subclass of [[SemanticLayoutConfig>>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/SemanticLayoutConfig.java||shape="rect"]]:
	172	+
	173	+{{code language="xml"}}
	174	+ <semanticOption
	175	+ class="de.cau.cs.kieler.synccharts.Scope"
	176	+ config="de.cau.cs.kieler.synccharts.diagram.custom.AnnotationsLayoutConfig">
	177	+ </semanticOption>
	178	+{{/code}}
	179	+
	180	+Similarly to {{code language="none"}}staticConfig{{/code}} entries, the {{code language="none"}}class{{/code}} attribute refers to which model elements the configuration is applied. However, only domain model (a.k.a. //semantic// model) classes may be referenced. The {{code language="none"}}config{{/code}} attribute names a concrete implementation of the semantic layout configurator.
	181	+
	182	+The advantage of this kind of configuration compared to {{code language="none"}}staticConfig{{/code}} declarations is that it may perform arbitrary analyses of the domain model. For instance, different option values may be computed depending on certain properties of the domain model elements. This approach can be used to enable annotations of domain model elements. When the domain model is stored with a textual format, e.g. defined with [[Xtext>>url:http://www.eclipse.org/Xtext/||shape="rect"]], such annotations can be written in the source file that specifies the model:
	183	+
	184	+{{code}}
	185	+@portConstraints FIXED_SIDE
	186	+@minWidth 20.0
	187	+@minHeight 15.0
	188	+entity IdentityActor
	189	+{
	190	+ @portSide WEST
	191	+ port Input;
	192	+
	193	+ @portSide EAST
	194	+ port Output;
	195	+}
	196	+{{/code}}
	197	+
	198	+The source file annotations can be translated to KIML layout options with a semantic layout configurator, which is registered to each domain model class where annotations can occur.
	199	+
171	171

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-9469991
	1	+9469995

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9469991/Configuring Automatic Layout
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9469995/Configuring Automatic Layout