Open GoogleCodeExporter opened 8 years ago
Or, use drag-n-drop to combine task times ?
Original comment by robert.s...@gmail.com
on 13 Sep 2012 at 6:49
Cool Idea
Original comment by thkee...@gmail.com
on 8 Aug 2014 at 5:47
This is a great app as-is, but being a student and using it for studying
different subjects in a sitting and seeing how much time I've spent on an
individual subject through the app would be a definite boon.
I'm taking a programming course in school, but still need to finish off the
mathematics prerequisites before I can get past my rudimentary understanding.
With that said I would wager a simple and elegant solution is to change the
text input box to a combo text entry/drop-down box that stores entries created
(might have to create a way to clear them too for that "light and airyapp"
feeling, LOL) by the user simply typing in the task they want to time. The
possible ease of this is (hopefully) when the end user selects the item from
the drop-down menu it pulls that object ID and any "history" it has and then
simply starts the time back up again giving a clear overall time for the task.
A real basic text example of what I'm talking about is I put in for a few hours
of study, but I want to take a break between each subject and possibly bounce
between subjects in a night and look back at how long it actually took me to
complete:
Task Name Task ID Current time spent on task Total time spent on
task
MIC 101 UI123 XX:XX:XX XX:XX:XX
Break UI124 XX:XX:XX XX:XX:XX
ITC102 UI125 XX:XX:XX XX:XX:XX
Break UI124 YY:YY:YY XX:XX:XX
EvilMath UI126 XX:XX:XX XX:XX:XX
Break UI124 ZZ:ZZ:ZZ XX:XX:XX
Granted that is more from an understanding of database items, and not objects
used in apps, however I can't imagine the concept if not the actual practice is
too different. I can mock something up in excel if a more interactive visual
example would prove more useful/beneficial.
Sorry, I haven't actually gotten into much of the programming field yet, but I
am so thrilled and I do have some understanding already, but I'm nowhere near
your tallent yet. :-)
Original comment by william....@gmail.com
on 28 Apr 2015 at 5:19
Original issue reported on code.google.com by
michael....@gmail.com
on 15 Aug 2012 at 11:55