Hi, > First let me introduce myself: > > I'm called Siggi, and I'm new around here. I started using pyTrainer a > few months ago, when I got my ForeRunner 305. To cut a long story short, > I love the program enough to want to help to make it even better, both > in terms of ironing out flaws and in adding new features. I happen to be > quite experienced when it comes to Python development, having used the > language on a more or less daily basis professionally for some years > now. However, I'm must admit to being a total newbie in GTK, Glade and > Python GUI work in general.
Welcome Siggi and thanks very much for your contibution. > I started out a few weeks ago and cut my teeth on a couple of minor > tickets. I now have a sizeable changeset to contribute. The contents: > > - a new "Totals" tab, along the lines of that suggested in ticket #60, > with a table of aggregate info for each sport, ordered by descending > duration. It also includes a graph with a bar for each year. I found that pytrainer refuses to start due to some issue with data retrieved (trying to add None to int). I have just submitted a dirty hack [767] to overcome it, but I guess the source for this is some kind of corruption of data stored in my pytrainer database (old entries, manual updates, etc.) that might happen to someone else. > - extension of the stacked/colored graph of the Week view to Day, > Month, Year and Totals. > - refactoring of day/week/month/year(/totals) graph code, introducing a > base class "TimeGraph", eliminating some pretty severe code duplication I should put more attention on code changes... > - I had also done speed coloring on the Google maps, but Jonathan's > implementation is better than mine, so I scrapped the latter. I am > contributing an extension of the coloring to HR and cadence*, and a > combobox to select None/Speed/HR/Cadence. > * (The cadence coloring is untested, as I don't have a cadence > sensor or footpod. Can someone try it out?) I would need to have a look on this because now I see all track paths coloured in green regardless running at 4'/km or 6'/km. Heartrate seems to work fine as I can see track path's colour changing. Sorry I can't talk about cadence 0:-) > A pending issue with the stacked graphs is the fact that the values > "Average HR" and "Average speed" don't play nice with the others, i.e. > it doesn't make any sense to add them up. On the other hand, if you do > want to trace your progress in terms of HR or speed, you probably want > to do it for a single sport anyway, in which case this is really a > non-issue. Being able to produce the nonsensical stacked heart rates > still bothers me, though. I agree it doesn't make sense to present them in stacked bars, but it does if both figures could be represented in line graph, it would be interesting to see them combined with time or distance represented in bars. So I would propose: Distance, Time -> bar graph (change in magnitude) Speed, Calories, HeartRate -> line graph (change in direction) Any ideas? Regards, David ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
