-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO
44 lines (33 loc) · 1.73 KB
/
TODO
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
TODO List for Journal
*) Have separate bands for each data type in the diary view (not so useful
in the lifeline view).
Hmm, that won't really work, because a "highlight" band can only sync
with a single band -- the you wouldn't get the neat "summary" view. Ahh,
but you could have multiple highlight bands, one per data type band.
- In the lifeline, you could have multiple bands based on tags. A
"relationships" band, a "housing" band, "jobs", "concerts", etc. Any
event/period whose tag doesn't correspond to a user-defined band is
rendered in the "other/misc" band. Lets people segment however they
want.
*) A narrow band at the top that somehow has an on-click to bring up an
"add an entry/event/period/whatever" dialog.
*) Add per-decade clicky bits on the lifeline page, and per-month and
next/prev year on diary.
*) BikeRide mileage should be a float. Duration should either take time
in HH:MM, or just be removed.
*) Better rendering of event detail.
http://code.google.com/p/simile-widgets/wiki/Timeline_CustomEventDetailDisplay
We fetch bubble detail via AJAX, should we then cache it? If so, how to
invalidate cache?
*) Get rid of 'duration' attr on Activity.
SQL FOR SCHEMA & DATA CHANGES
alter table diary_period change start_date start_date date null;
alter table diary_period change end_date end_date date null;
alter table diary_activity add `date` date not null;
update diary_activity a join diary_entry e on e.entry_id = a.entry_id
set a.date=e.date;
alter table diary_activity drop column entry_id;
alter table diary_medical_observation add `date` date not null;
update diary_medical_observation mo join diary_entry e on e.entry_id = mo.entry_id
set mo.date=e.date;
alter table diary_medical_observation drop column entry_id;