ProofScriptParser issueshttps://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues2018-09-25T03:44:00+02:00https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/19Implement Filter for List of Goals2018-09-25T03:44:00+02:00tk5165Implement Filter for List of GoalsImplementation of the filter functionality of the `ListView` for current `GoalNode`.
(see the current `ListGoalViewMenu`)
* [ ] Input Dialog for Terms and Strings
* [ ] reuse the KeyMatcherAPI
* [ ] show hint beside the list, that a fi...Implementation of the filter functionality of the `ListView` for current `GoalNode`.
(see the current `ListGoalViewMenu`)
* [ ] Input Dialog for Terms and Strings
* [ ] reuse the KeyMatcherAPI
* [ ] show hint beside the list, that a filter is activated.https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/14Make a Difference between selected goal node in the interpreter and UI2017-06-05T23:34:37+02:00tk5165Make a Difference between selected goal node in the interpreter and UIDuring debugging we have two selected goal nodes.
1. The selection in the UI made by the user.
2. The selected node in the interpreter.
* [ ] distinguish both in the `listGoalView` (e.g. by color or text marker)
* [ ] allow user to ...During debugging we have two selected goal nodes.
1. The selection in the UI made by the user.
2. The selected node in the interpreter.
* [ ] distinguish both in the `listGoalView` (e.g. by color or text marker)
* [ ] allow user to set the selected node in the interpreter
* [ ] via the context menu `Set this Node as selected by the Interpreter`
* [ ] Sync-Mode, automatically set the UI-selected node in the interpreter.Feature Complete 1.0https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/12Concept of Editing and Restart a Proof Script2018-09-25T03:44:51+02:00tk5165Concept of Editing and Restart a Proof ScriptWe need a concept/workflow for editing and restart of proof scripts.
1. We record the set of goal nodes (and also key nodes) at the beginning of every statement.
2. We can ignore all commands call until a certain position.
From this...We need a concept/workflow for editing and restart of proof scripts.
1. We record the set of goal nodes (and also key nodes) at the beginning of every statement.
2. We can ignore all commands call until a certain position.
From this we can create an editing concept, answering following question:
* What is the user allowed to edit in debug mode?
* How can base upon the current interpreter state (pruning, call ignoring)?Feature Complete 1.0https://git.scc.kit.edu/xt9634/ProofScriptParser/-/issues/5Dokumentation2017-04-30T19:47:13+02:00tk5165Dokumentation