The Following 29 Users Say Thank You to aspidites For This Useful Post: | ||
![]() |
2010-05-08
, 23:24
|
Posts: 10 |
Thanked: 3 times |
Joined on May 2010
|
#2
|
![]() |
2010-05-08
, 23:39
|
Posts: 114 |
Thanked: 62 times |
Joined on Jan 2010
|
#3
|
The Following User Says Thank You to cryox92 For This Useful Post: | ||
![]() |
2010-05-08
, 23:48
|
Posts: 402 |
Thanked: 229 times |
Joined on Nov 2009
@ Missouri, USA
|
#4
|
- Has a name, description, target (cardio, weight lifting), with a sub-target (heart rate, calorie burning, triceps, etc), and a reference picture/video
- Has a name, description, location, duration (target reps, sets, distance) and frequency (weight, speed, etc)
The Following User Says Thank You to aspidites For This Useful Post: | ||
![]() |
2010-05-09
, 00:01
|
Posts: 114 |
Thanked: 62 times |
Joined on Jan 2010
|
#5
|
Before I can continue development, I need a come up with a database schema. So far, I'm sure I at least need two tables as follows:
- Exercise
- Has a name, description, target (cardio, weight lifting), with a sub-target (heart rate, calorie burning, triceps, etc), and a reference picture/video
- Workout
- Has a name, description, location, duration (target reps, sets, distance) and frequency (weight, speed, etc)
I don't work out nearly as much as I ought to, so I know I'm missing something. Any feedback on this (or better naming for certain things) would be greatly appreciated.
![]() |
2010-05-09
, 00:16
|
Posts: 249 |
Thanked: 167 times |
Joined on Mar 2010
@ International
|
#6
|
Before I can continue development, I need a come up with a database schema. So far, I'm sure I at least need two tables as follows:
- Exercise
- Has a name, description, target (cardio, weight lifting), with a sub-target (heart rate, calorie burning, triceps, etc), and a reference picture/video
- Workout
- Has a name, description, location, duration (target reps, sets, distance) and frequency (weight, speed, etc)
I don't work out nearly as much as I ought to, so I know I'm missing something. Any feedback on this (or better naming for certain things) would be greatly appreciated.
The Following User Says Thank You to gryedouge For This Useful Post: | ||
![]() |
2010-05-09
, 00:50
|
Posts: 402 |
Thanked: 229 times |
Joined on Nov 2009
@ Missouri, USA
|
#7
|
![]() |
2010-05-09
, 00:59
|
Posts: 10 |
Thanked: 3 times |
Joined on May 2010
|
#8
|
![]() |
2010-05-09
, 01:15
|
Posts: 402 |
Thanked: 229 times |
Joined on Nov 2009
@ Missouri, USA
|
#9
|
![]() |
2010-05-09
, 01:25
|
Posts: 999 |
Thanked: 1,117 times |
Joined on Dec 2009
@ earth?
|
#10
|
The reason for posting this in development and not applications is that I literally just started working on it 10 minutes ago. Plus, I want some community feedback on where this should go.
Feel free to make suggestions, but please make sure to read the known issues and road map sections below first.
Code is available @ gitorious and from extras-devel. Once it is actually useful, I'll promote it to extras-testing.
Known Issues
- I can't seem to find a Qt equivalent for gtk.HILDON_SIZE_THUMB_HEIGHT.
- I haven't found a way for tell QWizard to align buttons horizontally when in portrait mode (Hoping I don't have to subclass QWizardPage)
- QSqlDatabase warning on exit. Harmless, but annoying.
- Thumbnails aren't available for exercises where a video is chosen as the example.
- Auto-rotate doesn't always operate correctly. This is a known Qt for Maemo bug, so nothing I can do about it.
- When deleting multiple exercises/routines/target areas, if you press the back button, no transition is shown. This is an implementation issue that doesn't really affect usability and would require a rewrite of some components. I may fix this before 1.0.0, but I doubt it.
Road MapTrying to set the horizontal sizing policy to expanding or prefered leads to ugly background repeating
If an 'x' is mentioned in the version name, the feature is planned for inclusion, but has yet to be slated for a release. Bold items are things that have been changed since this post's last edit.'Please remember that features listed are tentative. That is, I may at any time change my mind and not implement them at all.
[not started]: planned, but no code exists
[incomplete]: code exists, but not finished
[in progress]: what I'm currently focusing on
[complete]: erm...done coding
Screenshots (as of 6/6/2010)
aspidites | blog | aspidites@inbox.com
Last edited by aspidites; 2010-07-20 at 08:22.