[#2150] Add support for recurring tasks
Summary Add support for recurring tasks
Queue Nag
Queue Version HEAD
Type Enhancement
State Assigned
Priority 1. Low
Owners Gunnar Wrobel <p (at) rdus (dot) de>
Requester kevin_myer (at) iu13 (dot) org
Created 06/17/2005 (1477 days ago)
Due
Updated 11/05/2008 (240 days ago)
Assigned 11/05/2008 (240 days ago)
Resolved
Attachments HK-GW-Recurrence[3].patch Download
Milestone 3.0
Patch No

History
11/05/2008 Chuck Hagenbuch Patch ⇒
Assigned to Gunnar Wrobel
State ⇒ Assigned
 
10/24/2008 Jan Schneider Comment #11
State ⇒ Feedback		 Reply to this comment
It's still missing support in the SQL driver, and the form field 
renderer still includes HTML code that doesn't belong there. Field 
renderers must only contain the code for the actual fields. You add 
all kind of form row layout that is the job of the form renders (as 
opposed to the field renderer). If you want to add more then one 
(html) field in the form field renderer, separate them by simple 
breaks, or what ever fit your needs, but don't re-use or interrupt the 
regular form rendering with tables (because other renderers than the 
default might use a different rendering technique than tables).
10/24/2008 Jan Schneider Deleted Attachment: HK-GW-Recurrence[2].patch
 
09/16/2008 Gunnar Wrobel Comment #10
New Attachment: HK-GW-Recurrence[3].patch Download
State ⇒ Assigned		 Reply to this comment
Updated to the latest CVS.

I added the required JavaScript functionality now. So the patch should 
be complete feature wise.

I'm still a layman when it comes to JS and Horde Forms. So there might 
be some JS corrections necessary. As usual I'm open to suggestions :)

Thanks!
07/15/2008 Jan Schneider Deleted Attachment: HK-GW-Recurrence[1].patch
 
07/15/2008 Gunnar Wrobel Comment #9
New Attachment: HK-GW-Recurrence[2].patch		 Reply to this comment
Updated the patch. The var renderers are hopefully okay now.

There are some java script issues left and the whole recurrence part 
should only be shown if there exists a due date for the task. Maybe it 
is already okay for a first commit and some polishing in CVS.
07/13/2008 Jan Schneider Comment #8 Reply to this comment
I already committed Recurrence.php.
07/13/2008 CVS Commit Comment #7 Reply to this comment
Changes have been made in CVS for this ticket:

http://cvs.horde.org/co.php/nag/lib/Recurrence.php?r=1.1
07/07/2008 Jan Schneider Deleted Attachment: HK-GW-Recurrence.patch
 
07/07/2008 Gunnar Wrobel Comment #6 Reply to this comment
Horde_Form_Type_nag_recurrence should use $vars instead of 
Util::getFormData() and Nag_Recurrence instead of 
Horde_Date_Recurrance. And we probably have to use different 
constant names to avoid collisions when showing tasks in Kronolith. 
I just see you already did this, but you don't use them everywhere 
yet.
Fixed.
The varrenderers won't work the way you implemented them though. 
Either you need different form fields for the different recurrence 
settings, or you have to implement the complete widget in a single 
cell, like any other form field.
This is not yet fixed. I'll need to take a closer look at how var 
renderers work.
And you shouldn't create new tasks when completing one recurrence 
instance. Instead, you should store the completion of a single 
recurrence, similar to how exceptions are stored at the moment. And 
of course we should (at some point, not necessarily from the start) 
add the ability to actually create exceptions.
Adapted the patch to the new completion support in the recurrence library.
07/07/2008 Gunnar Wrobel Comment #5
New Attachment: HK-GW-Recurrence[1].patch		 Reply to this comment
Second draft version.
07/06/2008 Gunnar Wrobel Comment #4 Reply to this comment
And you shouldn't create new tasks when completing one recurrence 
instance. Instead, you should store the completion of a single 
recurrence, similar to how exceptions are stored at the moment. And 
of course we should (at some point, not necessarily from the start) 
add the ability to actually create exceptions.
Makes a lot of sense. I submitted a suggestion as for completion 
support in recurrences as bug #7029

07/04/2008 Jan Schneider Comment #3
Patch ⇒ 1
Milestone ⇒ 3.0
State ⇒ Feedback		 Reply to this comment
Horde_Form_Type_nag_recurrence should use $vars instead of 
Util::getFormData() and Nag_Recurrence instead of 
Horde_Date_Recurrance. And we probably have to use different constant 
names to avoid collisions when showing tasks in Kronolith. I just see 
you already did this, but you don't use them everywhere yet.

The varrenderers won't work the way you implemented them though. 
Either you need different form fields for the different recurrence 
settings, or you have to implement the complete widget in a single 
cell, like any other form field.

And you shouldn't create new tasks when completing one recurrence 
instance. Instead, you should store the completion of a single 
recurrence, similar to how exceptions are stored at the moment. And of 
course we should (at some point, not necessarily from the start) add 
the ability to actually create exceptions.

But beside that, it looks very promising, nice work!
07/04/2008 Gunnar Wrobel Comment #2
New Attachment: HK-GW-Recurrence.patch		 Reply to this comment
A draft for implementing recurrence in Nag. I did only implement it 
for the kolab driver so far. Does this go into the right direction?
07/30/2007 Chuck Hagenbuch State ⇒ Stalled
 
07/28/2005 Jan Schneider State ⇒ Accepted
 
06/17/2005 kevin_myer (at) iu13 (dot) org Comment #1
Summary ⇒ Add support for recurring tasks
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New
Queue ⇒ Nag		 Reply to this comment
Support recurrence in tasks.  Should just be a matter of extending Nag 
to use the recurrence portion of the iCalendar spec.