| Sending this discussion to the design list. We are discussing how to model the notion of 'Go offline' for the user. In Chandler, we have 2 flavors of 'Go offline'. One applies to email and the other applies to sharing. For email, 'Go offline' could apply to all email or to individual email accounts. (Although we will not be supporting the latter use case in Preview.) For sharing 'Go offline' could apply to all sharing, individual collections or individual sharing accounts. (Again, we will not be supporting the individual account use case in Preview.) For both email and sharing, 'Go offline' means stop all network activity. + For email, that means: Don't pull new mail down from the server. Don't send email. + For sharing, it means: Don't sync my changes. Don't pull changes from the server. Open Issue: How do we present 'Go offline' to the user? As separate menu items? + Go offline for Email in the File menu. + Go offline for Sharing in the Share menu. OR As a single, hierarchical menu item under the Share menu? + Go offline>> - Selected collection (if the selected collection is shared) ---------------------------- - All - Shares - Email Mimi |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
