Group tasks so long breaks can be used

[GoogleCodeExporter]

(Note:  I just posted a bunch of separate "issues," over the last few days, but 
I just want to make it clear to anyone who reads this that after trying SEVERAL 
pomodoro timers over the last year, Pomodairo is IMHO the BEST one out there BY 
FAR, for at least 2 reasons:  1.) The current features work beautifully with a 
surprisingly simple UI; and 2.) The creator does the BEST job of quickly and 
graciously responding to people's ideas, whether they are bad or good, and 
updating the program with bug fixes and people's suggestions.)

Issue 96 is similar to this, but the issue (again, IMO) is less about creating 
"Sub-tasks" and more about grouping multiple tasks together to make a 
4-pomodoro set that will allow for the long break timer to be used.  Currently 
(unless I'm doing something wrong) the long break only works after a task has 
been assigned 4 pomodoros.

While one could just put x number of things all in the one Task Name slot, and 
then set it for 4, I think it would be a LOT better if you were able to keep 
the 4 pomodoros separate (for allow accurate self-tracking, as well as accurate 
tracking of interruptions, task management, etc.)

I have a few suggestions on how to resolve this, and I apologize if they suck ;)

1.  Just make it so that the program automatically does a long break after 4 
pomodoros.

2.  Use the current formatting, but expand it and turn "Tasks" into "Task Sets" 
- when you click "New Task", instead of one line for a name and pomodoro 
estimate, have 4 lines for 4 different tasks.  Ideally, you would be able to 
not use all 4 lines and still use pomodoro estimates (as opposed to, for 
example, typing a 2-pom. task twice, each with 1-pom.) - the tasks listed would 
just have to add to 4 pomodoros total.

3. Have the program automatically move to the next task down on the list, after 
the previous task has reached it's pomodoro limit.  I'm not sure if this is 
feasible, since more problems would probably be created - If more or less 
pomodoros are needed, etc.

Again, this app RULES, and I appreciate Fredrick for making this!!

Original issue reported on code.google.com by michael....@gmail.com on 2 Jan 2011 at 8:01

[GoogleCodeExporter]

#1 This should be the current implementation. If it is not, then it is a bug... 
I.e. the long break should come after 4 pomodoros (default) regardless what 
tasks you are working with. I'll try to verify this.

#2 This should have to be done since #1 should work properly =)

#3 I am not sure it would be a good idea. The limit is only an estimate and as 
such you are allowed (and even expected) to go above it sometimes. The GUI does 
pop up (somewhat confusingly perhaps) a little 'next' button that selects the 
next task in order which simplifies it a little bit.

Please correct me if I got it wrong =)

Original comment by fredrikj...@gmail.com on 4 Jan 2011 at 9:48

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Fredrik - Thanks for responding, and I apologize for misspelling your name in 
my previous post!

#1  I looked at this further, and it seems to be working as long as I don't 
close the program - closing the program seems to restart the program's internal 
pomodoro counter, which may have been why I've been having trouble.  I'll be 
using it all day today, so I'll look at it more, but this may have been 
confusion on my part (in which case, I am a moron, and I apologize for the 
post!).

#2-3  As you said, if #1 works, my #2-3 are irrelevant.

However, it would be nice to have some sort of task break down when multiple 
tasks are grouped into 1 pomodoro (this is a different issue from the above, 
though maybe my #2 suggestion could be implemented for this purpose instead of 
for the 4-pomodoro set issue).  My reasoning for this is because many times I 
add several small tasks into one pomodoro, which results in that pomodoro 
having a long "name."  As a result, the Pomodoro name becomes partially blocked 
by other stuff in the UI, especially in the condensed view.  It would also be 
nice to cross/check off the smaller tasks once completed during the pomodoro.

Original comment by michael....@gmail.com on 4 Jan 2011 at 1:50