Lisa Dusseault wrote:
- One of them stores only recurrence masters and exceptions in their repository. When the client needs to display a time period, it asks for a list of events in that time period, and the model logic constructs objects for recurrence instances as well as for regular events, and hands that list off. Changes may be made to instances or non-recurring events, and the model logic handles that either way. I believe this is the pure "virtual event" model that Jeffrey originally proposed.
this is what i've been expecting to do within cosmo. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
