Browse Source

Added idea on dependencies

Alois Mahdal 11 years ago
parent
commit
df326e2de9
2 changed files with 58 additions and 0 deletions
  1. 4
    0
      TODO.md
  2. 54
    0
      ideas/dependency.md

+ 4
- 0
TODO.md View File

@@ -8,6 +8,10 @@
8 8
 
9 9
 *   TC dependency issues
10 10
 
11
+    *   [ideas/dependency.md][1]
12
+
13
+  [1]: ideas/dependency.md
14
+
11 15
 
12 16
 ### Data model ###
13 17
 

+ 54
- 0
ideas/dependency.md View File

@@ -0,0 +1,54 @@
1
+Notes: example to show idea of dependency markup
2
+
3
+
4
+# Demo: Dependency markup #
5
+
6
+This is for demonstration of way of showing dependency.
7
+
8
+The idea is to use dependency points.  The dependency point (DP) is a special
9
+TC that is identified by `{ID}`, where ID conforms to a unix path.
10
+
11
+*   the divider is `/`
12
+
13
+*   one special case is root DP, which has has name `/`
14
+
15
+*   you can call DP by something like `{/env2/}`. Scope of this declaration
16
+    is downwards, until next one or end
17
+
18
+
19
+## {/} prepare env=0 ##
20
+ 1. `x = 1`
21
+ 2. `y = 2`
22
+ 3. `m =`
23
+
24
+## {/env2} prepare env called 1 ##
25
+ 1. prepare env0
26
+ 2. `m = one`
27
+
28
+## {/env2} prepare something two ##
29
+ 1. prepare env0
30
+ 2. `m = two`
31
+
32
+{/env1/}
33
+
34
+## case 1.1 ##
35
+ 1. prepare env1
36
+ 2. do thing 1.1.1
37
+ 3. do thing 1.1.2
38
+
39
+## case 1.2 ##
40
+ 2. do thing 1.2.1
41
+ 3. do thing 1.2.2
42
+
43
+{/env2/}
44
+
45
+## case 2.1 ##
46
+ 1. prepare env2
47
+ 2. do thing 2.1.2
48
+ 3. do thing 2.1.2
49
+
50
+## case 2.2 ##
51
+ 1. prepare env2
52
+ 2. do thing 2.2.1
53
+ 3. do thing 2.2.2
54
+