[Design] Clarification on error icons

[Mimi Yin]

I'm not sure users need to know the difference between errors and  
conflicts. Both should provoke the user to look at the item to see  
what's happened to it. So I'm leery of adding more icons to decipher.  
Perhaps we could rename the icon: Alert? So that it's neither Error  
nor conflict?

Mimi

On Mar 20, 2007, at 12:00 AM, Davor Cubranic wrote:

> Grant Baillie wrote:
>> 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
>>
> A conflict is not really conceptually the same as a sync error,  
> though, is it? It's something that needs user's action to resolve  
> it, so I agree that some kind of indicator is needed, but I would  
> argue for a different symbol from "technical" errors like losing  
> connection to the server or a bug causing an exception during the  
> sync.
>
> Davor
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design