| Summary | Add support for recurring tasks |
| Queue | Nag |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Feedback |
| Priority | 1. Low |
| Owners | |
| Requester | kevin_myer (at) iu13 (dot) org |
| Created | 06/17/2005 (1113 days ago) |
| Due | |
| Updated | 07/04/2008 (today) |
| Assigned | |
| Resolved | |
| Attachments | HK-GW-Recurrence.patch ![]() |
| Milestone | 3.0 |
| Patch | Yes |
Patch ⇒ 1
Milestone ⇒ 3.0
State ⇒ Feedback
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!
New Attachment: HK-GW-Recurrence.patch
for the kolab driver so far. Does this go into the right direction?
Queue ⇒ Nag
Summary ⇒ Add support for recurring tasks
State ⇒ New
Type ⇒ Enhancement
Priority ⇒ 1. Low
to use the recurrence portion of the iCalendar spec.