<
From version < 27.1 >
edited by wah
on 2012/10/15 11:17
To version < 12.1 >
edited by wah
on 2012/10/11 13:55
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,7 +35,7 @@
35 35  )))|(((
36 36  [[image:attach:image2012-10-11 13:52:3.png]]
37 37  )))|(((
38 -**YAKINDU**: Initials State are pseudo states. The Initial State may not be a Composite State. (% style="color: rgb(0,0,0);" %)An initial state can only have one outgoing transition and no incoming.
38 +**YAKINDU**: An extra State for Initial State. The Initial State may not be a Composite State
39 39  )))
40 40  |(((
41 41  Final State
... ... @@ -44,7 +44,7 @@
44 44  )))|(((
45 45  [[image:attach:image2012-10-11 13:51:43.png]]
46 46  )))|(((
47 -**YAKINDU**: Final States are pseudo states. The Final State may not be a Composite State
47 +**YAKINDU**: An extra State for Final State. The Final State may not be a Composite State
48 48  )))
49 49  |(((
50 50  State
... ... @@ -71,12 +71,9 @@
71 71  )))|(((
72 72  [[image:attach:image2012-10-11 13:47:54.png]]
73 73  )))|(((
74 -**YAKINDU**:
74 +**YAKINDU**: A History is a Pseudostate
75 75  
76 -* Shallow History: (% style="color: rgb(0,0,0);" %)is a pseudo state. It is placed inside a region of a composite state.
77 -* (% style="color: rgb(0,0,0);" %)Deep History: (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %) is similar to shallow history. With a deep history the latest state of multiple nested states is remembered.-
78 -
79 -**KIELER**: A History is a attribute of a Transition
76 +**KIELER**: A History is a Transition
80 80  )))
81 81  |(((
82 82  Synchronization
... ... @@ -96,54 +96,3 @@
96 96  )))|(((
97 97  
98 98  )))
99 -
100 -|=(((
101 -
102 -)))|=(((
103 -KIELER
104 -)))|=(((
105 -YAKINDU
106 -)))
107 -|(((
108 -Interface declaration
109 -)))|(((
110 -[[image:attach:image2012-10-12 10:59:54.png]]
111 -)))|(((
112 -[[image:attach:image2012-10-12 10:51:52.png]]
113 -)))
114 -
115 -= Yakindu SCT module structure =
116 -
117 -[[See Yakindu Wiki>>url:http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/plugins/org.yakindu.sct.doc.user/help/developer/01_Overview/overview.html||shape="rect"]]
118 -
119 -= Customizing Yakindu SCT Editor to SyncCharts =
120 -
121 -Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax:
122 -
123 -* adapting the graphical representation (sgraph)
124 -* extending or replacing the textual description language (stext)
125 -
126 -1. (((
127 -== Adapting the graphical representation ==
128 -
129 -(% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several step is required:(%%)
130 -(% style="color: rgb(0,0,0);" %) (%%)\\
131 -
132 -1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\
133 -11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]]
134 -11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]]
135 -\\
136 -1. Figures (org.yakindu.sct.ui.editor.editor.figures)
137 -\\
138 -1. Editparts (org.yakindu.sct.ui.editor.editparts)
139 -\\
140 -1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets)
141 -\\
142 -1. The palette (org.yakindu.sct.ui.editor/plugin.xml)
143 -\\
144 -)))
145 -1. (((
146 -== Extending or replacing the textual description language ==
147 -
148 -(% style="color: rgb(0,0,0);" %)The textual [[description language>>url:http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/plugins/org.yakindu.sct.doc.user/help/user/05_Reference/reference.html#Statechartdescriptionlanguage||shape="rect"]] is used to declare and describe behaviors in the state machine. It is case sensitive.
149 -)))
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -2982106
1 +2982051
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2982106/A SyncChart-Editor based on Yakindu
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2982051/A SyncChart-Editor based on Yakindu