[kronolith] reccuring events: exceptions?

[Jesse Wolff]

Yeah, great question. 

Exceptions could be actual inserts to the db that are checked against when the 
nextRecurrance is being calculated? It might be feasible because these records 
could just be included in the current SQL select therefore not added extra 
calls to the db. I'm not familiar with mcal so of course this only applies to 
the sql driver.

This leads to another question. When a recurring event is viewed or edited 
should the original event dates and times be displayed (as it is currently) or 
should the specific instance date and times be displayed along with an 
indication that it's a recurring event. I think I'd prefer the later.

> but this week it occurs on Thursday at 6pm, or has been cancelled,

Then if you delete a specific instance of the recurrance a "cancelled" record 
could be inserted to the db. If you change the date or time, you could insert 
a "cancelled" record to the db, and then insert a new event for Thursday at 6pm 
in your example.

Just my first thoughts.

Jesse.


Quoting kellan <kellan@protest.net>:

> Hi, I've been watching kronolith off and on for a while, its great to see
> it making so much progress lately.
> 
> I'm working on rewriting the calendar system behind protest.net in the
> hopes of being able to open source it. (currently its proprietary)  And I
> wanted to pick your brains :)
> 
> With recurring events there are two roads one can go, either expand the
> event at insert time, or at display time.  Currently we expand at
> insertion time up to a fixed number of events.  But I think this is
> inelegant in the extreme.  I notice that Kronolith opts for the second
> route, expanding at display time.
> 
> The one feature I haven't figured out how to code under this model is
> exceptions.  It doesn't look like kronolith supports this yet either, but
> I was wondering if you had any thoughts about it.
> 
> By exceptions I mean, "We have an event that repeats every Wednesday, at
> 4pm", but this week it occurs on Thursday at 6pm, or has been cancelled,
> etc...
> 
> Any thoughts?  Insights. (btw.  I don't see the protest.net rewrite as
> being competition for kronolith as its is and will be heavily focused on
> event calendars, and away from a PIM like functionality)
> 
> thanks,
> kellan
> 
> --
> Dotcoms didn't make the world a better place.
> They weren't trying to. Rest in Peace.
> 
> kellan@protest.net
> 
> 
> -- 
> Kronolith mailing list: http://horde.org/kronolith/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: kronolith-unsubscribe@lists.horde.org
>