twiddle readme
This commit is contained in:
parent
cbe8bf4d4d
commit
543873164e
20
README.md
20
README.md
@ -47,6 +47,8 @@ ratio, or ... some other weirdness)
|
|||||||
|
|
||||||
Use `nix-shell`. Inside the shell
|
Use `nix-shell`. Inside the shell
|
||||||
|
|
||||||
|
* use `make` to build frontend (Elm) and backend (Haskell/Yesod)
|
||||||
|
|
||||||
* run tests with `cabal test --test-show-details=always`: if you don't
|
* run tests with `cabal test --test-show-details=always`: if you don't
|
||||||
ask for details it won't tell you about incomplete pattern matches
|
ask for details it won't tell you about incomplete pattern matches
|
||||||
|
|
||||||
@ -59,8 +61,7 @@ _Do not look below this line_
|
|||||||
|
|
||||||
## WIP, Puzzles and TODO
|
## WIP, Puzzles and TODO
|
||||||
|
|
||||||
* do we even need Track? will it ever be anything more than a collection
|
* rename Track to Gpx, it deals only with parsing.
|
||||||
of Points?
|
|
||||||
* can we lose this "if isJust lat && isJust lon && isJust ts" wart?
|
* can we lose this "if isJust lat && isJust lon && isJust ts" wart?
|
||||||
* probably we should store points in a more efficient form than
|
* probably we should store points in a more efficient form than
|
||||||
a singly-linked list
|
a singly-linked list
|
||||||
@ -78,6 +79,13 @@ _Do not look below this line_
|
|||||||
* could we converge the Point and Trkpt to make sql better?
|
* could we converge the Point and Trkpt to make sql better?
|
||||||
* [done] move Store into Point
|
* [done] move Store into Point
|
||||||
|
|
||||||
|
on timeline, show power, cadence, speed, height, ascent (checkboxes)
|
||||||
|
zoom gesture on graphs causes map to adjust
|
||||||
|
zooming map causes graphs to adjust
|
||||||
|
|
||||||
|
threshold display: adjust vertical slider to show time spent at
|
||||||
|
or above a particular intensity. Indicate somehow the length of
|
||||||
|
each continuous stretch at that intensity
|
||||||
|
|
||||||
|
|
||||||
* calendar displays sessions. a session is a sequence of measurements
|
* calendar displays sessions. a session is a sequence of measurements
|
||||||
@ -96,10 +104,10 @@ _Do not look below this line_
|
|||||||
using information thy have but the computer doesn't
|
using information thy have but the computer doesn't
|
||||||
|
|
||||||
in theory we don't even need draft sessions and we could have the
|
in theory we don't even need draft sessions and we could have the
|
||||||
rider create sessions from the calendar page or the timeline
|
rider create sessions from the calendar page. However, that's a GET
|
||||||
page. However, that's a GET and might be slow if it has to figure out
|
and might be slow if it has to figure out what all the sessions would
|
||||||
what all the sessions would be every time someone looks at it. So
|
be every time someone looks at it. So the draft session is just to
|
||||||
the draft session is just to precompute that and make the view easier
|
precompute that and make the view easier
|
||||||
|
|
||||||
the summary of a session is for display on the calendar and might
|
the summary of a session is for display on the calendar and might
|
||||||
change depending on the nature of the training effort. e.g.
|
change depending on the nature of the training effort. e.g.
|
||||||
|
Loading…
Reference in New Issue
Block a user