ProofScriptParser issueshttps://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues2018-11-23T15:46:40+01:00https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/55Add Variable View to GoalOptionsView2018-11-23T15:46:40+01:00sarah.grebingAdd Variable View to GoalOptionsView1. [x] Add inspection Model
2. [x] Show new Window with table
3. [x] Fix Bug: model.getSelectedGoalNodeToShow().getAssignments() in GoalOptionsMenu.java:67 ins always empty;
Example Contraposition + script varDecl()
4. [x] Add Tabpane...1. [x] Add inspection Model
2. [x] Show new Window with table
3. [x] Fix Bug: model.getSelectedGoalNodeToShow().getAssignments() in GoalOptionsMenu.java:67 ins always empty;
Example Contraposition + script varDecl()
4. [x] Add Tabpane with special ScriptVariables (starting with __)
5. [x] Prettify colum witdh
6. [ ] Remove empty colums, needs css
7. [ ] Write testcase/testuudmkuudmkhttps://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/56Compact script after exiting interactive mode2018-11-14T11:24:35+01:00uudmkCompact script after exiting interactive mode* [x] remove empty CaseStatements
* [x] remove empty interlaced CasesStatements
* [x] remove empty CaseStatements
* [x] remove empty interlaced CasesStatements
uudmkuudmkhttps://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/52Autocompletion does not work as intended2018-10-05T19:11:46+02:00sarah.grebingAutocompletion does not work as intendedIt is impossible to choose the suggestions by the autocompletion using mouse or keyboard.
The input events are not handled.It is impossible to choose the suggestions by the autocompletion using mouse or keyboard.
The input events are not handled.tk5165tk5165https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/17Support Interaction in Sequent View2018-09-25T03:40:29+02:00tk5165Support Interaction in Sequent View* [x] Support the user by showing the applicable rules for a selected term in the sequent
* [x] Create an appropriate `RuleCommand` call for a selected applicable rule in the script area.* [x] Support the user by showing the applicable rules for a selected term in the sequent
* [x] Create an appropriate `RuleCommand` call for a selected applicable rule in the script area.https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/22Concept and Implemetation of Explorative Debug Features2018-09-25T03:37:56+02:00sarah.grebingConcept and Implemetation of Explorative Debug Features* [ ] Informal Definition of different explorative features
* [ ] Implementation and interaction Concept
* [ ] Implementation* [ ] Informal Definition of different explorative features
* [ ] Implementation and interaction Concept
* [ ] Implementationsarah.grebingsarah.grebinghttps://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/16Tabs for ScriptArea2017-11-03T02:37:24+01:00tk5165Tabs for ScriptAreaDuring debugging, a jump into a different is possible.
For support of this event, e.g. `Step Into`, a tabbed pane or
accordion is necessary (maybe `DockFX` or `AnchorFX`).
There should be a concept for the entry point script, (e.g. t...During debugging, a jump into a different is possible.
For support of this event, e.g. `Step Into`, a tabbed pane or
accordion is necessary (maybe `DockFX` or `AnchorFX`).
There should be a concept for the entry point script, (e.g. the first script from the tab).
In connection to #15Feature Complete 1.0