Re: [PHPiCalendar-DEV] COUNT

[Jo R. <jr...@sv...>]

On Sun, Sep 17, 2006 at 03:05:19PM -0500, Jim Hu wrote:
> If we're on the same wavelength, I'm thinking that the parser would  
> create a collection of calendar objects, where there are two classes  
> that extend calendar_item (I'm making up names) - calendar_event and  
> calendar_todo.  This collection of events would be used instead of  
> the master array.  As the template system steps through the time  
> interval to be drawn, it would send messages to each event/todo as  
> appropriate: "Do you need this time slot?"  If the answer is yes,  
> then the calendar_item returns the information needed to draw that  
> part of the calendar.
 
Well, as part of the OO I would think that each of these items "has a"
schedule object.  That object defines the information about the schedule.
This would allow a consistent interface to asking objects about their
schedule.

calendar_event
	is a calendar_item
	has a schedule

calendar_todo
	is a calendar_item
	(optionally) has a schedule

..etc

Or perhaps

calendar_item
	has a schedule

calendar_event
	is a calendar_item

calendar_todo
	is a calendar_item

I don't think that the latter would make the most sense, but it all depends
on implementation.

-- 
Jo Rhett
senior geek
SVcolo : Silicon Valley Colocation