Beads issueshttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues2019-06-20T13:56:02+02:00https://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/60More Languages2019-06-20T13:56:02+02:00Adrian WuillemetMore Languages**User Story:**
> As a user I want to be able to choose from a set of default programming languages.
**Definition of Done:**
+ The following programming languages are supported:
- Java
- Python
- Javascript
- C#
- C++
...**User Story:**
> As a user I want to be able to choose from a set of default programming languages.
**Definition of Done:**
+ The following programming languages are supported:
- Java
- Python
- Javascript
- C#
- C++
- Ruby
+ Optionally other languages can be considered.
___
**Implementation Tasks:**
+ [ ] Add templates where possible
+ [ ] Extend generation where neccessary
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>9</td>
<td>-</td>
</tr>
</table>Deployable BetaRico PossienkaRico Possienkahttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/56Add Initial State type2019-07-11T21:11:25+02:00Adrian WuillemetAdd Initial State type**User Story:**
> As a user I want to define the initial state of the state machine.
**Definition of Done:**
+ States can be marked as 'initial'
+ Initial states are correctly set in the code
+ Validation can handle initial states
+ In...**User Story:**
> As a user I want to define the initial state of the state machine.
**Definition of Done:**
+ States can be marked as 'initial'
+ Initial states are correctly set in the code
+ Validation can handle initial states
+ Initial states are optional
+ If no initial state is given, the use will be notified about the one set by default
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>7</td>
<td>Validation, Code generation, Selection of nodes in the GUI</td>
</tr>
</table>Deployable Betahttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/51Behaviour Trees2019-05-30T14:57:30+02:00Adrian WuillemetBehaviour Trees**User Story:**
> As a user I want to be able to create behaviour trees
**Definition of Done:**
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>100</td>
<td>-</td>
</tr>
</table>**User Story:**
> As a user I want to be able to create behaviour trees
**Definition of Done:**
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>100</td>
<td>-</td>
</tr>
</table>https://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/40Python Logging setup2019-07-11T21:04:32+02:00Adrian WuillemetPython Logging setupResearch and demonstrate easy to use logging for possible verbose mode.Research and demonstrate easy to use logging for possible verbose mode.Alpha VersionMarcoMarcohttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/27Provide initial logic entry point2019-07-11T21:04:15+02:00Rico PossienkaProvide initial logic entry pointlogic.py
logic.py
Alpha VersionMarcoMarcohttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/23Generate code from a fine state machine2019-06-03T22:10:35+02:00Adrian WuillemetGenerate code from a fine state machine**User Story:**
> As a user I want to be able to generate code by passing a fine state machine
**Definition of Done:**
+ Providing a representation of a fsm leads to printing of valid code that resembles the fsm on the commandline.
___...**User Story:**
> As a user I want to be able to generate code by passing a fine state machine
**Definition of Done:**
+ Providing a representation of a fsm leads to printing of valid code that resembles the fsm on the commandline.
___
**Implementation Tasks:**
+ [x] Define template for languages
+ [x] parse fsm to dictionary model
+ [x] generate code from fsm model
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<td>13</td>
<td>
-
</td>
<tr>
</tr>
</table>Alpha VersionAdrian WuillemetAdrian Wuillemethttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/15Basic validation2019-06-07T14:15:07+02:00Adrian WuillemetBasic validation**User Story:**
> As a user I want to know that my FSM was validated before the code was generated
**Definition of Done:**
+ A provided fsm is validated
+ Feedback is given on command line about successful and failed validation
___
**...**User Story:**
> As a user I want to know that my FSM was validated before the code was generated
**Definition of Done:**
+ A provided fsm is validated
+ Feedback is given on command line about successful and failed validation
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>13</td>
<td>Validation</td>
</tr>
</table>Deployable BetaAdrian WuillemetAdrian Wuillemethttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/13Creating Code from the GUI2019-06-07T14:14:40+02:00Adrian WuillemetCreating Code from the GUI**User Story:**
> As a user I want to be able to generate and view code in the GUI
**Definition of Done:**
+ Correct code is displayed in the gui
+ The code resembles the drawn fsm
___
**Implementation Tasks:**
___
<table>
<tr>
<th>S...**User Story:**
> As a user I want to be able to generate and view code in the GUI
**Definition of Done:**
+ Correct code is displayed in the gui
+ The code resembles the drawn fsm
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>5</td>
<td>Drawing FSMs</td>
</tr>
</table>Deployable BetaPavel NepkePavel Nepkehttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/12Save Code from the GUI2019-07-11T20:59:23+02:00Adrian WuillemetSave Code from the GUI**User Story:**
> As a user I want to be to generated code from the GUI
**Definition of Done:**
+ Valid code is saved locally in a file
+ Code resembles the drawn fsm
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th...**User Story:**
> As a user I want to be to generated code from the GUI
**Definition of Done:**
+ Valid code is saved locally in a file
+ Code resembles the drawn fsm
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>8</td>
<td>Drawing FSMs</td>
</tr>
</table>Deployable BetaRico PossienkaRico Possienkahttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/11Export FSM into DOT2019-05-30T14:35:18+02:00Adrian WuillemetExport FSM into DOT**User Story:**
> As a user I want to be able to export the FSM from the GUI into a graphviz DOT file
**Definition of Done:**
+ A drawn fsm can be exported as a DOT file.
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints...**User Story:**
> As a user I want to be able to export the FSM from the GUI into a graphviz DOT file
**Definition of Done:**
+ A drawn fsm can be exported as a DOT file.
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>5</td>
<td>Drawing of FSMs</td>
</tr>
</table>https://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/10Pass multiple files as input to the CLI2019-07-11T21:01:46+02:00Adrian WuillemetPass multiple files as input to the CLI**User Story:**
> As a user I want to be able to pass multiple files as arguments to the command line tool
**Definition of Done:**
+ The cli can handle multiple files as arguments for one command
___
**Implementation Tasks:**
+ [x] C...**User Story:**
> As a user I want to be able to pass multiple files as arguments to the command line tool
**Definition of Done:**
+ The cli can handle multiple files as arguments for one command
___
**Implementation Tasks:**
+ [x] Change parse option 'file' to 'files'
+ [x] Change option type to multiple
+ [x] adopt runners pipelines to handle multiple inputs
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<td>7</td>
<td>Running CLI</td>
<tr>
</tr>
</table>MarcoMarcohttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/6Add output dir and file option2019-05-31T15:51:31+02:00Adrian WuillemetAdd output dir and file option**User Story:**
> As a user I want to be able to pass the output directory / file of the generated code as an option
**Definition of Done:**
+ The output directory can be provided to the cli command
+ Resulting code will be saved in a ...**User Story:**
> As a user I want to be able to pass the output directory / file of the generated code as an option
**Definition of Done:**
+ The output directory can be provided to the cli command
+ Resulting code will be saved in a file in the provided directory
+ An invalid directory will result in program abort with descriptive error message
+ Standard cli help exists for the option
+ The filename can be provided to the cli command
+ Resulting code will be saved to a file with the given name
+ Standard behaviour for existing files is applied
___
**Implementation Tasks:**
+ [x] Extend CLI command with '-o', '--out-dir' option
+ [x] Extend CLI command with '-f', '--file-name' option
+ [X] Pass provided argument to the responsible scripts
+ [x] Use provided option in logic to write resulting code
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>?</td>
<td>Write files</td>
</tr>
</table>Alpha VersionAdrian WuillemetAdrian Wuillemethttps://gitlab.beuth-hochschule.de/s40242/stategen/-/issues/3Add export into PNG2019-07-11T21:01:46+02:00Adrian WuillemetAdd export into PNG**User Story:**
> As a user I want to be able to export the FSM from the GUI into a PNG file
**Definition of Done:**
+ A drawn FSM can be exported as .png file.
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>...**User Story:**
> As a user I want to be able to export the FSM from the GUI into a PNG file
**Definition of Done:**
+ A drawn FSM can be exported as .png file.
___
**Implementation Tasks:**
___
<table>
<tr>
<th>Storypoints</th>
<th>Requires</th>
</tr>
<tr>
<td>8</td>
<td>Drawing of FSMs</td>
</tr>
</table>Adrian WuillemetAdrian Wuillemet