[Tickets #2150] Re: Add support for recurring tasks

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/2150
------------------------------------------------------------------------------
  Ticket             | 2150
  Updated By         | Gunnar Wrobel <p at rdus.de>
  Summary            | Add support for recurring tasks
  Queue              | Nag
  Version            | HEAD
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          | 3.0
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Gunnar Wrobel <p at rdus.de> (2008-07-07 00:47) wrote:

> 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.