Syncing behaviour for core-data app
Syncing behaviour for core-data app
- Subject: Syncing behaviour for core-data app
- From: Martin Hewitson <email@hidden>
- Date: Tue, 24 Aug 2010 16:17:51 +0200
Dear list,
I have a core-data app which can sync the data to mobile-me. I have a design question that perhaps others have already pondered. When is a good time to sync from the user's perspective? If I just do it automatically in the background I'm worried that the data will change via the sync while the user is working on the self-same data. Is there a recommended behaviour that stops the user getting a nasty surprise? For example, I would think it is bad form to update the data in a text field while the user is typing in there. I considered popping up a progress window but then I realised that would be a bad user experience as well. My app has the feature that it can be 'locked' which means the user doesn't input any more. Perhaps I should only sync during that state. I wonder how iCal et al handle this.
I realise that in principle (since core-data over mobile-me is inherently a single user experience), this is unlikely to ever happen, but one can imagine the user starts the app and quickly goes to edit some data just as some previous edits (entered on another computer) get pulled down.
Any thoughts gratefully received,
Martin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Martin Hewitson
Albert-Einstein-Institut
Max-Planck-Institut fuer
Gravitationsphysik und Universitaet Hannover
Callinstr. 38, 30167 Hannover, Germany
Tel: +49-511-762-17121, Fax: +49-511-762-5861
E-Mail: email@hidden
WWW: http://www.aei.mpg.de/~hewitson
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden