Le 17/07/2011 22:02, David García Granda a écrit : > This sounds like a sensible change. I'm not sure that activity types >>> should be editable though since it will mean data specific to activity >>> types will be stored in a name/value pair table. A predetermined set >>> of activity types would make for a better schema. >>> >> I agree. I had run into exactly the dilemma you mention - user created >> activity types would pose the problem of associating appropriate labels >> and DB fields. Whilst reviewing my code last night I realized that I had >> abandoned the editable activity types at some point and opted for >> hard-coded categories instead: Resistive, Cardio-Vascular & Weights. >> >> Regarding these new categories - for the sake of agreeing on a term - >> shall we use 'categories' or 'activity types'? Also, the official >> Pytrainer description refers to 'Resistive' sports. Do we want to keep >> this as the activity type/category for cycling, running, etc, or would a >> term such as 'geo-spacial', 'cross-country' or 'distance-based' be >> preferred? Please comment. >> Hi, I'm not sure but the "user created activity types" seems to be useful according Pytrainer categories with CSV imports, GPX imports... I remember I explored source code to do my own "GPX import" for SportsTracker and the categorie seems to be selected from import files if "forced_to" is unchecked.
------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
