[Design] Clarification on error icons

[Brian Kirsch]

Hello,
We should also be explicit in defining what happens when a mail send  
fails.
I do populate the item.errors attribute so the info is there.

If an error happens when sending an item, should Chandler show an  
error icon:

   [Yes/No] next to the relevant collection in the sidebar
   [Yes/No] in the communication status column in the dashboard


-Brian

On Mar 15, 2007, at 7:36 AM, Grant Baillie wrote:

> Howdy, y'all
>
> There was a discussion today on #chandler about error icons, and  
> Morgen, stearns and I wanted to clarify what determines the various  
> possible "error" states:
>
> 1) If a conflict arises on an item, should Chandler show an error  
> icon:
>
>    [Yes/No] next to the relevant collection in the sidebar
>    [Yes/No] in the communication status column in the dashboard
>
> 2) If there's an error during syncing of one particular item that's  
> not a conflict(*), should Chandler show an error icon:
>
>    [Yes/No] next to the relevant collection in the sidebar
>    [Yes/No] in the communication status column in the dashboard
>
> 3) If there's an error during sharing that's not associated with a  
> particular item (e.g. the server can't be reached), should Chandler  
> show an error icon:
>
>    [Yes/No] next to the relevant collection in the sidebar
>    [Yes/No] in the communication status column of all its items in  
> the dashboard
>
> --Grant
>
> (*) This would usually be the result of a client or server bug, I  
> think.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design