[Cosmo-dev] Cosmo 0.6.1 model changes

[Randy Letness]

Brian Moseley wrote:
>
> for item mods, where do you propose to put this new updateEvent
> method? on NoteItem, EventStamp, or somewhere else?
>

Either make it a service method, or a utility function that also uses a 
ContentService object.  The problem is that multiple items may be 
created/deleted/updated, so access to the service api is a must.

> 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
> apis directly.
>

Right, and i was thinking for 0.6.1 the ui should use the same apis as 
caldav and can switch to dealing with individual modification items in 0.7

> do your estimates include the effort to make dav, mc and the ui work
> properly or just the effort needed to make them compile?

As long as it compiles we can ship it right??  Actually I didn't include 
time for refactoring morse code (finalizing record types, handling those 
types, etc).  Thats probably at least 2-3 days work.

-Randy