[Cosmo-dev] Cosmo WebUI Service Layer

[Ted Leung]

Here are my comments after a first round of reading:

=== Use case section
I think there may be some additional use cases the fall out of things  
that you might do in the dashboard.  For example:
* Return a collection filtered by criteria? - like all items due in  
the last 5 minutes (whatever our client side timer period is)
* Saving Event Details and Deleting Events - shouldn't this be  
generalized to support any kind of item (tasks and notes at least?)
* What about dealing with Stamps?

=== Conduits section
I feel pretty strongly that app code should be using the Conduit API  
as little as possible.

=== MDC Syntax section

"this._conduit.save(this);"
This seems like a code smell to have to explicitly do the  
delegation.  Isn't there some Javascript prototype thing that we can  
to do implement this delegation automatically?

Also, in Chandler, Collections are Items - I'm not saying we have to  
do it this way, but wanted to be sure you knew that.

Ted

On Mar 2, 2007, at 4:47 PM, Travis Vachon wrote:

> Hi folks
>
> As part of Bobby and my continuing series of proposals for  
> dashboard plumbing, I'd like to request comments on http:// 
> wiki.osafoundation.org/Projects/CosmoWebUIServiceLayerProposal
>
> - Travis
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev