Add documentation file
This commit is contained in:
parent
a7c9c39af5
commit
0033d1b4b4
2 changed files with 53 additions and 0 deletions
52
doc/src/05100-lib-timetrack.md
Normal file
52
doc/src/05100-lib-timetrack.md
Normal file
|
@ -0,0 +1,52 @@
|
|||
## libimagtimetrack
|
||||
|
||||
A library for tracking time events in the imag store.
|
||||
|
||||
### Store format
|
||||
|
||||
Events are stored with a store id like this:
|
||||
|
||||
```
|
||||
/timetrack/<insert-date-year>/<insert-date-month>/<insert-date-day>/<insert-date-time>-<tag>.ext
|
||||
```
|
||||
|
||||
Timetrackings contain
|
||||
|
||||
* a comment (optional, free text)
|
||||
* a start date
|
||||
* an end date
|
||||
* a tag
|
||||
|
||||
by default and might be extended with more header fields as one likes.
|
||||
|
||||
The header of a timetrack "work" entry looks like this:
|
||||
|
||||
```toml
|
||||
[event]
|
||||
tag = "work"
|
||||
start = "2017-01-02T03:04:05"
|
||||
end = "2017-01-02T06:07:08"
|
||||
```
|
||||
|
||||
Normal tags (as in `libimagentrytag`) are explicitely _not_ used for tagging,
|
||||
so the user has the possibility to use normal tags on these entries as well.
|
||||
|
||||
The `tag` field is of type string, as for one tag, one entry is created. This
|
||||
way, one can track overlapping tags, as in:
|
||||
|
||||
```bash
|
||||
imag timetrack start foo
|
||||
imag timetrack start bar
|
||||
imag timetrack stop foo
|
||||
imag timetrack start baz
|
||||
imag timetrack stop bar
|
||||
imag timetrack stop baz
|
||||
```
|
||||
|
||||
The `end` field is, of course, only set if the event already ended.
|
||||
|
||||
### Library functionality
|
||||
|
||||
The library uses the `libimagentrydatetime::datepath::DatePathBuilder` for
|
||||
building `StoreId` objects.
|
||||
|
1
libimagtimetrack/README.md
Symbolic link
1
libimagtimetrack/README.md
Symbolic link
|
@ -0,0 +1 @@
|
|||
../doc/src/05100-lib-timetrack.md
|
Loading…
Reference in a new issue