[Chandler-dev] Web widgets strategy and proposal

[Travis Vachon]

>
> Proposal
>
> + Get the quick item entry widget working first. This is very useful  
> for the desktop user and high-bandwidth collaborator. It can be put  
> in lots of places - Mimi will talk more about this.
> + The second priority would be the email notifications. Dashboard  
> users and sharees receive an email summarizing the changes that have  
> been made to a particular collection. This reaches out to support  
> mobile devices and enhances the experience for regular users.
> + Implement the editable detail view. This is a great hook where the  
> desktop users can reach out to others.
> + Implement the simple list view in a way they can be viewed by non  
> Chandler users as well as Chandler users. It would be really useful  
> to share a list with others they can edit anonymously in the same  
> way a detail view is.
> + Implement the mini cal and preview pane so they can be viewed by  
> non Chandler users as well as Chandler users.
>
> The goal of this proposal is to support the people who have already  
> bought into Chandler and improve the ability to reach out to more  
> who don't have a clue but might find over time that they are targets  
> for our other core features.
>

Most of this sounds pretty reasonable to me. The email notifications  
bit seems heavier on server work, and afaik was considered second tier  
work on Jared's plate. If we really want to prioritize it as such we  
should probably reconsider our current plan of record on that front.

I think the order for the last three items on the list works fine,  
though the simple list view is likely to be simpler and faster out the  
door in a useful way.

Overall I'm +0 on the specifics, and would be +1 if I had a better  
idea about our plan for notifications.

-Travis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20080213/fe6fe7f6/attachment.html