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.

So, we started working on the project using darcs as the DVCS for the repos. Then we created a git so some people could work on the project and personally I even considered a third option (mercurial as I do prefer that over the other 2).

This lead to a big mess when trying to keep the repos in sync, plus a big headache to me and a not-very-productive discussion about what to do.

So, BDFL style, I decided to go on with:

• use git as the DVCS tool (for now)

• keep the repos in our openworkouts server

• keep using trac for web access to the repos + tickets/tasks/milestones

• have a mirror in github, with a very big WARNING telling users where the main development and repos goes (trac+git on our server)

I'm not fond of git, but right now this is what we will do.

So, for this ticket, we have to:

• remove/delete darcs and mercurial repos

• put the main git repo (under repos/git/OpenWorkouts-current) into repos/OpenWorkouts

• remove the third-party darcs plugin from trac (as this allows us to update trac to the most recent versions)

• update docs, scripts, tickets, etc to point to the git repo

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:

• 2016
  • march
  • february
  • january
• 2015
  • december
  • november
  • october
  • ...
  • march
  • february
  • january
• 2014
  • ...

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...)