[Chandler-dev] Recurrence series modeled as a single item

Mimi Yin mimi at osafoundation.org
Thu Sep 13 06:21:37 PDT 2007


Hi Jeffrey,

Didn't want to derail the framing discussion so split this off into a  
separate thread.

Would remodeling recurrence as a single item solve any / all of the  
following UI problems?
+ The entire series popping into NOW if there's a change made to  
either the entire series or any subset of occurrences in the series.
+ Conflict resolution-related issues with recurrence.
+ Recurrence series splitting into 2 halves when you make a  
THISANDFUTURE edit.
+ Inability to add/remove a single occurrence / subset of occurrences  
from a collection.

Just curious ;)

Mimi

On Sep 6, 2007, at 5:28 PM, Jeffrey Harris wrote:
> If I could, I'd back up to 2005 and model recurring events as one  
> item,
> not many.  The current model is frustrating to work with, but I'm not
> sure how feasible it would be to change this now, so I'm not thinking
> we'll change recurrence any time soon.



More information about the chandler-dev mailing list