Custom Query (49 matches)

Set up a base pyramid install (using zodb template), record and push to darcs repo.

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

Once we have the workouts storage ready (#4), we will need a way to upload gps tracking information to the system, either to an existing workout or (used more often) to create a new workout based on that gps tracking information.

First we have to define which kind of files we will allow (gpx, tcx, fit, etc) and then decide how we will store them: save the files "as is", parse them and save the parsed data into the db (maybe keeping the original file around).

This is directly related to the way we will show data on a map (what kind of files do we need for that, for example, if we are going to use a static file to provide the info when rendering the map).

Once some tracking information has been uploaded, some of that information should be "modifiable" using the workouts editing UI (#4) (we still have to define which info exactly).

Open question: How should we deal with incorrect file uploading? That is, I decide to upload a gps tracking file to a workout, but then I realize that I had chosen the wrong file. How could I fix it?

1. Remove workout, re-upload file and create new workout

2. Upload new file on the existing workout, overwriting existing data

3. (put more options here and let's discuss about it)