Workouts storage

[borja]

Design and implement a way to store workouts information for a given user:

• title
• description
• Date and time when the workout starts
• Date and time when the workout ends
• Kind of workout/activity (cycling, running, kayaking... - define a list of sports we allow to track at first)
• Some more information, probably depending on the kind of workout/activity:
  • distance
  • laps (+lap distance/time)
  • rounds/games (tennis table, basketball, football) (save distance/time per round/game)
  • ????

Add any other information you would think would be useful for new workouts.

+ views to list/view/add/edit/remove workouts

[betabug]

"Date and time when the workout ends" -> e... uses start + duration, makes more sense when manually entering workouts.

The kind of workouts, we should go by the list that is defined for the FIT file format, it is pretty comprehensive, and we will have the advantage of being aligned when we can import FIT files. We can then add others for manual workouts.

Distance: I've used km now in the code (same as e... does) for manual workouts. Laps, rounds, games... dunno how these could make sense.

[borja]

So far we have this quite advanced, I think it is time to move on splitting this one into smaller subtasks.

We have a base Workout model that stores the data, we have views to add, update, edit and delete workouts and views to show a list of workouts and a workouts detail page.

Check revisions up to [109/OpenWorkouts] for a detailed timeline of changes there.

[borja]

Milestone renamed

[borja]

Milestone renamed