|
1 | 1 | CTT-editor
|
2 | 2 | ==========
|
3 | 3 |
|
4 |
| -Concurrent task tree editor |
| 4 | +Concurrent Task Tree editor |
| 5 | + |
5 | 6 | A straightforward way to write CTTs in plain text, with a fast visualiser.
|
6 | 7 |
|
7 | 8 |
|
8 | 9 | TODO:
|
9 | 10 | -----
|
10 |
| -Be able to refer to tasks defined in another file. |
11 |
| -Generate enabled task sets |
12 |
| -- Check more cases with Disabling task |
13 |
| -- Allow to collapse []>> operators |
14 |
| -- Slide 11, how does second way to interpret an [optional-task] work? |
15 |
| -Generate HTML pages from CTT |
16 |
| -Check CTT on problems: |
17 |
| -- Syntax in text file |
18 |
| -- exercise 1: A looping task without deactivation |
19 |
| -- exercise 2: Or operations [] between optional tasks |
20 |
| -- exercise 3: Ambiguity in order of operations |
21 |
| -- exercise 4: Select task, before something is shown |
22 |
| -- exercise 6: UI specific words, like 'click' |
| 11 | +- Be able to refer to tasks defined in another file. |
| 12 | +- Generate enabled task sets |
| 13 | + - Check more cases with Disabling task |
| 14 | + - Allow to collapse []>> operators |
| 15 | + - Slide 11, how does second way to interpret an [optional-task] work? |
| 16 | +- Generate HTML pages from CTT |
| 17 | +- Check CTT on problems: |
| 18 | + - Syntax in text file |
| 19 | + - exercise 1: A looping task without deactivation |
| 20 | + - exercise 2: Or operations [] between optional tasks |
| 21 | + - exercise 3: Ambiguity in order of operations |
| 22 | + - exercise 4: Select task, before something is shown |
| 23 | + - exercise 6: UI specific words, like 'click' |
23 | 24 |
|
24 | 25 |
|
25 | 26 | Some things I learned:
|
|
0 commit comments