From 543873164ee705d9aec5c7300ab0af85a91963f7 Mon Sep 17 00:00:00 2001 From: Daniel Barlow Date: Tue, 12 Nov 2024 00:20:48 +0000 Subject: [PATCH] twiddle readme --- README.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 096d2b0..33e8e91 100644 --- a/README.md +++ b/README.md @@ -47,6 +47,8 @@ ratio, or ... some other weirdness) 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 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 -* do we even need Track? will it ever be anything more than a collection - of Points? +* rename Track to Gpx, it deals only with parsing. * can we lose this "if isJust lat && isJust lon && isJust ts" wart? * probably we should store points in a more efficient form than 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? * [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 @@ -96,10 +104,10 @@ _Do not look below this line_ using information thy have but the computer doesn't in theory we don't even need draft sessions and we could have the -rider create sessions from the calendar page or the timeline -page. However, that's a GET and might be slow if it has to figure out -what all the sessions would be every time someone looks at it. So -the draft session is just to precompute that and make the view easier +rider create sessions from the calendar page. However, that's a GET +and might be slow if it has to figure out what all the sessions would +be every time someone looks at it. So the draft session is just to +precompute that and make the view easier the summary of a session is for display on the calendar and might change depending on the nature of the training effort. e.g.