I have put together a spec for alpha 2 background sync.
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_7/ Sharing-0.7.html
Mimi, Morgen and I have been discussing the following issues offlist and thought it was appropriate to send to the design list...
1) Should import/export be background tasks as well - should the user be able to work on other things while these operations are taking place? I would probably make sense to have this running in the background as well given that we want to unify the experience for getting data in/out of Chandler.
2) What happens when the user clicks Sync All. Do they get the modal dialog - probably not. It makes sense for this to simply force a background sync. Basically this means there would be no more Modal- Lock-Me-Out-of-Chandler sync. We would have no dialog popup when the sync finishes either.
3) If a background sync is running and the user clicks "sync all" what happens? The current sync will quit and start again. Does the user need any feedback in this situation?
4) Since we are eliminating the popup dialogs, how does the user stop a background sync? We probably need to have a stop sync button, either on the toolbar or could be a menu item.
5) Is it possible to have a link in the status bar so when the sync finishes, we could put a message in the status bar then link to a log file or something like that? We have no idea if it's difficult to stick buttons/links in the status bar.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
