Hi, > Perhaps it's adequate to just allow speed to > be input as either pace or velocity. Have updated the wireframe to > show this.
Declaring those inputs as exclusive ones is definitely the right way, good. > You shouldn't need preferred_velocity_representation configuration > because the UI can just remember what was used last time. Right, could be enough. I'm no advocate of stuffing more things into the DB, but such a pre_vel_rep could also could be used when showing activities: ie graphs, lap-splits. Here IMHO pytrainer should become a bit smarter and simpler (however this is achieved ;). The attribute could also be None or empty then defining something stationary. Another idea: Routes could carry an attribute of sports type they are typically associated with (maybe list to allow multiple usage). This would minimize needed clicks to create a record even more - or give better overviews e.g. in route management. > If we want to satisfy other sports (for example, rowing, which > measures pace as a 500m split time) then we would need to look into > what Werner van Staden had suggested for activity types back in July. I missed the discussion in July (holidays) but now reread the thread. Thx for pointing there. cu Arnd ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
