Custom Query (49 matches)
Results (40 - 42 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 |
|||
| #17 | fixed | When adding a workout (manually) show a field to choose the type of workout | borja | borja |
| Description |
Right now we show an input text field and all workouts are saved as "gymnastics" by default. We have to keep track of posible workout types and allow the user to choose. |
|||
| #14 | fixed | Timezone support | borja | borja |
| Description |
Right now, when we load data from a GPX file, it is in UTC/GMT. We do not show this anywhere in the app, and we should improve this a bit. First iteration: Save datetime objects as objects with no timezone, then display them all in UTC/GMT, telling the user about it. Second iteration: Allow users to set their timezone, then display dates and times in that timezone for that user. |
|||
