diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/StatemachineEditor.dox b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/StatemachineEditor.dox index 784ba6ecf1..80940d4cd0 100644 --- a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/StatemachineEditor.dox +++ b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/StatemachineEditor.dox @@ -1,152 +1,152 @@ /** \page StatemachineEditor How to install and use the Statemachine-Editor \tableofcontents \section StatemachineEditorOverview Overview This plug-in for Eclipse allows you to create new statemachines and change existing statemachines in an graphical editor. You can open existing statemachines from a xml file or create a new statemachine in a new xml file. This document will tell you how to install the plug-in for eclipse and how to use it. \section StatemachineEditorInstallation How to Install the Statemachine-Editor First of all you have to install Eclipse (Eclipse Classic) and the plug-in Graphical Editing Framework (GEF). Furthermore we need the packages JDOM (jdom.jar) and Java3D (vecmath.jar). Caution: There have been problems reported with GEF runtime versions > 3.3.2. A known working configuration is: Eclipse SDK: 3.3.1 J3D: 1.5.1 Jdom: 1.0 GEF runtime: 3.3.2 Java Runtime Environment: jre6 Now you have to unzip the file StateMachines.zip into your eclipse folder. The file is located in your SVN checkout mitk/Modules/MitkExt/Interactions. Start Eclipse and select "File" -> "Import...". \imageMacro{Import.PNG,"\b Fig.1: Import",16} In the popup window (Fig.1: Import) select the folder "Plug-in Development" and "Plug-ins and Fragments". Click "Next >". \imageMacro{Import2.PNG,"\b Fig.2: Import Plug-ins and Fragments",16} On the page "Import Plug-ins and Fragments" ( Fig.2: Import Plug-ins and Fragments) just click "Next >". \imageMacro{Import3.PNG,"\b Fig.3: Selection",16} On the page "Selection" ( Fig.3: Selection) select the "StateMachines (1.0.0)" Plug-in and click the "Add ->" button. \imageMacro{Import4.PNG,"\b Fig.4: Selection 2",16} Click "Finish" ( Fig.4: Selection 2). Now you have to make sure that the path to vecmath.jar and jdom.jar is set correctly. \imageMacro{BuildPath.PNG,"\b Fig.5: Set build path",16} You can find the build path by selecting the project in the "Package Explorer" view. Then go to "Project" -> "Properties" -> "Java Build Path" in the tab "Libraries" (as you can see in Fig.5: Set build path). Now you should be able to start a Run-time Workbench. -\imageMacro{Runas.png,"\b Fig.6: Start Run-time Workbench",16} +\imageMacro{Runas.png,"\b Fig.6: Start Run-time Workbench",9} Therefore you have to press the "Run" button and select "Eclipse Application". Click "OK" (Fig.6: Start Run-time Workbench). A new Eclipse workbench opens where we can use the Statemachine-Editor. \section StatemachineEditorManual How to use the Statemachine-Editor In the Eclipse Run-time Workbench we have to create a new Java project first (Fig.7: Create a new Java project). \imageMacro{CreateJavaProject.PNG,"\b Fig.7: Create a new Java project",16} Then you can select one of the two buttons: \li \ref StatemachineEditorManual1 \li \ref StatemachineEditorManual2 \subsection StatemachineEditorManual1 New Statemachines When you press the button "New Statemachine" the following window will pop up: \imageMacro{NewStatemachine.PNG,"\b Fig.8: New Statemachine",16} Here, you have to "Browse..." for your Java-Project as your file container (Fig.8: New Statemachine). \imageMacro{NewStatemachine1.PNG,"\b Fig.9: New Statemachine 1",16} Select your Project and click "OK" (Fig.9: New Statemachine 1). \imageMacro{NewStatemachine2.PNG,"\b Fig.10: New Statemachine 2",16} As soon as you have selected a container and a File name, the "Finish" button will become enabled (Fig.10: New Statemachine 2). Attention: If the filename has already been used, you have to set another filename to enable the "Finish" button. \imageMacro{NewStatemachine3.PNG,"\b Fig.11: New Statemachine 3",16} As a last step you have to enter the location and name for the xml file to be generated (Fig.11: New Statemachine 3). If you want to have predefined events and actions, make sure the "mitkEventAndActionConstants.xml" file is in the same folder. Read on in Section \ref StatemachineEditorManual3. \subsection StatemachineEditorManual2 Statemachines from *.xml When you press the button "Statemachines from *.xml" the following window will pop up: \imageMacro{openstatemachinexml.png,"\b Fig.12: Open Statemachine from *.xml",16} Here you have to select the xml file, which contains the statemachines (Fig.12: Open Statemachine from *.xml). If you want to have predefined events and actions, make sure the "mitkEventAndActionConstants.xml" file is in the same folder. \imageMacro{specifycontainer.png,"\b Fig.13: Select container",16} Here, you have to "Browse..." for your Java-Project as your file container (Fig.13: Select container). \imageMacro{specifycontainer2.png,"\b Fig.14: Select container 1",16} Select your Project and click "OK" (Fig.14: Select container 1). \imageMacro{specifycontainer3.png,"\b Fig.15: Select container 2",16} As soon as you have selected a container, the "Finish" button will become enabled (Fig.15: Select container 2). Read on in Section \ref StatemachineEditorManual3. \subsection StatemachineEditorManual3 Work with the Editor Now your workspace looks something like this: \imageMacro{application.PNG,"\b Fig.16: Workspace",16} You can open a statemachine from the "Statemachines List" view (Fig.16: Workspace) by performing a double click on the statemachine. An editor opens and on its palette you can find different tools, such as create state or create transition. \imageMacro{openPropertiesView.PNG,"\b Fig.17: Open the properties view",16} \imageMacro{application1.PNG,"\b Fig.18: Change statename in the properties view",16} To edit the statename or state ID you have to open the "Properties" view (Fig.18: Change statename in the properties view). You will get it by "Window"->"Show View" -> "Other..." -> "General" -> "Properties" (Fig.17: Open the properties view). \imageMacro{changeEvent.PNG,"\b Fig.19: Change Event",16} \imageMacro{addAction.PNG,"\b Fig.20: Add Action",16} To change a transitions event or action you have to select the transition and open its context menu (Fig.19: Change Event, Fig.20: Add Action). You can connect a transition to another state by drag one end of it and drop it to another state. All these changes are connected with an undo/redo controller. When you save your statemachine it will be saved as an xml file which you either have created with your new statemachine or have opened before. */ \ No newline at end of file diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Import.PNG b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Import.PNG index f2b68f827f..6ba2eaa02a 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Import.PNG and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Import.PNG differ diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine.PNG b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine.PNG index 3b7210ab3d..642087d3e8 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine.PNG and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine.PNG differ diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine1.PNG b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine1.PNG index 4c182c91b0..d692f776bd 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine1.PNG and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/NewStatemachine1.PNG differ diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Runas.png b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Runas.png index f249c78f7f..f661ab4cd1 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Runas.png and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/Runas.png differ diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer.png b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer.png index ebfc963d60..c53da3ac56 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer.png and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer.png differ diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer2.png b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer2.png index 966cfad381..efe8be1127 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer2.png and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer2.png differ diff --git a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer3.png b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer3.png index fbed7c3603..a397e12828 100644 Binary files a/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer3.png and b/Documentation/Doxygen/DeveloperManual/Starting/FirstSteps/StatemachineEditor/images/specifycontainer3.png differ