Replying to chandler-dev...

On Mar 15, 2007, at 11:32 AM, Mimi Yin wrote:

Answers in line...or in summary: YYYYYNooooooo

On Mar 15, 2007, at 10: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.

To whoever is implementing the above error icon in the sidebar, you can now ask the Share object if it has any conflicts via share.hasConflicts( ).


   [Yes/No] in the communication status column in the dashboard

Yes.

For a particular item, you can ask sharing.hasConflicts(item) or see if sharing.SharedItem(item).conflictingStates has anything in it.



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.

Morsecode sharing operates on a collection as an atomic unit, so there aren't really per-item errors per se.


   [Yes/No] in the communication status column in the dashboard

Yes.

Ditto.



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

This already is in place, and is the Share object's "error" attribute.


[Yes/No] in the communication status column of all its items in the dashboard


Nooooo.

Gooooood.


--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

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to