GothenburgBitFactory/timewarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/timewarrior.git synced 2025-07-07 20:06:39 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Docs: Migrated notes to data.txt

Browse source
This commit is contained in:
Paul Beckingham 2015-12-17 00:42:09 -05:00
parent 07a50d67b1
commit 2462ab1271
2 changed files with 13 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/data.txt
View file

@ -28,3 +28,16 @@ P: Instead of one day per line, one interval per line:
The first has no 'end' timestamp, and is therefore an open track, ie active The first has no 'end' timestamp, and is therefore an open track, ie active
now. The second is a bounded range. now. The second is a bounded range.
F: have an archive file as well?(edited)
P: I was thinking that we could auto-archive, moving out records older than X into another file. Queries would then know in advance whether it needed to read the archive.
F: Should there be a possibility to freeze entries?
P: hmm. Good point, I tihnk yes.
For old data? Or so that a workweek redefine has no effect?
F: the first yes. the latter, hm. perhaps. would make sense to get the reports correct that depend on that.
--> If old data is frozen, what does that mean? It should mean that the inclusions and exclusions are collapsed, and the net inclusions recorded and frozen. This prevents changes to the work week from modifying old information.

24
doc/notes.txt
View file

@ -301,28 +301,4 @@ P: There is a use-case for double tracking. Suppose I am a manager, and I do th
It could have a start date, which means “cannot bill before next month”. It could have a start date, which means “cannot bill before next month”.
Could also define overlap. This could be implemented using Rules. Could also define overlap. This could be implemented using Rules.
P: Final topic on my list: Data Format, and it’s very short.
data is a text file. one line per day.
Example:
2015-12-10 9am-10am “painting door”, 10am-11:29am “meeting with x”, 1:32pm-5pm “training"
Minimal. readable. Comma-separated intervals.
JSON would be more than twice as long. Available via ‘export’.
Could alternatively be one line per interval. Not sure it matters
F: have an archive file as well?(edited)
P: I was thinking that we could auto-archive, moving out records older than X into another file. Queries would then know in advance whether it needed to read the archive.
Think about the volume though: a month is 31 lines of text. Nothing.
F: not performance wise. just to reduce the clutter.
P: Agreed.
F: Should there be a possibility to freeze entries?
P: hmm. Good point, I tihnk yes.
For old data? Or so that a workweek redefine has no effect?
F: the first yes. the latter, hm. perhaps. would make sense to get the reports correct that depend on that.
--> If old data is frozen, what does that mean? It should mean that the inclusions and exclusions are collapsed, and the net inclusions recorded and frozen. This prevents changes to the work week from modifying old information.
--- ---