Custom Query (49 matches)
Results (10 - 12 of 49)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #22 | wontfix | less to css generation | borja | |
| Description |
For the UI (css) we are using less (source:OpenWorkouts/ow/static/less). From the less files we do generate a single (minimized) css file containing all the css code needed for the app. Right now, to do that, we are using a set of nodejs tools, offline, to generate the main css file and then we push it to the repo. First iteration: document the procedure to generate the css file offline Second iteration: Evaluate the posibility of generate that css on-the-fly instead, specially if we can do it using python code instead of nodejs |
|||
| #23 | fixed | Show workouts in the dashboard with date filtering | borja | borja |
| Description |
Right now we show all existing workouts for the user in the dashboard. To improve this, one idea would be to show only the workouts in the last N days, with a filter to get more workouts, something like:
By default we could show the workouts in the current month (later on, if they are too many, maybe we can show them weekly, each 2 weeks...) |
|||
| #26 | fixed | GPX files generation (from .fit/.tcx) | borja | borja |
| Description |
So, right now we can import gpx files, and there are a couple of tickets to support .fit (#13) and .tcx (#25) files too. Those files should be saved, attached to the workout, but then, in order to visualize the tracks in those files in the workout details page, it would be nice to simplify it a bit and use a common format instead of parsing those files again into maps. One idea would be to generate gpx files from .fit, .tcx, etc, so we don't need new js code to show the maps, analysis charts (#16), etc. |
|||
