Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,7 +1,7 @@
1	1	{{panel title="Project Overview" borderStyle="dashed"}}
2	2	Responsible:
3	3
4		-* {{mention reference="XWiki.cds" style="FULL_NAME" anchor="XWiki-cds-gxWPf"/}}
	4	+* {{mention reference="XWiki.cds" style="FULL_NAME" anchor="XWiki-cds-WDonl"/}}
5	5
6	6	Key Publications:
7	7
...	...	@@ -100,4 +100,20 @@
100	100	1. With a layout computed for each connected component, the ComponentsProcessor is invoked again to join them together. The processor can use one of two implementations of the AbstractGraphPlacer class: SimpleRowGraphPlacer simply places the connected components in rows, trying to adhere to the required aspect ratio. The ComponentGroupGraphPlacer is more sophisticated and tries to work around problems with connected components processing in compound nodes.
101	101	1. Finally, it again uses one of the IGraphImporter implementations to apply the computed layout back to the KGraph.
102	102
103		-
	103	+= Example Layouts =
	104	+
	105	+Below some example diagrams that were layouted with the KLay Layered algorithm.
	106	+
	107	+== Ptolemy Diagram ==
	108	+
	109	+[[image:attach:ptolemy.png]]
	110	+
	111	+== SCChart with Dataflow ==
	112	+
	113	+(% style="text-align: left;" %)
	114	+[[image:attach:scchartsdataflow.png]]
	115	+
	116	+(% style="text-align: left;" %)
	117	+== SCG ==
	118	+
	119	+[[image:attach:scg.png]]

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-10751406
	1	+10751773

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/10751406/KLay Layered
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/10751773/KLay Layered