Sun, 07 Sep 2008 16:37:35 -0400 http://bugs.horde.org/ticket/2150 Add support for recurring tasks Support recurrence in tasks. Should just be a matter of extending Nag to use the recurrence portion of the iCalendar spec. Fri, 17 Jun 2005 10:56:50 -0400 http://bugs.horde.org/ticket/2150#t9212 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? Fri, 04 Jul 2008 10:28:57 -0400 http://bugs.horde.org/ticket/2150#t47209 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! Fri, 04 Jul 2008 11:06:51 -0400 http://bugs.horde.org/ticket/2150#t47212 > 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 Sun, 06 Jul 2008 09:58:40 -0400 http://bugs.horde.org/ticket/2150#t47249 Second draft version. Mon, 07 Jul 2008 00:46:28 -0400 http://bugs.horde.org/ticket/2150#t47335 > 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. Mon, 07 Jul 2008 00:47:44 -0400 http://bugs.horde.org/ticket/2150#t47336 Changes have been made in CVS for this ticket: http://cvs.horde.org/co.php/nag/lib/Recurrence.php?r=1.1 Sun, 13 Jul 2008 08:36:05 -0400 http://bugs.horde.org/ticket/2150#t47492 I already committed Recurrence.php. Sun, 13 Jul 2008 08:36:43 -0400 http://bugs.horde.org/ticket/2150#t47493 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. Tue, 15 Jul 2008 07:04:38 -0400 http://bugs.horde.org/ticket/2150#t47546