-
Notifications
You must be signed in to change notification settings - Fork 0
/
Tidea Definition.txt
191 lines (183 loc) · 19.6 KB
/
Tidea Definition.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
Tidea means Text Idea, or Idea presented as Text
Tidea is a way of writing, it's neither a source code nor a new data format
Tidea is useful to record knowledge
The below text
presents each idea in 1 line and show relationship between ideas by indent.
Thus, well demonstrate the spirit of Tidea.
Phylosophy
Idea is the most valuable asset, the only thing matter
Idea is a stream of plain text + image + sound inside human brain
Idea has nothing to do with Format, grammar, writing style...
Tidea records and link text + image + sound together in an succinct, informal, platform-independent ways
How Tidea do that?
Ideas are written in plain text files
No special character, no escape character, no markup tag → What you write is what you meant
Only 4 rules:
- Child idea is indented below parent idea by 4 spaces
- Internal link is wrapped by quare brackets: [[...]]
i.e: [[image.jpg]] [[object\spreadsheet.xlsx]] [[C:\test.tex]] http://google.com/
Ctrl+enter will fire up those links
Internal link can have "Jumpto" section after sharp # sign,
i.e: [[C:\test.txt#Section]]
This open test.txt, then jumpto the first text "Section" (similar to common find feature)
Note: To jumpto specific help page in chm file:
Open the chm file > Right click the link to the desired page
The Address (URL) looks like this: mk:@MSITStore:E:\7Utilities\XYplorer\XYplorer.chm::/idh_find.htm#idh_findtabtags
the Internal link will be: [[E:\7Utilities\XYplorer\XYplorer.chm#::/idh_find.htm#idh_findtabtags]]
- Terminology (symbol) is wrapped by 2 colons, i.e: :Black Hole:
- Tidea support very minimal mark-up
Use a few zero-space Unicode characters, i.e:
a Boldtext needs no obstrusive mark-up tag
See table at the end
Benefit
- Any text editor with syntax highlighting capability can render these format
- Even Notepad can view all the content correctly (only lose the format)
- source code looks the same as final deliverable
A few good practice (non-mandatory):
Use mark-up as little as possible
Writing should be short, to the point, no need for lengthy/articulate sentences
Lengthy lines which require word wrap should start with a dash and end with a dot
Very informal, grammar is not needed
Have a root text files contain main ideas then have some internal links to
Other text files
Everything non-text (Image, sound, chart, formula, url...)
To facilitate View on small-screen devices and Printing
Lines should be as short as possible
Each file should have no more than 4 indent level
File Format: txt with Encoding = UTF-16 LE with BOM
View with Fixed width font (i.e: Consolas)
Format
Indent-level = 4-space
Format text
| Format | Code | Name of character | Sample | Width | Sublime Scope |
|-----------|--------|----------------------------|-----------------------|---------------|------------------------------------|
| | | none | http://google.com/ | | entity.name.function.link.external |
| | | [[]] | [[Target.txt]] | | entity.name.function.link.internal |
| | U+2009 | THIN SPACE | foo link bar | 1/5 em | entity.name.function.link.internal |
| | | none | [email protected] | | variable.parameter.link.email |
| | | none | 091234567857 | | constant.numeric |
| Orange | U+202a | Bidirectional text control | fooOrangebar | Zero | variable.parameter, tidea.orange |
| Red | U+200b | Zero-Width-Space | fooRedbar | Zero | keyword.control, tidea.red |
| Gray | U+202c | Bidirectional text control | fooGraybar | Zero | comment.line, tidea.gray |
| Bold | U+200e | Bidirectional text control | fooBoldbar | Zero | tidea.bold |
| Italic | U+200f | Bidirectional text control | fooItalicbar | Zero | tidea.italic |
| Highlight | U+202d | Bidirectional text control | fooHightlightbar | Zero | invalid, tidea.hightlight |
| version | U+1401 | | ver1 ~ᐁ~ ver2 | | |
|-----------|--------|----------------------------|-----------------------|---------------|------------------------------------|
| Unused | U+202e | Bidirectional text control | fooHightlightbar | Zero | |
| Unused | U+202b | Bidirectional text control | fooRedbar | Zero | |
| Unused | U+FEFF | ZERO WIDTH NO-BREAK SPACE | foobar | Zero | |
| Unused | U+200c | Zero-Width-Non-joiner | fooXXbar | Zero | |
| Unused | U+200a | HAIR SPACE | foo bar | <1/6 em | |
| Unused | U+2006 | SIX-PER-EM SPACE | foo bar | 1/6 em | |
| Unused | U+2005 | FOUR-PER-EM SPACE | foo bar | 1/4 em | |
| Unused | U+2004 | THREE-PER-EM SPACE | foo Italic bar | 1/3 em | |
| Unused | U+2000 | EN QUAD | foo Orange bar | 1 en (1/2 em) | |
| Unused | U+2001 | EM QUAD | foo gray bar | 1 em | |
| Unused | U+2002 | EN SPACE | foo red bar | 1 en (1/2 em) | |
| Unused | U+2003 | EM SPACE | foo Bold bar | 1 em | |
http://www.cs.tut.fi/~jkorpela/chars/spaces.html
http://en.wikipedia.org/wiki/Unicode_control_characters
[[obj\Tidea format in Microsoft Word.docx]]
To enter math: [[obj\Plain Text Math.pdf]]
Another table using Unicode Box Drawing symbols:
┌───────────┬─────┬───────────┐
│ Name │ Age │ Phone │
├───────────┼─────┼───────────┤
│ Anna │ 32 │ 123456789 │
├───────────┼─────┼───────────┤
│ Alexander │ 28 │ 987654321 │
└───────────┴─────┴───────────┘
File naming convention:
SortInfo1.SortInfo2, Identity ~ Tag1, Tag2,.txt
A large subject can be broken down like this:
Tax.Procedure.txt
Tax.Process.txt
Tax.Regulation.txt
Tax.Regulation.CIT.txt
Tax.Regulation.PIT.txt
Tax.Regulation.VAT.txt
To visualize relationship between files
FileName contain a recognizable Identity (fairly-unique, standard name)
Relationship type
Create/Modify/supporting info is denoted as +
Terminate is denoted as -
Upstream/Downstream: Relationship type (+-) is placed before or after target file's Identifier
i.e: "13.2013.TT.BTC, VAT law, VN, +21.2012, 23.2013-.docx" => 13.2013 modify 21.2012 AND being nullified by 23.2013
Law:
"210.2012.TT.BTC, Tomtatnoidung, EN, -SoVanBanBiHuy, +SoVabBanBiDieuChinh.docx"
Appendix and PDF signed version should be attached inside main file
EN version is separated
Example:
Comment
(ftp:\/\/|https?:\/\/)?(\w\.)?([\w-]+)\.[a-z]{2,6}(\.|\/)[\/\w\.-:~]*
Optional ftp:// or http:// or https:// Domain en.wiki.com Subpages /football#Rules
Insert this in .tmtheme:
<dict>
<key>name</key>
<string>Tidea: Unicode Symbol</string>
<key>scope</key>
<string>unicode.symbol</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#1BBC43</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>tidea.red</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#F92672</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>tidea.orange</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#FD971F</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>tidea.hightlight</string>
<key>settings</key>
<dict>
<key>background</key>
<string>#FFFF00</string>
<key>foreground</key>
<string>#222222</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>tidea.bold</string>
<key>settings</key>
<dict>
<key>fontStyle</key>
<string>bold</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>tidea.italic</string>
<key>settings</key>
<dict>
<key>fontStyle</key>
<string>italic</string>
</dict>
</dict>
<dict>
<key>scope</key>
<string>tidea.gray</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#75715E</string>
</dict>
</dict>