Updated user guide structure

plugins/org.yakindu.sct.doc.user/.settings/org.eclipse.core.resources.prefs

@@ -1,11 +1,9 @@
 eclipse.preferences.version=1
 encoding//help/01_Overview/overview.html=utf-8
-encoding//help/Tutorial/tutorial-toc.xml=utf-8
-encoding//help/Tutorial/tutorial.html=utf-8
-encoding//help/user/02_Getting_Started/getting_started.html=utf-8
-encoding//help/user/03_Concepts/concepts.html=utf-8
-encoding//help/user/04_Tasks/tasks-toc.xml=utf-8
-encoding//help/user/04_Tasks/tasks.html=utf-8
-encoding//help/user/05_Reference/reference-toc.xml=utf-8
-encoding//help/user/05_Reference/reference.html=utf-8
+encoding//help/02_Getting_started/tutorial-toc.xml=utf-8
+encoding//help/02_Getting_started/tutorial.html=utf-8
+encoding//help/03_Tasks/tasks-toc.xml=utf-8
+encoding//help/03_Tasks/tasks.html=utf-8
+encoding//help/04_Reference/reference-toc.xml=utf-8
+encoding//help/04_Reference/reference.html=utf-8
 encoding/<project>=UTF-8

plugins/org.yakindu.sct.doc.user/build.properties

@@ -5,5 +5,4 @@ bin.includes = plugin.xml,\
                about.html,\
                about.ini,\
                about.mappings,\
-               about.properties,\
-               YAKINDU_OSS_32.png
+               about.properties

plugins/org.yakindu.sct.doc.user/help/02_Getting_started/tutorial-toc.xml

@@ -0,0 +1,16 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="help/02_Getting_started/tutorial.html" label="tutorial">
+	<topic href="help/02_Getting_started/tutorial.html" label="Getting started tutorial ">
+		<topic href="help/02_Getting_started/tutorial.html#Installation" label="Installation"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#InstallingtheYAKINDUPlugIns" label="Installing the YAKINDU-Plug-Ins"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#Introduction" label="Introduction"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#CallHandlingexampleexplained" label="CallHandling example explained"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#Prepareaproject" label="Prepare a project"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#Createastatechartmodel" label="Create a statechart model"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#UsetheEditor" label="Use the Editor"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#Simulatingthemodel" label="Simulating the model"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#GenerateJavacode" label="Generate Java code"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#Integrationwithclientcode" label="Integration with client code"></topic>
+		<topic href="help/02_Getting_started/tutorial.html#Weblinks" label="Weblinks"></topic>
+	</topic>
+</toc>

plugins/org.yakindu.sct.doc.user/help/Tutorial/tutorial.textile

@@ -4,6 +4,26 @@
 
 h1. Getting started tutorial 
 
+h3. Installation
+
+The *Yakindu Statechart Tools* are built upon Java and Xtext. So you need to have installed a "Java Runtime Environment":http://www.oracle.com/technetwork/java/index.html and Xtext installed. The easier way to get this is to install the "pre configured Xtext contribution":http://xtext.itemis.com.
+
+The *Yakindu Statechart Tools 2* need *Eclipse Indigo 3.7* or higher and *Xtext 2.0.1* exactly (no higher) to work correctly.
+
+h3. Installing the YAKINDU-Plug-Ins
+
+You install the Yakindu Plug-Ins from the update site: http://updates.yakindu.com/indigo/milestones. 
+
+* Click *Help* > *Install new software...* and *Add..* the update site _Yakindu SCT2 milestones_ - http://updates.yakindu.com/indigo/milestones/
+* Check all to install the YAKINDU SCT2
+* Click *Next* to start the installation and click *Next* at the next step
+* Accept the licence agreement and click *Finish*
+* The software will be installed
+
+When the installation finished the wizard will ask to reopen Eclipse. The restart is important to make the newly installed software work correctly.
+
+!images/updatesite_4.jpg!
+
 h3. Introduction
 
 This tutorial will introduce the open source project Yakindu Statechart Tools (SCT).YAKINDU Statechart Tools provides an integrated modeling environment for the specification and development of reactive, event-driven systems based on the concept of statecharts. It is an easy to use tool that features sophisticated graphical state chart editing, validation and simulation of statecharts as well as code generation.

plugins/org.yakindu.sct.doc.user/help/03_Tasks/tasks-toc.xml

@@ -0,0 +1,33 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="help/03_Tasks/tasks.html" label="tasks">
+	<topic href="help/03_Tasks/tasks.html" label="Tasks">
+		<topic href="help/03_Tasks/tasks.html#Modelingastatemachine" label="Modeling a statemachine">
+			<topic href="help/03_Tasks/tasks.html#Relatedtopics" label="Related topics"></topic>
+		</topic>
+		<topic href="help/03_Tasks/tasks.html#Validatingastatemachine" label="Validating a statemachine"></topic>
+		<topic href="help/03_Tasks/tasks.html#Simulatingastatemachine" label="Simulating a statemachine"></topic>
+		<topic href="help/03_Tasks/tasks.html#GeneratingCode" label="Generating Code"></topic>
+		<topic href="help/03_Tasks/tasks.html#CoreFeatures" label="Core Features">
+			<topic href="help/03_Tasks/tasks.html#Outlet" label="Outlet"></topic>
+			<topic href="help/03_Tasks/tasks.html#LicenseHeader" label="LicenseHeader"></topic>
+			<topic href="help/03_Tasks/tasks.html#FunctionInlining" label="FunctionInlining"></topic>
+			<topic href="help/03_Tasks/tasks.html#Debug" label="Debug"></topic>
+		</topic>
+		<topic href="help/03_Tasks/tasks.html#JavaGeneratorFeatures" label="Java Generator Features">
+			<topic href="help/03_Tasks/tasks.html#Naming" label="Naming"></topic>
+			<topic href="help/03_Tasks/tasks.html#GeneralFeatures" label="GeneralFeatures"></topic>
+		</topic>
+		<topic href="help/03_Tasks/tasks.html#CGeneratorFeatures" label="C Generator Features">
+			<topic href="help/03_Tasks/tasks.html#CCodeFeature" label="CCodeFeature"></topic>
+		</topic>
+		<topic href="help/03_Tasks/tasks.html#CreateCustomCodeGenerators" label="Create Custom Code Generators">
+			<topic href="help/03_Tasks/tasks.html#WritingacustomcodegeneratorwithXtend2Java" label="Writing a custom code generator with Xtend2/Java"></topic>
+			<topic href="help/03_Tasks/tasks.html#ExecutingacustomXtend2Javacodegenerator" label="Executing a custom Xtend2/Java code generator">
+				<topic href="help/03_Tasks/tasks.html#Generator" label="Generator"></topic>
+			</topic>
+			<topic href="help/03_Tasks/tasks.html#ExecutingacustomXpandcodegenerator" label="Executing a custom Xpand code generator">
+				<topic href="help/03_Tasks/tasks.html#Template" label="Template"></topic>
+			</topic>
+		</topic>
+	</topic>
+</toc>

plugins/org.yakindu.sct.doc.user/help/04_Reference/reference-toc.xml

@@ -0,0 +1,85 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="help/04_Reference/reference.html" label="reference">
+	<topic href="help/04_Reference/reference.html" label="YAKINDU SCT 2 Reference">
+		<topic href="help/04_Reference/reference.html#Statechartelements" label="State chart elements">
+			<topic href="help/04_Reference/reference.html#Regions" label="Regions"></topic>
+			<topic href="help/04_Reference/reference.html#States" label="States"></topic>
+			<topic href="help/04_Reference/reference.html#Transitions" label="Transitions"></topic>
+			<topic href="help/04_Reference/reference.html#Initialstateandfinalstate" label="Initial state and final state"></topic>
+			<topic href="help/04_Reference/reference.html#Choice" label="Choice"></topic>
+			<topic href="help/04_Reference/reference.html#Junction" label="Junction"></topic>
+			<topic href="help/04_Reference/reference.html#CompositeState" label="Composite State">
+				<topic href="help/04_Reference/reference.html#Orthogonalstates" label="Orthogonal states"></topic>
+				<topic href="help/04_Reference/reference.html#Submachinestates" label="Submachine states"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#ShallowHistory" label="Shallow History"></topic>
+			<topic href="help/04_Reference/reference.html#DeepHistory" label="Deep History"></topic>
+		</topic>
+		<topic href="help/04_Reference/reference.html#Statechartdescriptionlanguage" label="Statechart description language">
+			<topic href="help/04_Reference/reference.html#Typesystem" label="Typesystem"></topic>
+			<topic href="help/04_Reference/reference.html#Expressions" label="Expressions">
+				<topic href="help/04_Reference/reference.html#LogicalAND" label="Logical AND"></topic>
+				<topic href="help/04_Reference/reference.html#LogicalOR" label="Logical OR"></topic>
+				<topic href="help/04_Reference/reference.html#LogicalNOT" label="Logical NOT"></topic>
+				<topic href="help/04_Reference/reference.html#Conditionalexpression" label="Conditional expression"></topic>
+				<topic href="help/04_Reference/reference.html#BitwiseXOR" label="Bitwise XOR"></topic>
+				<topic href="help/04_Reference/reference.html#BitwiseOR" label="Bitwise OR"></topic>
+				<topic href="help/04_Reference/reference.html#BitwiseAND" label="Bitwise AND"></topic>
+				<topic href="help/04_Reference/reference.html#LogicalRelationsandShiftOperators" label="Logical Relations and Shift Operators"></topic>
+				<topic href="help/04_Reference/reference.html#Binaryarithmeticoperators" label="Binary arithmetic operators"></topic>
+				<topic href="help/04_Reference/reference.html#Unaryarithmeticoperators" label="Unary arithmetic operators"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#Statements" label="Statements"></topic>
+			<topic href="help/04_Reference/reference.html#Scopes" label="Scopes">
+				<topic href="help/04_Reference/reference.html#Namespace" label="Namespace"></topic>
+				<topic href="help/04_Reference/reference.html#interfacescope" label="interface scope"></topic>
+				<topic href="help/04_Reference/reference.html#internalscope" label="internal scope"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#Declarations" label="Declarations"></topic>
+			<topic href="help/04_Reference/reference.html#Events" label="Events"></topic>
+			<topic href="help/04_Reference/reference.html#Variables" label="Variables"></topic>
+			<topic href="help/04_Reference/reference.html#ReactionTriggers" label="Reaction Triggers">
+				<topic href="help/04_Reference/reference.html#after" label="after"></topic>
+				<topic href="help/04_Reference/reference.html#every" label="every"></topic>
+				<topic href="help/04_Reference/reference.html#always" label="always"></topic>
+				<topic href="help/04_Reference/reference.html#defaultelse" label="default, else"></topic>
+				<topic href="help/04_Reference/reference.html#entry" label="entry"></topic>
+				<topic href="help/04_Reference/reference.html#exit" label="exit"></topic>
+				<topic href="help/04_Reference/reference.html#oncycle" label="oncycle"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#Operations" label="Operations"></topic>
+			<topic href="help/04_Reference/reference.html#BuildInFunctions" label="Build-In Functions">
+				<topic href="help/04_Reference/reference.html#valueofevent" label="valueof(event)"></topic>
+				<topic href="help/04_Reference/reference.html#activestate" label="active(state)"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#LocalReactions" label="LocalReactions"></topic>
+			<topic href="help/04_Reference/reference.html#EntryPoints" label="EntryPoints"></topic>
+			<topic href="help/04_Reference/reference.html#ExitPoints" label="ExitPoints"></topic>
+		</topic>
+		<topic href="help/04_Reference/reference.html#SGraph" label="SGraph"></topic>
+		<topic href="help/04_Reference/reference.html#SExec" label="SExec"></topic>
+		<topic href="help/04_Reference/reference.html#SGen" label="SGen">
+			<topic href="help/04_Reference/reference.html#GeneratormodelforJava" label="Generator model for Java">
+				<topic href="help/04_Reference/reference.html#FeatureOutlet" label="Feature Outlet"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureLicenseHeader" label="Feature LicenseHeader"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureDebug" label="Feature Debug"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureFunctionInlining" label="Feature FunctionInlining"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureGeneralFeatures" label="Feature GeneralFeatures"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureNaming" label="Feature Naming"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#GeneratormodelforC" label="Generator model for C">
+				<topic href="help/04_Reference/reference.html#FeatureOutlet2" label="Feature Outlet"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureLicenseHeader2" label="Feature LicenseHeader"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureDebug2" label="Feature Debug"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureCCodeFeature" label="Feature CCodeFeature"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureFunctionInlining2" label="Feature FunctionInlining"></topic>
+			</topic>
+			<topic href="help/04_Reference/reference.html#GeneratormodelforC2" label="Generator model for C++">
+				<topic href="help/04_Reference/reference.html#FeatureOutlet3" label="Feature Outlet"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureLicenseHeader3" label="Feature LicenseHeader"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureDebug3" label="Feature Debug"></topic>
+				<topic href="help/04_Reference/reference.html#FeatureFunctionInlining3" label="Feature FunctionInlining"></topic>
+			</topic>
+		</topic>
+	</topic>
+</toc>

plugins/org.yakindu.sct.doc.user/help/Tutorial/tutorial-toc.xml

@@ -1,14 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/Tutorial/tutorial.html" label="tutorial">
-	<topic href="help/Tutorial/tutorial.html" label="Getting started tutorial ">
-		<topic href="help/Tutorial/tutorial.html#Introduction" label="Introduction"></topic>
-		<topic href="help/Tutorial/tutorial.html#CallHandlingexampleexplained" label="CallHandling example explained"></topic>
-		<topic href="help/Tutorial/tutorial.html#Prepareaproject" label="Prepare a project"></topic>
-		<topic href="help/Tutorial/tutorial.html#Createastatechartmodel" label="Create a statechart model"></topic>
-		<topic href="help/Tutorial/tutorial.html#UsetheEditor" label="Use the Editor"></topic>
-		<topic href="help/Tutorial/tutorial.html#Simulatingthemodel" label="Simulating the model"></topic>
-		<topic href="help/Tutorial/tutorial.html#GenerateJavacode" label="Generate Java code"></topic>
-		<topic href="help/Tutorial/tutorial.html#Integrationwithclientcode" label="Integration with client code"></topic>
-		<topic href="help/Tutorial/tutorial.html#Weblinks" label="Weblinks"></topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/developer/01_Overview/overview-toc.xml

@@ -1,6 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/developer/01_Overview/overview.html" label="overview">
-	<topic href="help/developer/01_Overview/overview.html" label="Overview">
-		<topic href="help/developer/01_Overview/overview.html#Howdoesitwork" label="How does it work?"></topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/developer/01_Overview/overview.html

@@ -1,40 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>overview</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<h1 id="Overview">Overview</h1>
-		<h2 id="Howdoesitwork">How does it work?</h2>
-		<p>The YAKINDU SCT 2 are integrated in Eclipse and use the textual modeling toolkit Xtext and the graphical modeling toolkit GMF. Behind the scenes of the statechart tools there are some meta models: </p>
-		<ul>
-			<li>
-				<strong>SText</strong> the meta model for the state machines and their behavior
-			</li>
-			<li>
-				<strong>SGraph</strong> the meta model for the graphical representation of the state machine models
-			</li>
-			<li>
-				<strong>SExec</strong> an intermediate model for execution
-			</li>
-			<li>
-				<strong>SGen</strong> an intermediate model used for generating
-			</li>
-		</ul>
-		<p>The following graph shows these meta models, which are all defined as languages and their position in the SCT 2 work flow:</p>
-		<p>
-			<img border="0" src="images/overview_yakindu_modules_tech.jpg"/>
-		</p>
-		<p>The statechart editor uses 
-			<strong>SText</strong> and 
-			<strong>SGraph</strong>. The actual model of the state machine is defined in 
-			<strong>SText</strong>. 
-			<strong>SGraph</strong> only describes the graphical representation in the editor. 
-			<strong>SExec</strong> is an intermediate execution model. It is used behind the scenes as a foundation for the code generators and the simulation engine. This guarantees that the simulation behaves in the same way as the generated statechart implementations. It captures the execution behavior and may also serve as the basis of custom code generators. 
-			<strong>SGen</strong> is a generator model. All generators can be customized with such a generator model. In fact it is a textual model file where generator features, like i.e. the outlet path, can be specified.
-		</p>
-		<p>The YAKINDU SCT 2 can be installed in a full blown Eclipse-IDE specifically tailored for your language. It already provides great default functionality for all aspects and allows to configure  the most common things very easily. </p>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/developer/02_Getting_Started/getting_started-toc.xml

@@ -1,7 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/developer/02_Getting_Started/getting_started.html" label="getting_started">
-	<topic href="help/developer/02_Getting_Started/getting_started.html" label="Developer Getting started">
-		<topic href="help/developer/02_Getting_Started/getting_started.html#YakinduXpandGeneratorProject" label="Yakindu Xpand Generator Project"></topic>
-		<topic href="help/developer/02_Getting_Started/getting_started.html#YakinduXtend2JavaGeneratorProject" label="Yakindu Xtend2/Java Generator Project"></topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/developer/02_Getting_Started/getting_started.html

@@ -1,43 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>getting_started</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<h1 id="DeveloperGettingstarted">Developer Getting started</h1>
-		<h2 id="YakinduXpandGeneratorProject">Yakindu Xpand Generator Project</h2>
-		<p>In the context of model driven software development generators play an important role. The generator transforms the model to either another model or text like code. Yakindu generators support multiple transform languages. One is Xpand. By clicking 
-			<strong>File</strong> &gt; 
-			<strong>New</strong> &gt; 
-			<strong>Other...</strong> &gt; 
-			<strong>YAKINDU Xpand Generator Project</strong> you create a project optimized for writing a generator in Xpand. For more details regarding Xpand see: 
-			<a href="PLUGIN_ROOT/org.eclipse.xpand.doc/help/index.html">Xpand documentation</a>.
-		</p>
-		<p>
-			<img border="0" src="images/new_xpand_project_simple.jpg"/>
-		</p>
-		<p>All you need to do is to give it a speaking name and click 
-			<strong>Finish</strong>. The setting 
-			<strong>Configure for Plugin Export</strong> is an option for plugin developers.
-		</p>
-		<p>The newly created project has a package with an Xpand starting point: the 
-			<em>Main.xpt</em>. This file the includes the needed metamodels. It has the entrance Xpand statement that iterates all states in the model and prints the names in a text file.
-		</p>
-		<h2 id="YakinduXtend2JavaGeneratorProject">Yakindu Xtend2/Java Generator Project</h2>
-		<p>The generator that transforms the state machine model into code or documentation can be written in Xtend2 and Java. Find a detailed description on Xtend2 in the 
-			<a href="PLUGIN_ROOT/org.eclipse.xtext.doc/contents/01-Xtend_Introduction.html">Xtend2 documentation</a>. Yakindu comes with a predefined project setting for such projects. To create such a project click 
-			<strong>File</strong> &gt; 
-			<strong>New</strong> &gt; 
-			<strong>Other...</strong> &gt; 
-			<strong>YAKINDU Xtend2/Java Generator Project</strong>. 
-		</p>
-		<p>
-			<img border="0" src="images/new_java_xtend_project.jpg"/>
-		</p>
-		<p>Give the project a speaking full qualified name and name also the generator java class with a full qualified name. If you also want to use Xtend select 
-			<strong>Use Xtend</strong>. The result is a new project with an initial Xtend file and java class.
-		</p>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/developer/02_Getting_Started/getting_started.textile

@@ -1,19 +0,0 @@
-h1. Developer Getting started
-
-h2. Yakindu Xpand Generator Project
-
-In the context of model driven software development generators play an important role. The generator transforms the model to either another model or text like code. Yakindu generators support multiple transform languages. One is Xpand. By clicking *File* > *New* > *Other...* > *YAKINDU Xpand Generator Project* you create a project optimized for writing a generator in Xpand. For more details regarding Xpand see: "Xpand documentation":PLUGIN_ROOT/org.eclipse.xpand.doc/help/index.html.
-
-!images/new_xpand_project_simple.jpg!
-
-All you need to do is to give it a speaking name and click *Finish*. The setting *Configure for Plugin Export* is an option for plugin developers.
-
-The newly created project has a package with an Xpand starting point: the _Main.xpt_. This file the includes the needed metamodels. It has the entrance Xpand statement that iterates all states in the model and prints the names in a text file.
-
-h2. Yakindu Xtend2/Java Generator Project
-
-The generator that transforms the state machine model into code or documentation can be written in Xtend2 and Java. Find a detailed description on Xtend2 in the "Xtend2 documentation":PLUGIN_ROOT/org.eclipse.xtext.doc/contents/01-Xtend_Introduction.html. Yakindu comes with a predefined project setting for such projects. To create such a project click *File* > *New* > *Other...* > *YAKINDU Xtend2/Java Generator Project*. 
-
-!images/new_java_xtend_project.jpg!
-
-Give the project a speaking full qualified name and name also the generator java class with a full qualified name. If you also want to use Xtend select *Use Xtend*. The result is a new project with an initial Xtend file and java class.

plugins/org.yakindu.sct.doc.user/help/developer/03_Concepts/concepts-toc.xml

@@ -1,9 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/developer/03_Concepts/concepts.html" label="concepts">
-	<topic href="help/developer/03_Concepts/concepts.html" label="Developer Concepts">
-		<topic href="help/developer/03_Concepts/concepts.html#APIspecificationsofthegeneratedcode" label="API specifications of the generated code">
-			<topic href="help/developer/03_Concepts/concepts.html#SpecificationsofJavacode" label="Specifications of Java code"></topic>
-			<topic href="help/developer/03_Concepts/concepts.html#SpecificationsofCcode" label="Specifications of C code"></topic>
-		</topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/developer/03_Concepts/concepts.html

@@ -1,112 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>concepts</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<p><link href="../../../css/bootstrap.css" rel="stylesheet" />
-			<br/><link href="../../../css/custom.css" rel="stylesheet" />
-		</p>
-		<h1 id="DeveloperConcepts">Developer Concepts</h1>
-		<h2 id="APIspecificationsofthegeneratedcode">API specifications of the generated code</h2>
-		<p>In the following comments the TrafficLight example statemachine is used to describe the API specifications of the code generated by the Yakindu C and Java code generators. The following image shows the statechart. It is a model of a simple pedestrian crossing with a traffic light for pedestrians and a traffic light for the cars.</p>
-		<p>
-			<img border="0" src="images/TrafficLight.png"/> 
-		</p>
-		<p>For Java you can checkout the project &#8218;org.yakindusct.examples.trafficlight&#8217; from the Yakindu google code repository ( 
-			<a href="http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/examples">Google code link</a> ). The Java example contains the statechart, sgen model, graphical widgets and some glue code to connect the generated code with the widgets. The graphical widgets are based on SWT. To execute the Java example you can run the file &#8218;CrossingDemoCycleBased.java&#8217; as &#8218;Java Application&#8217; from the eclipse &#8218;Run As&#8217; context menu.
-		</p>
-		<p>For C you can checkout the project &#8218;org.yakindu.examples.c.trafficlight&#8217; from the Yakindu google code repository ( 
-			<a href="http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/examples">Google code link</a> ). The C example contains the statechart, sgen model, graphical widgets and some glue code to connect the generated code with the widgets. The graphical widgets are based on Qt. To execute the c example you can run the file org_yakindu_sct_examples_c_trafficlight as &#8218;Local C/C++ application&#8217; from the eclipse &#8218;Run As&#8217; context menu.
-		</p>
-		<h3 id="SpecificationsofJavacode">Specifications of Java code</h3>
-		<p>You find the generated code in the &#8218;src-gen&#8217; folder of the traffic light example.</p>
-		<p>In the package &#8218;org.yakindu.sct.examples.trafficlight.cyclebased&#8217; are the most basic statemachine interfaces and classes located. These are needed by each statemachine and are independend from the concrete statemachine design.</p>
-		<p>The interface 
-			<code>IStatemachine</code> is implemented by each generated statemachine:
-		</p>
-		<pre><code>package org.yakindu.sct.examples.trafficlight.cyclebased;
-
-/**
- * Basic interface for statemachines.
- * 
- * 
- */
-public interface IStatemachine {
-
-	/**
-	* Initializes the statemachine. Use to init internal variables etc.
-	*/
-	public void init();
-
-	/**
-	* Enters the statemachine. Sets the statemachine in a defined state.
-	*/
-	public void enter();
-
-	/**
-	* Exits the statemachine. Leaves the statemachine with a defined state.
-	*/
-	public void exit();
-
-	/**
-	* Start a run-to-completion cycle.
-	*/
-	public void runCycle();
-}
-</code></pre>
-		<p>It contains the four methods 
-			<code>init()</code>, 
-			<code>enter()</code>, 
-			<code>exit()</code> and 
-			<code>runCycle()</code>. The 
-			<code>init()</code> method is used to initialize the internal objects of the statemachine after instantiation. Variables are initialized to a default value. If you have initialized variables in the statechart definition these initializations are done in the init method too. The 
-			<code>enter()</code> method should be called if the statemachine is entered. It sets the statemachine into a defined state. The 
-			<code>exit()</code> method is used to leave a statemachine statefully. If for example a history state is used in one of the top regions the last active state is stored and the statemachine is leaved via 
-			<code>exit()</code> and reentered via 
-			<code>enter()</code> it continues working with this state. The 
-			<code>runCycle()</code> method is used to trigger a run to completion step in which the statemachine evaluates arising events and computes possible state changes.
-		</p>
-		<p>In the traffic light example timing is used (after clauses). To support this the interfaces &#8218;ITimedStatemachine&#8217;, &#8218;ITimerService&#8217; and the class &#8218;TimeEvent&#8217; are generated.</p>
-		<pre><code>package org.yakindu.sct.examples.trafficlight.cyclebased;
-
-/**
-* Interface for state machines which use timed event triggers.
-*/
-public interface ITimedStatemachine {
-
-	/**
-	* Set the {@link ITimerService} for the state machine. It must be set
-	* externally on a timed state machine before a run cycle can be correct
-	* executed.
-	* 
-	* @param timerService
-	*/
-	public void setTimerService(ITimerService timerService);
-
-	/**
-	* Returns the currently used timer service.
-	* 
-	* @return {@link ITimerService}
-	*/
-	public ITimerService getTimerService();
-
-	/**
-	* Callback method if a {@link TimeEvent} occurred.
-	* 
-	* @param timeEvent
-	*/
-	public void onTimeEventRaised(TimeEvent timeEvent);
-}
-</code></pre>
-		<p>
-			<code>ITimedStatemachine</code> extends the generated statemachine to set a 
-			<code>ITimerService</code> and provides a callback method 
-			<code>onTimeEventRaised(TimeEvent timeEvent)</code> to raise 
-			<code>TimeEvents</code>.
-		</p>
-		<h3 id="SpecificationsofCcode">Specifications of C code</h3>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/developer/04_Tasks/tasks-toc.xml

@@ -1,4 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/developer/04_Tasks/tasks.html" label="tasks">
-	<topic href="help/developer/04_Tasks/tasks.html" label="Developer Tasks"></topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/developer/04_Tasks/tasks.html

@@ -1,11 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>tasks</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<h1 id="DeveloperTasks">Developer Tasks</h1>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/developer/04_Tasks/tasks.textile

@@ -1 +0,0 @@
-h1. Developer Tasks

plugins/org.yakindu.sct.doc.user/help/developer/05_Reference/reference-toc.xml

@@ -1,4 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/developer/05_Reference/reference.html" label="reference">
-	<topic href="help/developer/05_Reference/reference.html" label="Reference"></topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/developer/05_Reference/reference.html

@@ -1,11 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>reference</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<h1 id="Reference">Reference</h1>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/developer/05_Reference/reference.textile

@@ -1 +0,0 @@
-h1. Reference

plugins/org.yakindu.sct.doc.user/help/style.css

@@ -1,49 +0,0 @@
-@CHARSET "UTF-8";
-/* use this statement to integrate the stylesheet to all html filed manually :( 
-<link rel="stylesheet" type="text/css" href="../style.css"></link>
-*/
-
-
-
-li img {
-	display: block;
-	margin-top: 0.5ex;
-	margin-bottom: 0.5ex;
-}
-
-code{ 
- border: 1px solid #bbb;
-padding: 7px;
-margin-right:10px;
-margin-left:5px;
-display:block;
-color:#6d0479;
-}
-
-li code {
-display:inline;
-border:0px;
-margin:0px;
-color:#000;
-}
-
-h2 {
-margin-top:85px;
-}
-
-h4 {
-margin-top:10px;
-}
-
-table {
-width: 80%;
-margin-left:5px;
-margin-right:10px;
-
-}
-
-td, th {
-border : 1px solid #bbb;
-padding: 7px;
-}
-

plugins/org.yakindu.sct.doc.user/help/user/02_Getting_Started/getting_started-toc.xml

@@ -1,14 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/user/02_Getting_Started/getting_started.html" label="getting_started">
-	<topic href="help/user/02_Getting_Started/getting_started.html" label="Getting started">
-		<topic href="help/user/02_Getting_Started/getting_started.html#Installation" label="Installation">
-			<topic href="help/user/02_Getting_Started/getting_started.html#Prerequisites" label="Prerequisites"></topic>
-			<topic href="help/user/02_Getting_Started/getting_started.html#InstallingtheYAKINDUPlugIns" label="Installing the YAKINDU-Plug-Ins"></topic>
-		</topic>
-		<topic href="help/user/02_Getting_Started/getting_started.html#Firststepsmyfirststatemachine" label="First steps: my first state machine">
-			<topic href="help/user/02_Getting_Started/getting_started.html#CreatingaNewProject" label="Creating a New Project"></topic>
-			<topic href="help/user/02_Getting_Started/getting_started.html#DefiningaStateMachine" label="Defining a State Machine"></topic>
-			<topic href="help/user/02_Getting_Started/getting_started.html#SimulatingtheStateMachine" label="Simulating the State Machine"></topic>
-		</topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/user/02_Getting_Started/getting_started.html

@@ -1,200 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>getting_started</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<p><link href="../../../css/bootstrap.css" rel="stylesheet" /></p>
-		<h1 id="Gettingstarted">Getting started</h1>
-		<p>Here you learn how to install the YAKINDU SCT2 and to make the first steps.</p>
-		<h2 id="Installation">Installation</h2>
-		<h3 id="Prerequisites">Prerequisites</h3>
-		<p>The 
-			<strong>Yakindu Statechart Tools 2</strong> are built upon Java and Xtext. So you need to have installed a 
-			<a href="http://www.oracle.com/technetwork/java/index.html">Java Runtime Environment</a> and Xtext installed. The easier way to get this is to install the 
-			<a href="http://xtext.itemis.com">pre configured Xtext contribution</a>.
-		</p>
-		<p>The 
-			<strong>Yakindu Statechart Tools 2</strong> need 
-			<strong>Eclipse Indigo 3.7</strong> or higher and 
-			<strong>Xtext 2.0.1</strong> exactly (no higher) to work correctly.
-		</p>
-		<h3 id="InstallingtheYAKINDUPlugIns">Installing the YAKINDU-Plug-Ins</h3>
-		<p>You install the Yakindu Plug-Ins from the update site: http://updates.yakindu.com/indigo/milestones. </p>
-		<ul>
-			<li>Click 
-				<strong>Help</strong> &gt; 
-				<strong>Install new software...</strong> and 
-				<strong>Add..</strong> the update site 
-				<em>Yakindu SCT2 milestones</em> - http://updates.yakindu.com/indigo/milestones/
-			</li>
-			<li>Check all to install the YAKINDU SCT2</li>
-			<li>Click 
-				<strong>Next</strong> to start the installation and click 
-				<strong>Next</strong> at the next step
-			</li>
-			<li>Accept the licence agreement and click 
-				<strong>Finish</strong>
-			</li>
-			<li>The software will be installed</li>
-		</ul>
-		<p>When the installation finished the wizard will ask to reopen Eclipse. The restart is important to make the newly installed software work correctly.</p>
-		<p>
-			<img border="0" src="images/updatesite_4.jpg"/>
-		</p>
-		<h2 id="Firststepsmyfirststatemachine">First steps: my first state machine</h2>
-		<p>In the following you will create your first state machine with the YAKINDU Statechart tools and simulate it. </p>
-		<h3 id="CreatingaNewProject">Creating a New Project</h3>
-		<p>For modeling purposes the YAKINDU statechart tools offer a workbench perspective. Such a perspective is a bunch of editors and views that are organized in a pre defined order on the screen. Open the Yakindu 
-			<strong>SC Modeling</strong> perspective by clicking 
-			<strong>Window</strong> &gt; 
-			<strong>Open Perspective</strong> &gt; 
-			<strong>SC Modeling</strong>. This perspective is optimized for statechart modeling. It consists of 
-		</p>
-		<ul>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> on the left
-			</li>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm">Outline</a> View on the right
-			</li>
-			<li>YAKINDU Statechart Editor at the top</li>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cprbview.htm">Problems</a> and 
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cpropview.htm">Properties View</a> at the bottom
-			</li>
-		</ul>
-		<p>
-			<img border="0" src="images/sc_modeling_perspective.jpg"/>
-		</p>
-		<p>In the Eclipse workbench all elements are organized in projects. So first to do is to create a project. Therefore click 
-			<strong>File</strong> &gt; 
-			<strong>New..." &gt; *Project</strong>. In the wizard click 
-			<strong>Next</strong> and insert a project name. Click 
-			<strong>Finish</strong>.
-		</p>
-		<p>Now you see your project in the project explorer. </p>
-		<h3 id="DefiningaStateMachine">Defining a State Machine</h3>
-		<p>In the new project now create a new statechart model:</p>
-		<ol>
-			<li>Click 
-				<strong>File</strong> &gt; 
-				<strong>New</strong> &gt; 
-				<strong>Other...</strong> &gt; 
-				<strong>YAKINDU</strong> &gt; 
-				<strong>YAKINDU Statechart Model</strong>
-			</li>
-			<li>Click 
-				<strong>Next</strong> and name the sct file
-			</li>
-			<li>Click 
-				<strong>Finish</strong>
-			</li>
-			<li>The YAKINDU statechart editor opens on the statechart model. It already has an initial state and an unnamed simple state connected by a transition.</li>
-		</ol>
-		<p>The newly created model has a problem. The new state has a red dot with a cross. This is an error marker. If you look at the problems view (the 
-			<strong>Problems</strong> tab) you see more details to that problem. In that case it says: &#8222;A state must have a name&#8221;. 
-			<br/>To solve the problem:
-		</p>
-		<ol>
-			<li>Click in the name field of the state and type the name &#8218;off&#8217;. </li>
-			<li>Click 
-				<strong>File</strong> &gt; 
-				<strong>Save</strong>. 
-			</li>
-		</ol>
-		<p>The error marker and the entry in the problems view vanish.</p>
-		<p>
-			<img border="0" src="images/sc_modeling_perspective_errorview.jpg"/>
-		</p>
-		<p>With the 
-			<strong>YAKINDU Statechart editor</strong> you create or modify state models. The editor automatically opens on .sct files. 
-		</p>
-		<p>The editor consists of three parts: </p>
-		<ul>
-			<li>the graphic canvas to design the state machine</li>
-			<li>the palette on the right that owns the elements to design the state machine </li>
-			<li>a textual modeling field on the left</li>
-		</ul>
-		<p>
-			<img border="0" src="images/sc_editor_01.jpg"/>
-		</p>
-		<p>You can use the textual modeling field for declarating internal behavior of states and events or variables.  The editor also owns comfortable functionality like 
-			<em>syntax highlighting</em>, 
-			<em>code completion</em>, 
-			<em>live validation</em>. The following image shows an example of code completion in the text fields of the editor:
-		</p>
-		<p>
-			<img border="0" src="images/sc_editor_code_completion.jpg"/> 
-		</p>
-		<ol>
-			<li>Add a second state 
-				<ol>
-					<li>Click on the symbol 
-						<strong>State</strong> in the palette
-					</li>
-					<li>Draw a state icon in the main region</li>
-					<li>Name the second state 'on'</li>
-				</ol>
-			</li>
-			<li>Draw a transition from &#8218;off&#8217; state to &#8218;on&#8217; state. 
-				<ol>
-					<li>Click on the symbol 
-						<strong>Transition</strong> on the palette. 
-					</li>
-					<li>Draw a line from &#8218;off&#8217; to &#8218;on&#8217;. </li>
-					<li>Add the following statement to the transition: after 2 s.</li>
-				</ol>
-			</li>
-			<li>Draw a transition with an event from &#8218;on&#8217; to &#8218;off&#8217; state. 
-				<ol>
-					<li>Click on the symbol 'Transition'</li>
-					<li>Draw a line from off to on state.</li>
-					<li>In the declarations view add the statement internal: event switchOff.</li>
-					<li>To the transition add the text switchOff</li>
-				</ol>
-			</li>
-		</ol>
-		<h3 id="SimulatingtheStateMachine">Simulating the State Machine</h3>
-		<p>YAKINDU SCT 2 comes with a perspective to simulate the models. To simulate a state machine open the Yakindu 
-			<strong>SC Simulation</strong> perspective by clicking 
-			<strong>Window</strong> &gt; 
-			<strong>Open Perspective</strong> &gt; 
-			<strong>SC Simulation</strong>. This perspective is optimized for simulation purposes and consists of:
-		</p>
-		<ul>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> on the left
-			</li>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm">Outline</a> view on the right top
-			</li>
-			<li>Simulation View on the right bottom</li>
-			<li>Debug view at the top</li>
-			<li>YAKINDU Statechart Editor</li>
-		</ul>
-		<p>The simulation view is an interactive view to watch and control the state machine simulation. To get it open the simulation perspective. </p>
-		<ol>
-			<li>Start the simulation by clicking 
-				<strong>Run</strong> &gt; 
-				<strong>Run</strong>. 
-			</li>
-			<li>The simulation starts and state &#8218;off&#8217; is red for 2 seconds. Then state &#8218;on&#8217; gets active (red).</li>
-			<li>Raise event &#8218;switchOff&#8217;: Click on &#8218;switchOff&#8217; in the simulation view.</li>
-			<li>State &#8218;off&#8217; is active again for 2 seconds.</li>
-			<li>Stop the simulation: 
-				<strong>Run</strong> &gt; 
-				<strong>Terminate</strong>.
-			</li>
-		</ol>
-		<p>
-			<img border="0" src="images/simulation_view_active.jpg"/>
-		</p>
-		<p>During the simulation in the statechart editor the active state gets a red color. The previous transition is green. The simulation view shows the events that trigger the states. You can change values here to trigger events. Beneath the table there are two clocks. One for the 
-			<em>virtual time</em> and one for the 
-			<em>real time</em> and a slider to change virtual time.
-		</p>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/user/02_Getting_Started/getting_started.textile

@@ -1,115 +0,0 @@
-<link href="../../../css/bootstrap.css" rel="stylesheet" />
-
-h1. Getting started
-
-Here you learn how to install the YAKINDU SCT2 and to make the first steps.
-
-h2. Installation
-
-h3. Prerequisites
-
-The *Yakindu Statechart Tools 2* are built upon Java and Xtext. So you need to have installed a "Java Runtime Environment":http://www.oracle.com/technetwork/java/index.html and Xtext installed. The easier way to get this is to install the "pre configured Xtext contribution":http://xtext.itemis.com.
-
-The *Yakindu Statechart Tools 2* need *Eclipse Indigo 3.7* or higher and *Xtext 2.0.1* exactly (no higher) to work correctly.
-
-h3. Installing the YAKINDU-Plug-Ins
-
-You install the Yakindu Plug-Ins from the update site: http://updates.yakindu.com/indigo/milestones. 
-
-* Click *Help* > *Install new software...* and *Add..* the update site _Yakindu SCT2 milestones_ - http://updates.yakindu.com/indigo/milestones/
-* Check all to install the YAKINDU SCT2
-* Click *Next* to start the installation and click *Next* at the next step
-* Accept the licence agreement and click *Finish*
-* The software will be installed
-
-When the installation finished the wizard will ask to reopen Eclipse. The restart is important to make the newly installed software work correctly.
-
-!images/updatesite_4.jpg!
-
-
-
-h2. First steps: my first state machine
-
-In the following you will create your first state machine with the YAKINDU Statechart tools and simulate it. 
-
-h3. Creating a New Project
-
-For modeling purposes the YAKINDU statechart tools offer a workbench perspective. Such a perspective is a bunch of editors and views that are organized in a pre defined order on the screen. Open the Yakindu *SC Modeling* perspective by clicking *Window* > *Open Perspective* > *SC Modeling*. This perspective is optimized for statechart modeling. It consists of 
-* "Project Explorer":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm on the left
-* "Outline":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm View on the right
-* YAKINDU Statechart Editor at the top
-* "Problems":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cprbview.htm and "Properties View":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cpropview.htm at the bottom
-
-!images/sc_modeling_perspective.jpg!
-
-In the Eclipse workbench all elements are organized in projects. So first to do is to create a project. Therefore click *File* > *New..." > *Project*. In the wizard click *Next* and insert a project name. Click *Finish*.
-
-Now you see your project in the project explorer. 
-
-h3. Defining a State Machine
-
-In the new project now create a new statechart model:
-
-# Click *File* > *New* > *Other...* > *YAKINDU* > *YAKINDU Statechart Model*
-# Click *Next* and name the sct file
-# Click *Finish*
-# The YAKINDU statechart editor opens on the statechart model. It already has an initial state and an unnamed simple state connected by a transition.
-
-The newly created model has a problem. The new state has a red dot with a cross. This is an error marker. If you look at the problems view (the *Problems* tab) you see more details to that problem. In that case it says: "A state must have a name". 
-To solve the problem:
-# Click in the name field of the state and type the name 'off'. 
-# Click *File* > *Save*. 
-The error marker and the entry in the problems view vanish.
-
-!images/sc_modeling_perspective_errorview.jpg!
-
-With the *YAKINDU Statechart editor* you create or modify state models. The editor automatically opens on .sct files. 
-
-The editor consists of three parts: 
-* the graphic canvas to design the state machine
-* the palette on the right that owns the elements to design the state machine 
-* a textual modeling field on the left
-
-!images/sc_editor_01.jpg!
-
-You can use the textual modeling field for declarating internal behavior of states and events or variables.  The editor also owns comfortable functionality like _syntax highlighting_, _code completion_, _live validation_. The following image shows an example of code completion in the text fields of the editor:
-
-!images/sc_editor_code_completion.jpg! 
-
-# Add a second state 
-## Click on the symbol *State* in the palette
-## Draw a state icon in the main region
-## Name the second state 'on'
-# Draw a transition from 'off' state to 'on' state. 
-## Click on the symbol *Transition* on the palette. 
-## Draw a line from 'off' to 'on'. 
-## Add the following statement to the transition: after 2 s.
-# Draw a transition with an event from 'on' to 'off' state. 
-## Click on the symbol 'Transition'
-## Draw a line from off to on state.
-## In the declarations view add the statement internal: event switchOff.
-## To the transition add the text switchOff
-
-h3. Simulating the State Machine
-
-YAKINDU SCT 2 comes with a perspective to simulate the models. To simulate a state machine open the Yakindu *SC Simulation* perspective by clicking *Window* > *Open Perspective* > *SC Simulation*. This perspective is optimized for simulation purposes and consists of:
-
-* "Project Explorer":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm on the left
-* "Outline":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm view on the right top
-* Simulation View on the right bottom
-* Debug view at the top
-* YAKINDU Statechart Editor
-
-
-The simulation view is an interactive view to watch and control the state machine simulation. To get it open the simulation perspective. 
-
-# Start the simulation by clicking *Run* > *Run*. 
-# The simulation starts and state 'off' is red for 2 seconds. Then state 'on' gets active (red).
-# Raise event 'switchOff': Click on 'switchOff' in the simulation view.
-# State 'off' is active again for 2 seconds.
-# Stop the simulation: *Run* > *Terminate*.
-
-!images/simulation_view_active.jpg!
-
-During the simulation in the statechart editor the active state gets a red color. The previous transition is green. The simulation view shows the events that trigger the states. You can change values here to trigger events. Beneath the table there are two clocks. One for the _virtual time_ and one for the _real time_ and a slider to change virtual time.
-

plugins/org.yakindu.sct.doc.user/help/user/03_Concepts/concepts-toc.xml

@@ -1,14 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/user/03_Concepts/concepts.html" label="concepts">
-	<topic href="help/user/03_Concepts/concepts.html" label="Yakindu Statechart tool concepts">
-		<topic href="help/user/03_Concepts/concepts.html#Modeling" label="Modeling"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#Simulation" label="Simulation"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#CodeGeneration" label="Code Generation"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#Domainspecificadaptability" label="Domain specific adaptability"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#YakinduSCModelingperspective" label="Yakindu SC Modeling perspective"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#YakinduSCSimulationperspective" label="Yakindu SC Simulation perspective"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#YAKINDUStatechartEditor" label="YAKINDU Statechart Editor"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#SimulationView" label="Simulation View"></topic>
-		<topic href="help/user/03_Concepts/concepts.html#YAKINDUSCTNature" label="YAKINDU SCT Nature"></topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/user/03_Concepts/concepts.html

@@ -1,133 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>concepts</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<p><link href="../../../css/bootstrap.css" rel="stylesheet" /></p>
-		<h1 id="YakinduStatecharttoolconcepts">Yakindu Statechart tool concepts</h1>
-		<h2 id="Modeling">Modeling</h2>
-		<p>Yakindu Statechart Models are based on statecharts as defined by David Harel and are close to UML state machines. Thus, they support all structural model elements as defined by the UML specification, which are States (orthogonal and hierarchical), Regions, Transitions and Pseudo States (History, Deep History, Initial, Final, Choice, Join / Fork).
-			<br/>In addition, Yakindu Statechart Models specify interfaces that define the interaction of the state machine with its environment. Besides some more advanced concepts like Entry / Exit Points, an interface basically consists of in and out Events as well as Variables including types. These well-defined statechart interfaces are especially useful in the context of component models and product line engineering.
-		</p>
-		<p>For defining interfaces and modeling the dynamic aspects of statecharts (triggers, guards and actions) SCT provides a statically typed, textual action language. It tightly integrates into the graphical editor and supports the user with code completion, syntax highlighting, cross referencing and validation during modeling.</p>
-		<p>Declarations of interfaces, events, variables etc. are done in a textual modeling field in the editor. The language expressions that define actions are directly added to the elements like states or transitions. </p>
-		<h2 id="Simulation">Simulation</h2>
-		<p>Yakindu Statechart Models can be executed via an integrated simulation engine. The simulation engine supports two different types of execution semantics:</p>
-		<ul>
-			<li>cycle based </li>
-			<li>event driven</li>
-		</ul>
-		<p>The default execution semantic is 
-			<strong>cycle based</strong> which executes a statechart cycle within a fixed period of time and thus allows processing of concurrent events. In contrast, the 
-			<strong>event based</strong> approach executes a statechart cycle as soon as an event occurrs.
-		</p>
-		<p>During simulation, the currently active states and the transition path including the previous states are highlighted in the editor for visual debugging. An additional view shows the variable values and allows to raise events. </p>
-		<p>Apart from that, the engine uses a 
-			<strong>virtual time</strong> during simulation. The user can provide a time scaling factor that is multiplied with the real time. This is especially useful during debugging, if the statechart model contains very tight or long running time triggers.
-		</p>
-		<h2 id="CodeGeneration">Code Generation</h2>
-		<p>Yakindu Statechart Tools currently support the generation of Java, C and C++ Code.  All generators can be customized with a 
-			<strong>generator model</strong>. This is a textual model file where generator features, like the execution type (event or cycle based), or the interface styles (static or generic), can be specified. The code generation process can either be executed with a builder that starts code generation on resource change or manually with a context menu action.
-		</p>
-		<h2 id="Domainspecificadaptability">Domain specific adaptability</h2>
-		<p>Yakindu Statechart Tools were developed with a domain specific adaptability in mind. Several extension points allow the customization of all mentioned aspects. It is possible to contribute a custom type system or custom action languages which may be a dialect of the textual description language or a complete new language.</p>
-		<p>Also, the different code generators can be customized or new code generators for other target languages can be plugged in easily.</p>
-		<h2 id="YakinduSCModelingperspective">Yakindu SC Modeling perspective</h2>
-		<p>For state machine modeling purposes open the Yakindu 
-			<strong>SC Modeling</strong> perspective by clicking 
-			<strong>Window</strong> &gt; 
-			<strong>Open Perspective</strong> &gt; 
-			<strong>SC Modeling</strong>. This perspective is optimized for statechart modeling. It consists of 
-		</p>
-		<ul>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> on the left
-			</li>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm">Outline</a> View on the right
-			</li>
-			<li>YAKINDU Statechart Editor at the top</li>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cprbview.htm">Problems</a> and 
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cpropview.htm">Properties View</a> at the bottom
-			</li>
-		</ul>
-		<p>
-			<img border="0" src="../02_Getting_Started/images/sc_modeling_perspective.jpg"/>
-		</p>
-		<h2 id="YakinduSCSimulationperspective">Yakindu SC Simulation perspective</h2>
-		<p>To simulate a state machine use the Yakindu 
-			<strong>SC Simulation</strong> perspective by clicking 
-			<strong>Window</strong> &gt; 
-			<strong>Open Perspective</strong> &gt; 
-			<strong>SC Simulation</strong>. This perspective is optimized for simulation purposes and consists of:
-		</p>
-		<ul>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> on the left
-			</li>
-			<li>
-				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm">Outline</a> view on the right top
-			</li>
-			<li>Simulation View on the right bottom</li>
-			<li>Debug view at the top</li>
-			<li>YAKINDU Statechart Editor at the bottom</li>
-		</ul>
-		<p>
-			<img border="0" src="../02_Getting_Started/images/sc_simulation_perspective.jpg"/>
-		</p>
-		<h2 id="YAKINDUStatechartEditor">YAKINDU Statechart Editor</h2>
-		<p>With the YAKINDU Statechart editor you create or modify state models. The editor automatically opens on .sct files. To create a new YAKINDU statechart model click 
-			<strong>File</strong> &gt; 
-			<strong>New</strong> &gt; 
-			<strong>Other...</strong> &gt; 
-			<strong>YAKINDU Statechart model</strong>. Give it a speaking name and click 
-			<strong>Finish</strong>. The newly created model opens in the statechart editor. Also the SC Modeling perspective opens.
-		</p>
-		<p>
-			<img border="0" src="../02_Getting_Started/images/sc_editor_01.jpg"/>
-		</p>
-		<p>The editor consists of three parts: </p>
-		<ul>
-			<li>the graphic canvas to design the state machine</li>
-			<li>the palette on the right that owns the elements to design the state machine </li>
-			<li>a textual modeling field on the left</li>
-		</ul>
-		<p>You can use the textual modeling field to define internal behavior of states and declare events or variables. The 
-			<a href="../05_Reference/reference.html#Statechartdescriptionlanguage">reference</a> explains this language.
-		</p>
-		<p>Elements that cause problems get warning and error markers attached. For more details about the problems open the 
-			<strong>Problems View</strong>.
-		</p>
-		<h2 id="SimulationView">Simulation View</h2>
-		<p>The simulation view is an interactive view to watch and control the state machine simulation. To get it open the simulation perspective. </p>
-		<p>Start a simulation by clicking 
-			<strong>Run</strong> &gt; 
-			<strong>Run</strong>. 
-		</p>
-		<p>
-			<img border="0" src="../02_Getting_Started/images/simulation_view_active.jpg"/>
-		</p>
-		<p>During the simulation in the statechart editor the active state gets a red color. The previous transition is green. The simulation view shows the events that trigger the states. You can change values here to trigger events. Beneath the table there are two clocks. One for the 
-			<em>virtual time</em> and one for the 
-			<em>real time</em> and a slider to change virtual time.
-		</p>
-		<p>You can also select an 
-			<em>event driven</em> or 
-			<em>cycle based</em> run configuration.
-		</p>
-		<h2 id="YAKINDUSCTNature">YAKINDU SCT Nature</h2>
-		<p>YAKINDU model projects are associated with the 
-			<strong>YAKINDU SCT nature</strong>. On projects with 
-			<strong>YAKINDU SCT nature</strong> 
-			<em>.sct</em> and 
-			<em>.sgen</em> files are automatically build and checked for problems. So you get fast feedback during editing. You can toggle the SCT nature by right clicking 
-			<strong>Configure</strong> &gt; 
-			<strong>Add</strong> or 
-			<strong>Remove YAKINDU SCT Nature</strong> on the project.
-		</p>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/user/03_Concepts/concepts.textile

@@ -1,97 +0,0 @@
-<link href="../../../css/bootstrap.css" rel="stylesheet" />
-
-h1. Yakindu Statechart tool concepts
-
-
-h2. Modeling
-
-Yakindu Statechart Models are based on statecharts as defined by David Harel and are close to UML state machines. Thus, they support all structural model elements as defined by the UML specification, which are States (orthogonal and hierarchical), Regions, Transitions and Pseudo States (History, Deep History, Initial, Final, Choice, Join / Fork).
-In addition, Yakindu Statechart Models specify interfaces that define the interaction of the state machine with its environment. Besides some more advanced concepts like Entry / Exit Points, an interface basically consists of in and out Events as well as Variables including types. These well-defined statechart interfaces are especially useful in the context of component models and product line engineering.
-
-For defining interfaces and modeling the dynamic aspects of statecharts (triggers, guards and actions) SCT provides a statically typed, textual action language. It tightly integrates into the graphical editor and supports the user with code completion, syntax highlighting, cross referencing and validation during modeling.
-
-Declarations of interfaces, events, variables etc. are done in a textual modeling field in the editor. The language expressions that define actions are directly added to the elements like states or transitions. 
-
-h2. Simulation
-
-Yakindu Statechart Models can be executed via an integrated simulation engine. The simulation engine supports two different types of execution semantics:
-
-* cycle based 
-* event driven
-
-The default execution semantic is *cycle based* which executes a statechart cycle within a fixed period of time and thus allows processing of concurrent events. In contrast, the *event based* approach executes a statechart cycle as soon as an event occurrs.
-
-During simulation, the currently active states and the transition path including the previous states are highlighted in the editor for visual debugging. An additional view shows the variable values and allows to raise events. 
-
-Apart from that, the engine uses a *virtual time* during simulation. The user can provide a time scaling factor that is multiplied with the real time. This is especially useful during debugging, if the statechart model contains very tight or long running time triggers.
-
-h2. Code Generation
-
-Yakindu Statechart Tools currently support the generation of Java, C and C++ Code.  All generators can be customized with a *generator model*. This is a textual model file where generator features, like the execution type (event or cycle based), or the interface styles (static or generic), can be specified. The code generation process can either be executed with a builder that starts code generation on resource change or manually with a context menu action.
-
-h2. Domain specific adaptability
-
-Yakindu Statechart Tools were developed with a domain specific adaptability in mind. Several extension points allow the customization of all mentioned aspects. It is possible to contribute a custom type system or custom action languages which may be a dialect of the textual description language or a complete new language.
-
-Also, the different code generators can be customized or new code generators for other target languages can be plugged in easily.
-
-h2. Yakindu SC Modeling perspective
-
-For state machine modeling purposes open the Yakindu *SC Modeling* perspective by clicking *Window* > *Open Perspective* > *SC Modeling*. This perspective is optimized for statechart modeling. It consists of 
-* "Project Explorer":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm on the left
-* "Outline":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm View on the right
-* YAKINDU Statechart Editor at the top
-* "Problems":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cprbview.htm and "Properties View":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cpropview.htm at the bottom
-
-!../02_Getting_Started/images/sc_modeling_perspective.jpg!
-
-
-h2. Yakindu SC Simulation perspective
-
-To simulate a state machine use the Yakindu *SC Simulation* perspective by clicking *Window* > *Open Perspective* > *SC Simulation*. This perspective is optimized for simulation purposes and consists of:
-
-* "Project Explorer":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm on the left
-* "Outline":PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm view on the right top
-* Simulation View on the right bottom
-* Debug view at the top
-* YAKINDU Statechart Editor at the bottom
-
-!../02_Getting_Started/images/sc_simulation_perspective.jpg!
-
-
-
-h2. YAKINDU Statechart Editor
-
-With the YAKINDU Statechart editor you create or modify state models. The editor automatically opens on .sct files. To create a new YAKINDU statechart model click *File* > *New* > *Other...* > *YAKINDU Statechart model*. Give it a speaking name and click *Finish*. The newly created model opens in the statechart editor. Also the SC Modeling perspective opens.
-
-!../02_Getting_Started/images/sc_editor_01.jpg!
-
-
-The editor consists of three parts: 
-* the graphic canvas to design the state machine
-* the palette on the right that owns the elements to design the state machine 
-* a textual modeling field on the left
-
-You can use the textual modeling field to define internal behavior of states and declare events or variables. The "reference":../05_Reference/reference.html#Statechartdescriptionlanguage explains this language.
-
-Elements that cause problems get warning and error markers attached. For more details about the problems open the *Problems View*.
-
-h2. Simulation View
-
-The simulation view is an interactive view to watch and control the state machine simulation. To get it open the simulation perspective. 
-
-Start a simulation by clicking *Run* > *Run*. 
-
-!../02_Getting_Started/images/simulation_view_active.jpg!
-
-During the simulation in the statechart editor the active state gets a red color. The previous transition is green. The simulation view shows the events that trigger the states. You can change values here to trigger events. Beneath the table there are two clocks. One for the _virtual time_ and one for the _real time_ and a slider to change virtual time.
-
-You can also select an _event driven_ or _cycle based_ run configuration.
-
-h2. YAKINDU SCT Nature
-
-YAKINDU model projects are associated with the *YAKINDU SCT nature*. On projects with *YAKINDU SCT nature* _.sct_ and _.sgen_ files are automatically build and checked for problems. So you get fast feedback during editing. You can toggle the SCT nature by right clicking *Configure* > *Add* or *Remove YAKINDU SCT Nature* on the project.
-
-
-
-

plugins/org.yakindu.sct.doc.user/help/user/04_Tasks/tasks-toc.xml

@@ -1,33 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/user/04_Tasks/tasks.html" label="tasks">
-	<topic href="help/user/04_Tasks/tasks.html" label="Tasks">
-		<topic href="help/user/04_Tasks/tasks.html#Modelingastatemachine" label="Modeling a statemachine">
-			<topic href="help/user/04_Tasks/tasks.html#Relatedtopics" label="Related topics"></topic>
-		</topic>
-		<topic href="help/user/04_Tasks/tasks.html#Validatingastatemachine" label="Validating a statemachine"></topic>
-		<topic href="help/user/04_Tasks/tasks.html#Simulatingastatemachine" label="Simulating a statemachine"></topic>
-		<topic href="help/user/04_Tasks/tasks.html#GeneratingCode" label="Generating Code"></topic>
-		<topic href="help/user/04_Tasks/tasks.html#CoreFeatures" label="Core Features">
-			<topic href="help/user/04_Tasks/tasks.html#Outlet" label="Outlet"></topic>
-			<topic href="help/user/04_Tasks/tasks.html#LicenseHeader" label="LicenseHeader"></topic>
-			<topic href="help/user/04_Tasks/tasks.html#FunctionInlining" label="FunctionInlining"></topic>
-			<topic href="help/user/04_Tasks/tasks.html#Debug" label="Debug"></topic>
-		</topic>
-		<topic href="help/user/04_Tasks/tasks.html#JavaGeneratorFeatures" label="Java Generator Features">
-			<topic href="help/user/04_Tasks/tasks.html#Naming" label="Naming"></topic>
-			<topic href="help/user/04_Tasks/tasks.html#GeneralFeatures" label="GeneralFeatures"></topic>
-		</topic>
-		<topic href="help/user/04_Tasks/tasks.html#CGeneratorFeatures" label="C Generator Features">
-			<topic href="help/user/04_Tasks/tasks.html#CCodeFeature" label="CCodeFeature"></topic>
-		</topic>
-		<topic href="help/user/04_Tasks/tasks.html#CreateCustomCodeGenerators" label="Create Custom Code Generators">
-			<topic href="help/user/04_Tasks/tasks.html#WritingacustomcodegeneratorwithXtend2Java" label="Writing a custom code generator with Xtend2/Java"></topic>
-			<topic href="help/user/04_Tasks/tasks.html#ExecutingacustomXtend2Javacodegenerator" label="Executing a custom Xtend2/Java code generator">
-				<topic href="help/user/04_Tasks/tasks.html#Generator" label="Generator"></topic>
-			</topic>
-			<topic href="help/user/04_Tasks/tasks.html#ExecutingacustomXpandcodegenerator" label="Executing a custom Xpand code generator">
-				<topic href="help/user/04_Tasks/tasks.html#Template" label="Template"></topic>
-			</topic>
-		</topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/help/user/04_Tasks/tasks.html

@@ -1,433 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-	<head>
-		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
-		<title>tasks</title>
-		<link type="text/css" rel="stylesheet" href="../style.css"/>
-	</head>
-	<body>
-		<p><link href="../../../css/bootstrap.css" rel="stylesheet" /></p>
-		<h1 id="Tasks">Tasks</h1>
-		<h2 id="Modelingastatemachine">Modeling a statemachine</h2>
-		<ol>
-			<li>Make sure the YAKINDU Modeling perspective is active.</li>
-			<li>Create a new project.</li>
-			<li>Click 
-				<strong>File</strong> &gt; 
-				<strong>New</strong> &gt; 
-				<strong>Other...</strong> &gt; 
-				<strong>YAKINDU</strong> &gt; 
-				<strong>YAKINDU Statechart Model</strong>. 
-			</li>
-			<li>Click 
-				<strong>Next</strong> name the sct file and click 
-				<strong>Finish</strong>
-			</li>
-			<li>The YAKINDU statechart editor opens on the statechart model. It already has an initial state and an unnamed simple state connected by a transition.</li>
-			<li>Now you can add states and transitions from the palette.</li>
-		</ol>
-		<p>To edit the states and transitions you can use the properties view. It has an integrated Xtext support. This makes correct editing easier. You can also change the appearance of the model elements. </p>
-		<p>On the palette you will also find a composite submachine state. This is a state that contains a complete statemachine. You can choose an existing statemachine or create a new one.</p>
-		<h3 id="Relatedtopics">Related topics</h3>
-		<p>
-			<a href="../05_Reference/reference.html#Statechartelements">Statemachine Elements reference</a>
-			<br/>
-			<a href="../05_Reference/reference.html#Statechartdescriptionlanguage">Textual modeling lanuage  Reference</a>
-		</p>
-		<h2 id="Validatingastatemachine">Validating a statemachine</h2>
-		<p>The statemachine is validated automatically during build. The elements that cause problems get error markers. You can find the details about the problems on the problems view.</p>
-		<h2 id="Simulatingastatemachine">Simulating a statemachine</h2>
-		<p>The YAKINDU simulation engine supports simulation modes:</p>
-		<ul>
-			<li>event driven</li>
-			<li>cycle based</li>
-		</ul>
-		<p>The default setting is 
-			<em>cycle based</em> with a cycle period of 200 ms. In this mode the simulation engine processes the state machine transitions in steps of the given cycle duration. The following statechart illustrates this. It is simulated cycle based with a cycle period of 3 seconds.
-		</p>
-		<p>
-			<img border="0" src="images/cycleBasedVsEventDriven.png"/>
-		</p>
-		<p>What happend during simulation is the following:</p>
-		<ol>
-			<li>After 3s 
-				<strong>init</strong> switches to 
-				<strong>pre1</strong>
-			</li>
-			<li>After 3 further seconds recursive transition to 
-				<strong>pre1</strong> is processed (not after 2s the transition says)
-			</li>
-			<li>After 3 further seconds recursive transition to 
-				<strong>pre1</strong> is processed again and the condition becomes 
-				<strong>true</strong> so 
-				<strong>result</strong> gets activated
-			</li>
-		</ol>
-		<p>In contrast to cycle based the event driven simulation mode concentrates on the events of a state machine. The same state machine above could be simulated as follows:</p>
-		<ol>
-			<li>Immediately 
-				<strong>init</strong> switches to 
-				<strong>pre1</strong>
-			</li>
-			<li>Immediately the event 
-				<strong>touch</strong> is raised twice
-			</li>
-			<li>The condition becomes true so that the 
-				<strong>result</strong> state is reached after 2 or 3 seconds instead of 9 
-			</li>
-		</ol>
-		<p>Start a simulation with the different modes as follows</p>
-		<ol>
-			<li>Make sure the YAKINDU Simulation Perspectiv is opened.</li>
-			<li>Start the simulation by clicking 
-				<strong>Run</strong> &gt; 
-				<strong>Run Configurations...</strong>.
-			</li>
-			<li>Select the statechart you want to simulate and the simulation mode.</li>
-			<li>
-				<strong>Apply</strong> the setting and 
-				<strong>Run</strong> the simulation.
-			</li>
-		</ol>
-		<p>
-			<img border="0" src="images/simulationRunConfiguration.png"/>
-		</p>
-		<p>
-			<a href="../03_Concepts/concepts.html#Simulation">Simulation Concept</a>
-			<br/>
-			<a href="../03_Concepts/concepts.html#YakinduSCSimulationperspective">Simulation perspective</a>
-			<br/>
-			<a href="../03_Concepts/concepts.html#SimulationView">Simulation View</a>
-		</p>
-		<h2 id="GeneratingCode">Generating Code</h2>
-		<p>For configuring the code generation process, YAKINDU Statechart Tools uses a textual generator model called 
-			<strong>SGen</strong>. It can be created either by using the provided wizard 
-			<strong>Yakindu Statechart Generator Model</strong> or by creating a new text file with the file extension &#8218;.sgen&#8217;.
-			<br/>To create a generator model with the wizard,
-		</p>
-		<ol>
-			<li>Click 
-				<strong>File</strong> &gt; 
-				<strong>New</strong> &gt; 
-				<strong>Other...</strong> &gt; 
-				<strong>Yakindu Statechart Generator Model</strong>
-			</li>
-			<li>Type a name and click 
-				<strong>Next</strong>
-			</li>
-			<li>Choose the desired generator, i.e. 
-				<strong>YAKINDU Java Code Generator</strong>
-			</li>
-			<li>Check the model(s) to generate code from and click 
-				<strong>Finish</strong>
-			</li>
-		</ol>
-		<p>
-			<img border="0" src="images/genmodelwizardchooselanguage.jpg"/>
-		</p>
-		<p>The result is an .sgen file of the following format: </p>
-		<pre><code>GeneratorModel for [GeneratorId] {
-	statechart [StatechartReference] {
-		feature [Feature] {
-			[ParameterName] = [ParameterValue]
-		}
-	}
-}
-</code></pre>
-		<p>The [GeneratorId] is the unique id of the Generator. Currently, the following Generators are supported out of the box:</p>
-		<ol>
-			<li>yakindu::java &#8211; Generator ID for the Java Code Generator </li>
-			<li>yakindu::c &#8211; Generator ID for the C Code Generator</li>
-			<li>yakindu::cpp &#8211; Generator ID for the C++ Code Generator</li>
-			<li>yakindu::xpand &#8211; Generator ID for custom Xpand based Code Generators</li>
-			<li>yakindu::generic &#8211; Generator ID for custom Java based Code Generators  </li>
-		</ol>
-		<p>One GeneratorModel can contain several [StatechartReference]s. These are cross references to statechart models for which the code should be generated. For each reference, the generator process can be configured with [Feature]s. Each Feature consists of several parameters. These parameters can be configured with [ParameterName] = [ParameterValue].</p>
-		<p>The Generator Model is executed by a builder. Thus, the artifacts are generated automatically if 
-			<strong>Project</strong> &gt; 
-			<strong>Build Automatically</strong> is checked. If you want to execute your Generator Model by hand, select 
-			<strong>Generate Statechart Artifacts</strong> from the 
-			<strong>Package Explorer&#8217;s</strong> context menu.
-		</p>
-		<h2 id="CoreFeatures">Core Features</h2>
-		<p>The following section describes the 
-			<strong>Core Features</strong> which are available for all code generators:
-		</p>
-		<p><!-- Start sgen_feature_outlet --></p>
-		<h4 id="Outlet">Outlet</h4>
-		<p>The 
-			<strong>Outlet</strong> feature specifies the target project and folder for the generated artifacts. It is a 
-			<strong>required</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>targetProject</i>  (String, required): The project to store the generated artifacts  
-			</li>
-			<li>
-				<i>targetFolder</i>  (String, required): The folder to store the generated artifacts
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature Outlet {
-	targetProject = "ExampleProject"
-	targetFolder = "src-gen"
-}
-</code></pre>
-		<p><!-- End sgen_feature_outlet -->
-			<br/><!-- Start sgen_feature_licenseheader -->
-		</p>
-		<h4 id="LicenseHeader">LicenseHeader</h4>
-		<p>The 
-			<strong>LicenseHeader</strong> feature specifies the license text that should be added as a header to the generated artifacts. It is an 
-			<strong>optional</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>licenseText</i>  (String, required): The license text to add as a header  
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature LicenseHeader {
-	licenseText = "Copyright (c) 2012 committers of YAKINDU and others."
-}
-</code></pre>
-		<p><!-- End sgen_feature_licenseheader -->
-			<br/><!-- Start sgen_feature_functioninlining -->
-		</p>
-		<h4 id="FunctionInlining">FunctionInlining</h4>
-		<p>The 
-			<strong>FunctionInlining</strong> feature allows the inlining of expressions instead of generating separate functions or methods. This might reduce the readability of the generated code, but increases performance because less operation calls are necessary. 
-			<br/>It is an 
-			<strong>optinal</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>inlineReactions</i>  (Boolean, optional): Inlines the expression for reactions
-			</li>
-			<li>
-				<i>inlineEntryActions</i>  (Boolean, optional): Inlines the expression for entry actions
-			</li>
-			<li>
-				<i>inlineExitActions</i>  (Boolean, optional): Inlines the expression for exit actions
-			</li>
-			<li>
-				<i>inlineEnterSequences</i>  (Boolean, optional): Inlines the expression for enter sequences
-			</li>
-			<li>
-				<i>inlineExitSequences</i>  (Boolean, optional): Inlines the expression for exit sequences
-			</li>
-			<li>
-				<i>inlineChoices</i>  (Boolean, optional): Inlines the expression for choices
-			</li>
-			<li>
-				<i>inlineEnterRegion</i>  (Boolean, optional): Inlines the expression for enter regions
-			</li>
-			<li>
-				<i>inlineExitRegion</i>  (Boolean, optional): Inlines the expression for exit regions
-			</li>
-			<li>
-				<i>inlineEntries</i>  (Boolean, optional): Inlines the expression for entries 
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature FunctionInlining {
-	inlineChoices = false
-	inlineEnterRegion = true
-	inlineEntries = true
-}
-</code></pre>
-		<p><!-- End sgen_feature_functioninlining -->
-			<br/><!-- Start sgen_feature_debug -->
-		</p>
-		<h4 id="Debug">Debug</h4>
-		<p>The 
-			<strong>Debug</strong> feature dumps the Execution Model to the target folder as xmi model. It is an 
-			<strong>optional</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>dumpSexec</i>  (Boolean, required): The license text to add as a header  
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature Debug {
-	dumpSexec = true
-}
-
-</code></pre>
-		<p><!-- End sgen_feature_debug --></p>
-		<h2 id="JavaGeneratorFeatures">Java Generator Features</h2>
-		<p><!-- Start sgen_feature_naming --></p>
-		<h4 id="Naming">Naming</h4>
-		<p>The 
-			<strong>Naming</strong> feature allows the configuration of package names as well as class name prefix / suffix.
-			<br/>It is an 
-			<strong>optional</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>basePackage</i>  (Boolean, required): The package to create for the generated java classes
-			</li>
-			<li>
-				<i>implementationSuffix</i>  (Boolean, optional): The suffix for the implementing classes
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature Naming {
-	basePackage = "org.yakindu.sct"
-	implementationSuffix = "Impl"
-}
-</code></pre>
-		<p><!-- End sgen_feature_naming -->	
-			<br/><!-- Start sgen_feature_generalfeatures -->	
-		</p>
-		<h4 id="GeneralFeatures">GeneralFeatures</h4>
-		<p>The 
-			<strong>GeneralFeatures</strong> feature allows to configure additional services to generate with the statemachine. Per default, all parameters are configured to 
-			<i>false</i> It is an 
-			<strong>optional</strong> feature and consists of the following parameters:
-		</p>
-		<p><!-- # __EventBasedStatemachine__ (Boolean, optional): Enables/disables the generation of a cycle based statemachine implementation --></p>
-		<ol>
-			<li>
-				<i>InterfaceObserverSupport</i> (Boolean, optional): Enables/disables the generation of listener interfaces for the statemachine
-			</li>
-			<li>
-				<i>RuntimeService</i> (Boolean, optional): Enables/disables the generation of a runtime service that triggers the runcycle of a cycle based statemachine
-			</li>
-			<li>
-				<i>TimerService</i> (Boolean, optional): Enables/disables the generation of a timer service implementation using 
-				<i>java.util.Timer</i>
-			</li>
-		</ol>
-		<p><!-- # __GenericInterfaceSupport__ (Boolean, optional): Enables/disables the generation of generic interfaces -->
-			<br/><!-- # __StatemachineFactorySupport__ (Boolean, optional): Enables/disables  the generation of a factory class -->
-		</p>
-		<p>Example configuration:</p>
-		<pre><code>feature GeneralFeatures {
-	InterfaceObserverSupport = true
-	RuntimeService = true
-	TimerService = true
-}
-
-</code></pre>
-		<p><!-- End sgen_feature_generalfeatures -->			</p>
-		<h2 id="CGeneratorFeatures">C Generator Features</h2>
-		<p><!-- Start sgen_feature_ccodefeature -->	</p>
-		<h4 id="CCodeFeature">CCodeFeature</h4>
-		<p>The 
-			<strong>CCodeFeature</strong> feature allows to configure c code specific generator properties. It is an 
-			<strong>optional</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>InterfaceEventListener</i> (Boolean, mandatory): generates listener interface for notification of outgoing events.
-			</li>
-			<li>
-				<i>Singleton</i> (Boolean, mandatory): generates a statically allocated singleton variant of the state machine that does not allow multiple instances.
-			</li>
-			<li>
-				<i>DebugType</i> (String, optional): don&#8217;t use this property &#8211; it will be removed
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature CCodeFeature {
-	InterfaceEventListerner = true
-	Singleton = true
-}
-
-</code></pre>
-		<p><!-- End sgen_feature_ccodefeature -->			</p>
-		<h2 id="CreateCustomCodeGenerators">Create Custom Code Generators</h2>
-		<p>YAKINDU Statechart Tools provides a rich feature set to supports custom code generators out of the box. These code generators can be either written in Java, 
-			<a href="http://www.eclipse.org/xtend/">Xtend</a> or in 
-			<a href="http://www.eclipse.org/modeling/m2t/?project=xpand">Xpand</a>
-		</p>
-		<h3 id="WritingacustomcodegeneratorwithXtend2Java">Writing a custom code generator with Xtend2/Java</h3>
-		<p>First, you have to create a new Xtend2 generator project. Click 
-			<strong>File</strong> &gt; 
-			<strong>New</strong> &gt; 
-			<strong>Other...</strong> &gt; 
-			<strong>YAKINDU</strong> &gt; 
-			<strong>YAKINDU Xtend2/Java Generator Project</strong> to create a new Xtend2 Generator Project. 
-		</p>
-		<p>
-			<img border="0" src="images/xtendGenerator.png"/>
-		</p>
-		<p>The wizards asks for a 
-			<strong>Project name</strong> and the name of the 
-			<strong>Generator class</strong>, where you have to specify a full qualified class name. If you check the 
-			<strong>Use Xtend</strong> checkbox, the Generator class will be initially created as an 
-			<a href="http://www.eclipse.org/xtend/">Xtend</a> class. Otherwise, Java will be used for the generator.
-		</p>
-		<p>The check box 
-			<strong>Configure for Plugin Export</strong> adds all required extension point registrations to the new project for exporting as a plugin The Generator Model can refer to the new Generator Plugin via its unique 
-			<strong>Generator ID</strong>. If you want to contribute custom generator features for your code generator, check the 
-			<strong>Create Feature Library</strong> check box.  
-		</p>
-		<p>After click on 
-			<strong>Finish</strong> a new project is created in your workspace. All required plugin dependencies and extension points are registered and you can start to write your code generator based on the ExecutionFlow meta model [Link].
-		</p>
-		<h3 id="ExecutingacustomXtend2Javacodegenerator">Executing a custom Xtend2/Java code generator</h3>
-		<p>YAKINDU Statechart Tools provide a convenient way to execute your generator while you are developing it.
-			<br/>Therefore, you have to create a new 
-			<strong>Generator Model</strong> with the generator id 
-			<strong>yakindu::generic</strong>, either by using the 
-			<strong>New Statechart Generator Model</strong> wizard or by simple creating a new text file with the file extension 
-			<strong>.sgen</strong>. the following feature allows to configure your code generator.
-		</p>
-		<p><!-- Start sgen_feature_generator --></p>
-		<h4 id="Generator">Generator</h4>
-		<p>The 
-			<strong>Generator</strong> feature allows the configuration of a custom code generator located in the workspace and written in Java or another JVM language. It is a 
-			<strong>required</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>generatorProject</i>  (String, required): The name of the generator project   
-			</li>
-			<li>
-				<i>generatorClass</i>  (String, required): The full qualified class name of the code generator class.
-			</li>
-			<li>
-				<i>configurationModule</i> (String, optional): The full qualified class name for a guice module to configure the code generator 
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature Generator {
-	generatorProject = "org.yakindu.sct.mygenerator"
-	generatorClass = "org.yakindu.sct.MyGenerator"
-}
-		
-</code></pre>
-		<p><!-- End sgen_feature_generator --></p>
-		<h3 id="ExecutingacustomXpandcodegenerator">Executing a custom Xpand code generator</h3>
-		<p>to execute an xpand based custom code generator, you have to create a new 
-			<strong>Generator Model</strong> with the generator id 
-			<strong>yakindu::xpand</strong>, either by using the 
-			<strong>New Statechart Generator Model</strong> wizard or by simple creating a new text file with the file extension 
-			<strong>.sgen</strong>. the following feature allows to configure your code generator.
-		</p>
-		<p><!-- Start sgen_feature_template --></p>
-		<h4 id="Template">Template</h4>
-		<p>The 
-			<strong>Generator</strong> feature allows the configuration of a custom code generator located in the workspace and written in Java or another JVM language. It is a 
-			<strong>required</strong> feature and consists of the following parameters:
-		</p>
-		<ol>
-			<li>
-				<i>templateProject</i>  (String, required): The name of the generator project   
-			</li>
-			<li>
-				<i>templatePath</i>  (String, required): The full qualified template path to the main template.
-			</li>
-		</ol>
-		<p>Example configuration:</p>
-		<pre><code>feature Template {
-	templateProject = "ExampleProject"
-	templatePath = "org::yakindu::sct::generator::xpand::Main::main"
-}
-</code></pre>
-		<p><!-- End sgen_feature_template --></p>
-	</body>
-</html>

plugins/org.yakindu.sct.doc.user/help/user/05_Reference/reference-toc.xml

@@ -1,85 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<toc topic="help/user/05_Reference/reference.html" label="reference">
-	<topic href="help/user/05_Reference/reference.html" label="YAKINDU SCT 2 Reference">
-		<topic href="help/user/05_Reference/reference.html#Statechartelements" label="State chart elements">
-			<topic href="help/user/05_Reference/reference.html#Regions" label="Regions"></topic>
-			<topic href="help/user/05_Reference/reference.html#States" label="States"></topic>
-			<topic href="help/user/05_Reference/reference.html#Transitions" label="Transitions"></topic>
-			<topic href="help/user/05_Reference/reference.html#Initialstateandfinalstate" label="Initial state and final state"></topic>
-			<topic href="help/user/05_Reference/reference.html#Choice" label="Choice"></topic>
-			<topic href="help/user/05_Reference/reference.html#Junction" label="Junction"></topic>
-			<topic href="help/user/05_Reference/reference.html#CompositeState" label="Composite State">
-				<topic href="help/user/05_Reference/reference.html#Orthogonalstates" label="Orthogonal states"></topic>
-				<topic href="help/user/05_Reference/reference.html#Submachinestates" label="Submachine states"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#ShallowHistory" label="Shallow History"></topic>
-			<topic href="help/user/05_Reference/reference.html#DeepHistory" label="Deep History"></topic>
-		</topic>
-		<topic href="help/user/05_Reference/reference.html#Statechartdescriptionlanguage" label="Statechart description language">
-			<topic href="help/user/05_Reference/reference.html#Typesystem" label="Typesystem"></topic>
-			<topic href="help/user/05_Reference/reference.html#Expressions" label="Expressions">
-				<topic href="help/user/05_Reference/reference.html#LogicalAND" label="Logical AND"></topic>
-				<topic href="help/user/05_Reference/reference.html#LogicalOR" label="Logical OR"></topic>
-				<topic href="help/user/05_Reference/reference.html#LogicalNOT" label="Logical NOT"></topic>
-				<topic href="help/user/05_Reference/reference.html#Conditionalexpression" label="Conditional expression"></topic>
-				<topic href="help/user/05_Reference/reference.html#BitwiseXOR" label="Bitwise XOR"></topic>
-				<topic href="help/user/05_Reference/reference.html#BitwiseOR" label="Bitwise OR"></topic>
-				<topic href="help/user/05_Reference/reference.html#BitwiseAND" label="Bitwise AND"></topic>
-				<topic href="help/user/05_Reference/reference.html#LogicalRelationsandShiftOperators" label="Logical Relations and Shift Operators"></topic>
-				<topic href="help/user/05_Reference/reference.html#Binaryarithmeticoperators" label="Binary arithmetic operators"></topic>
-				<topic href="help/user/05_Reference/reference.html#Unaryarithmeticoperators" label="Unary arithmetic operators"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#Statements" label="Statements"></topic>
-			<topic href="help/user/05_Reference/reference.html#Scopes" label="Scopes">
-				<topic href="help/user/05_Reference/reference.html#Namespace" label="Namespace"></topic>
-				<topic href="help/user/05_Reference/reference.html#interfacescope" label="interface scope"></topic>
-				<topic href="help/user/05_Reference/reference.html#internalscope" label="internal scope"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#Declarations" label="Declarations"></topic>
-			<topic href="help/user/05_Reference/reference.html#Events" label="Events"></topic>
-			<topic href="help/user/05_Reference/reference.html#Variables" label="Variables"></topic>
-			<topic href="help/user/05_Reference/reference.html#ReactionTriggers" label="Reaction Triggers">
-				<topic href="help/user/05_Reference/reference.html#after" label="after"></topic>
-				<topic href="help/user/05_Reference/reference.html#every" label="every"></topic>
-				<topic href="help/user/05_Reference/reference.html#always" label="always"></topic>
-				<topic href="help/user/05_Reference/reference.html#defaultelse" label="default, else"></topic>
-				<topic href="help/user/05_Reference/reference.html#entry" label="entry"></topic>
-				<topic href="help/user/05_Reference/reference.html#exit" label="exit"></topic>
-				<topic href="help/user/05_Reference/reference.html#oncycle" label="oncycle"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#Operations" label="Operations"></topic>
-			<topic href="help/user/05_Reference/reference.html#BuildInFunctions" label="Build-In Functions">
-				<topic href="help/user/05_Reference/reference.html#valueofevent" label="valueof(event)"></topic>
-				<topic href="help/user/05_Reference/reference.html#activestate" label="active(state)"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#LocalReactions" label="LocalReactions"></topic>
-			<topic href="help/user/05_Reference/reference.html#EntryPoints" label="EntryPoints"></topic>
-			<topic href="help/user/05_Reference/reference.html#ExitPoints" label="ExitPoints"></topic>
-		</topic>
-		<topic href="help/user/05_Reference/reference.html#SGraph" label="SGraph"></topic>
-		<topic href="help/user/05_Reference/reference.html#SExec" label="SExec"></topic>
-		<topic href="help/user/05_Reference/reference.html#SGen" label="SGen">
-			<topic href="help/user/05_Reference/reference.html#GeneratormodelforJava" label="Generator model for Java">
-				<topic href="help/user/05_Reference/reference.html#FeatureOutlet" label="Feature Outlet"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureLicenseHeader" label="Feature LicenseHeader"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureDebug" label="Feature Debug"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureFunctionInlining" label="Feature FunctionInlining"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureGeneralFeatures" label="Feature GeneralFeatures"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureNaming" label="Feature Naming"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#GeneratormodelforC" label="Generator model for C">
-				<topic href="help/user/05_Reference/reference.html#FeatureOutlet2" label="Feature Outlet"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureLicenseHeader2" label="Feature LicenseHeader"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureDebug2" label="Feature Debug"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureCCodeFeature" label="Feature CCodeFeature"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureFunctionInlining2" label="Feature FunctionInlining"></topic>
-			</topic>
-			<topic href="help/user/05_Reference/reference.html#GeneratormodelforC2" label="Generator model for C++">
-				<topic href="help/user/05_Reference/reference.html#FeatureOutlet3" label="Feature Outlet"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureLicenseHeader3" label="Feature LicenseHeader"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureDebug3" label="Feature Debug"></topic>
-				<topic href="help/user/05_Reference/reference.html#FeatureFunctionInlining3" label="Feature FunctionInlining"></topic>
-			</topic>
-		</topic>
-	</topic>
-</toc>

plugins/org.yakindu.sct.doc.user/plugin.xml

@@ -13,41 +13,17 @@
             primary="false">
       </toc>
       <toc
-            file="help/user/02_Getting_Started/getting_started-toc.xml"
+            file="help/02_Getting_started/tutorial-toc.xml"
             primary="false">
       </toc>
       <toc
-            file="help/user/03_Concepts/concepts-toc.xml"
+            file="help/03_Tasks/tasks-toc.xml"
             primary="false">
       </toc>
       <toc
-            file="help/user/04_Tasks/tasks-toc.xml"
+            file="help/04_Reference/reference-toc.xml"
             primary="false">
       </toc>
-          <toc
-            file="help/user/05_Reference/reference-toc.xml"
-            primary="false">
-      </toc>
-            <toc
-            file="help/developer/02_Getting_Started/getting_started-toc.xml"
-            primary="false">
-      </toc>
-      <toc
-            file="help/developer/03_Concepts/concepts-toc.xml"
-            primary="false">
-      </toc>
-      <toc
-            file="help/developer/04_Tasks/tasks-toc.xml"
-            primary="false">
-      </toc>
-          <toc
-            file="help/developer/05_Reference/reference-toc.xml"
-            primary="false">
-      </toc>
-          <toc
-                file="help/Tutorial/tutorial-toc.xml"
-                primary="false">
-          </toc>
    </extension>
    <extension
          point="org.eclipse.help.contexts">

plugins/org.yakindu.sct.doc.user/toc.xml

@@ -3,7 +3,7 @@
 
 <toc label="Statechart Tools User Guide">
    <link toc="help/01_Overview/overview-toc.xml"/>
-   <link toc="help/Tutorial/tutorial-toc.xml"/>
-   <link toc="help/user/04_Tasks/tasks-toc.xml"/>
-   <link toc="help/user/05_Reference/reference-toc.xml"/>
+   <link toc="help/02_Getting_started/tutorial-toc.xml"/>
+   <link toc="help/03_Tasks/tasks-toc.xml"/>
+   <link toc="help/04_Reference/reference-toc.xml"/>
 </toc>