Changes for page SCCharts-Editor based on Yakindu
Last modified by Richard Kreissig on 2023/09/14 11:09
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,8 +1,8 @@ 1 1 = Yakindu SCT = 2 2 3 -YAKINDU Statechart Tools (SCT) is an open source tool for the specification and development of reactive, event-based systems using state machines ([[Yakindu SCT User Guide>>attach:YAKINDU-SCT-UserGuide-1.2.0.pdf]]).3 +YAKINDU Statechart Tools (SCT) is an open source tool for the specification and development of reactive, event-based systems using state machines. 4 4 5 - YAKINDUSCTconsists of a graphical tool for editing and provides validation, simulation, and code generators for different target platforms. The tools are provided as Eclipse-plugins and integrate tightly into the IDE ([[Yakindu SCT Website>>url:http://www.itemis.de/itemis-ag/produkte/yakindu-open-source/yakindu-statechart-tools/language=de/43437/produktbeschreibung||shape="rect"]]).5 +It consists of a graphical tool for editing and provides validation, simulation, and code generators for different target platforms. The tools are provided as Eclipse-plugins and integrate tightly into the IDE ([[Yakindu SCT Website>>url:http://www.itemis.de/itemis-ag/produkte/yakindu-open-source/yakindu-statechart-tools/language=de/43437/produktbeschreibung||shape="rect"]]). 6 6 7 7 [[image:attach:Yakindu SCT.png]] 8 8 ... ... @@ -54,8 +54,6 @@ 54 54 [[image:attach:image2012-10-11 13:52:3.png]] 55 55 )))|((( 56 56 **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. 57 - 58 -(% style="color: rgb(0,0,0);" %)**KIELER**: Initial states are supposed to have a thicker border than normal states 59 59 ))) 60 60 |((( 61 61 Final State ... ... @@ -65,8 +65,6 @@ 65 65 [[image:attach:image2012-10-11 13:51:43.png]] 66 66 )))|((( 67 67 **YAKINDU**: Final States are pseudo states. The Final State may not be a Composite State 68 - 69 -**KIELER**: Final states are depicted with a double border 70 70 ))) 71 71 |((( 72 72 History ... ... @@ -89,13 +89,7 @@ 89 89 )))|((( 90 90 [[image:attach:image2012-10-11 13:47:49.png]] 91 91 )))|((( 92 -**YAKINDU**: Synchronization is a pseudo state. 93 - 94 -**KIELER**: Synchronization not needed in KIELER 95 - 96 -* 97 -** No interlevel transitions 98 -** Closest construct: normal termination 88 + 99 99 ))) 100 100 |((( 101 101 Choice ... ... @@ -130,36 +130,30 @@ 130 130 131 131 Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax: 132 132 133 -* adapting the graphical representation (sgraph + ui)123 +* adapting the graphical representation (sgraph) 134 134 * extending or replacing the textual description language (stext) 135 135 136 - (% style="margin-left: 30.0px;"%)126 +1. ((( 137 137 == Adapting the graphical representation == 138 138 139 -(% style=" margin-left:30.0px;"%)140 -(% style="color: rgb(0,0,0);" %) Toadapt the graphical representation, several steps are required:129 +(% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several step is required:(%%) 130 +(% style="color: rgb(0,0,0);" %) (%%)\\ 141 141 142 -* 143 -*1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\ 144 -*11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]] 145 -*11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]] 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]] 146 146 \\ 147 - *1. Figures (org.yakindu.sct.ui.editor.editor.figures)136 +1. Figures (org.yakindu.sct.ui.editor.editor.figures) 148 148 \\ 149 - *1. Editparts (org.yakindu.sct.ui.editor.editparts)138 +1. Editparts (org.yakindu.sct.ui.editor.editparts) 150 150 \\ 151 - *1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets)140 +1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets) 152 152 \\ 153 -*1. The palette (org.yakindu.sct.ui.editor/plugin.xml) 154 - 155 -(% style="margin-left: 60.0px;" %) 156 -**Examples:** 157 - 158 -* [[How to modify Initial and Finial States in Yakindu SCT Editor>>doc:How to modify Initial and Final States in Yakindu SCT Editor]] 159 -* [[doc:How to add Transition Types in Yakindu SCT Editor]] 160 - 161 -(% style="margin-left: 30.0px;" %) 142 +1. The palette (org.yakindu.sct.ui.editor/plugin.xml) 143 +\\ 144 +))) 145 +1. ((( 162 162 == Extending or replacing the textual description language == 163 163 164 -(% style="margin-left: 30.0px;" %) 165 165 (% 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 -2982 3581 +2982128 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2982 358/A SyncChart-Editor based on Yakindu1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2982128/A SyncChart-Editor based on Yakindu