Morgen Sågen wrote:
Yes, it's one item. Chandler will show the user the item with their local changes, and (obviously) not write those back to the read-only share on the server. If afterwards someone else changes the item in the read-only share, Chandler will show a pending change on the item that the user can choose to apply/discard. The sharing framework allows Chandler to maintain the differences between a local copy of an item and any number of shares.
The problem would be that they are local changes in Chandler, but not in the web ui, which would have to deal with two different items. So a user may see changes locally that they won't see when using the web ui. Maybe this is something we can live with.
-Randy _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
