time inherited from DateTime
DateTime::Schedule contains one or more events.
If you try the former:
DateTime::Event - who what where added, time inherited from DateTime,
list of DateTime added as DateTime::Schedule if a recurrning event
it doens't seem to fit. Heck, it doesn't even REA
me.
-Original Message-
From: Dave Rolsky [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 16, 2007 2:04 PM
To: datetime
Subject: Re: DateTime::Event again
On Wed, 16 May 2007, Simon Wistow wrote:
> On Wed, May 16, 2007 at 04:46:56PM +0100, Zefram said:
>> A "recurring event&
07 2:04 PM
To: datetime
Subject: Re: DateTime::Event again
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 cl
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 c
On 5/16/07, Simon Wistow <[EMAIL PROTECTED]> wrote:
I've started sketching out DateTime::Event - a module that would
represent a single, err, event.
It's based on my experiences with the Palm Calendar, Google Calendar and
the iCalendar standard.
Eventually it's my hope that there'd would be num
Simon Wistow wrote:
> 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.
Bad OO design is very common. Especially, I have found, where dates
and times are concerned.
>
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
Simon Wistow wrote:
>I've started sketching out DateTime::Event - a module that would
>represent a single, err, event.
...
>The problem we have here is that for one off events start and end are
>definite points in time. For recurring events this merely represents the
>earliest and latest instanc
I've started sketching out DateTime::Event - a module that would
represent a single, err, event.
It's based on my experiences with the Palm Calendar, Google Calendar and
the iCalendar standard.
Eventually it's my hope that there'd would be numerous implementations
of DateTime::Event::Provider
