[Cosmo-dev] Incremental Topics Proposal

[Matthew Eernisse]

Responses below ...

Bobby Rullo wrote:
> Phase I - Assessment and Documentation
> ----------
> Go through existing topic publish/subscribe calls, and document what 
> they do, what's in a message, who is using them.

Probably the hairiest stuff in there will be in cosmo/view/cal.js. 
There's a lot of context getting passed with published messages to allow 
the UI to figure out how to respond to successes/failures when editing 
or removing.

I think most of the other use of topics is pretty straightforward, and 
will be pretty easy to document.

> Phase III - Formalization
> ----------
> Formalize remaining topics - remove calendar specific names, use 
> declared objects for messages, use constants instead of strings, make 
> API more consistent where need be.

Excellent. I'd like to vote strongly that in this process we err on the 
side of keeping things nice and simple -- I'd like to avoid tricky stuff 
as much as we can.

It will be good to get this stuff formalized.

Thanks.


Matthew