API Documentation

Classes

EventManager

Functions

manage_addEventManager

EventManager

An Event Manager is a ZCatalog sub class which adds functionality to work with Event Documents.

Additions from ZCatalog: different default indexes different default meta_data catalog awareness calendaring system a layer above the ZCatalog search

Classes

class EventManager

A folder which contains references to Event objects

__module__ = __builtin__

Methods

activeEventsFor(year=None, month=None, day=None, type=None, path=None, sort_on=event_date):

Given a day return a list of MyBrains objects which have a show_date and hide_date the given day falls between.

eventsInRange(start_date, end_date, type=None, path=None):

Return a list of MyBrains objects for events occuring within a date range.

eventsOnDay(year=None, month=None, day=None, type=None):

Return catalogBrains object for all events that occur on the date passed

monthcalendar(self, year, month):

call monthcalendar from the python calendar module. This returns a list of tuples. Each tuple is a week. example: [( 0, 0, 0, 0, 1, 2, 3), ( 4, 5, 6, 7, 8, 9,10), (11,12,13,14,15,16,17), (18,19,20,21,22,23,24), (25,26,27,28,29,30, 0)] this is used to generate the calendar

defaultDayMethod(year=None, month=None, day=None):

monthCalendar requires a method taking (year,month,day) which is called for each day in the month. If that method is missing defaultDayMethod is called.

rdf(year=None, month=None, day=None, type=None, path=None, sort_on=event_date):

Given a day return an rdf+xml representation of the headlines.

getMaster():

Return the master catalog if it exists

Functions

manage_addEventManager(context, id, title=, createCalendar=0, createHeadlines=0, REQUEST=None):

Add an Event Manager Object