[kronolith] Question regarding behaviour of recurring events

[Michael Rubinsky]

A general question for kronolith users on list -

Due to the way ActiveSync devices such as Android and iPhone deal with  
exceptions to recurring events, it has become necessary to keep track  
of an exception's "base" event - the original, recurring event. The  
reason is that an activesync device treats exceptions as a sort of  
"sub event" that is part of the recurring event.  When a recurring  
event on an activesync device is removed, it also removes all events  
that represent exceptions to the recurring event.  This is NOT how  
kronolith currently deals with exceptions. Kronolith adds a new event  
for each exception, and does NOT remove exceptions when recurring  
events are completely deleted. My question is what would the majority  
of users expect the behavior to be in Kronolith when deleting a  
recurring event from within the kronolith interface?

One the one hand, it makes complete sense to remove the exceptions,  
and it would also be consistent with what happens when a user removes  
the exception from his activesync device. On the other hand, it's not  
how kronolith users are used to dealing with removing recurring  
events, so this might lead to unexpected deletion of events. The only  
drawback to leaving it the way it currently works, is that is would be  
inconsistent behavior - they would be removed when deleted from an  
ActiveSync device, but NOT deleted when removed from within Kronolith.

What are everyone's thoughts?

-- 
Mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Reality is merely an illusion, albeit a very persistent one." - A. Einstein