[Cosmo-dev] Cosmo 0.6.1 model changes
bcm at osafoundation.org
Fri Feb 9 12:48:15 PST 2007
On 2/9/07, Randy Letness <randy at osafoundation.org> wrote:
> Here is a first pass at what I think(based on discussions on sharing) is
> required for 0.6.1 as far as model changes go:
> Check it out when you get a chance and let me know if things don't make
> sense/won't work/are missing/etc.
pretty much what i had imagined.
for items in multiple collections, like you i'm most worried about how
this impacts dav. i can't think of anything specific at the moment.
for item mods, where do you propose to put this new updateEvent
method? on NoteItem, EventStamp, or somewhere else?
since we're going to try to do some amount of dashboard work in 0.7,
it seems like the ui is going to need apis to deal with modifications
directly. caldav, on the other hand, will never need to know about
them. this implies that updateEvent will be a convenience api that dav
will always want to use, even when the ui moves to using modification
do your estimates include the effort to make dav, mc and the ui work
properly or just the effort needed to make them compile?
More information about the cosmo-dev