Custom Query (49 matches)

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.

There are some texts around the app that are gathered dynamically, like:

• month names

• day names

• sport names

• gender

Those should be translated too.

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)