On Wed, 16 May 2007, Simon Wistow wrote:
On Wed, May 16, 2007 at 04:46:56PM +0100, Zefram said:
A "recurring event" is not a single event. It is a structured group of
events. You should have distinct classes for single event and recurrence.
Most of the methods you list are applicable to one class or the other,
not both.
Hmm, I disagree. In every calendaring system I've come across a
recurring event and a single event are represented as the same thing
only with different properties. A recurring event is a single entity -
it is one thing and should only be stored one time.
I think you're mixing together the end-user view of an event and the
program API view.
Clearly, when one is programming a calendar system, recurring and single
events would have to have some different properties.
Using your description, a one-off event could be described as a
structured group containing only one event.
That's not a bad idea.
A better distinction might be between a recurring event (every Tuesday at
noon) and a specific instance of that recurring event (May 15 at noon).
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/
