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
|
[[wn.private:Taskmanagers]]
= Part 1 =
notation:
`item` :: item of type
`[item]` :: list of item's
`{item}` :: optional item
--------------------------------------------------
{{{
[project]
project:
- title
- started
- {deadline}
- [link]
- [update]
update:
- title
- pub-date
- {body}
- }}}
--------------------------------------------------
tt list
tt note <id>
tt list <id>
--------------------------------------------------
{{{sql
sqlite example tables
create table projects (
id primary key not null,
title text not null,
started datetime not null,
deadline datetime
);
create table links (
id primary key not null,
project_id integer not null,
url text
);
create table updates (
id primary key not null,
project_id integer not null,
pub_date datetime not null,
title text not null,
body text
);
}}}
= Part 2 =
[ ] Possibly database, with sepparate frontend
I want multiple frontends.
The goal would be to have easy access from
the notes anywhere, be it a terminal, a web
browser or a smartphone.
I probably want the terminal based to act
something like a mix between mutt and git
commit trees.
- Vim Frontend
Probably a bad idea. So much of the time
would be spend converting between the text
file and the database spec.
- Curses based
Something like mutt
- overview
I want a calendar view, even if the program is
an agenda manager in its core.
= Part 3 =
Möjligheten att spara undan listor, vilka kan om-initialiseras gång på
gång, t.ex. en packlista, eller följand lista efter ett föreningsmöte:
- [ ] Efter mötet
- [ ] Uppdatera maillistor efter nyval
- [ ] Uppdatera webbsidan efter nyval
- [ ] Uppdatera unixgrupper efter nyval
Men låt samtidigt extra underpunkter läggas till vilka inte ändrar den
permanenta mallen.
= Part 4 =
Tasks should be able to block each other
but with high enough priority / deadline close enough they should show
despite the block
= Part 5 =
{{{SQL
CREATE TABLE IF NOT EXISTS task
( id INTEGER PRIMARY KEY NOT NULL
, description TEXT NOT NULL
, priority INTEGER NOT NULL DEFAULT 0
, blocked_by INTEGER
, parent INTEGER
, FOREIGN KEY (parent) REFERENCES task (id)
, FOREIGN KEY (blocked_by) REFERENCES task (id)
)
}}}
|
