Re: OS + iOS best practice
Re: OS + iOS best practice
- Subject: Re: OS + iOS best practice
- From: Amy Gibbs <email@hidden>
- Date: Tue, 07 Jun 2011 06:51:57 +0100
After the announcements about iCloud, should I just wait a while and
I'll be able to build this in 'for free' (there will be a cocoa way to
do this)?
On 3 Jun 2011, at 9:29PM, Evadne Wu wrote:
As for the SQLite file, I am never sure if Core Data’s OS X
implementation and iOS implementation share the same format and will
continue to be so, and it is surely a very strong and valid idea to
just use an intermediate format you control, I’ve been bouncing them
across OS X & iOS with no problem…
Note that Dropbox exposes directory hashes, so that might help with
images. I’m not sure if referenced images would be updated at all —
this can be a big problem if they can be updated outside the app and
you need to handle that.
For the record, going with Dropbox might not be very safe, could be
not scalable at all, and might have security implications as Jeffrey
pointed out. But it might work very well for your scenario. If
you’re serious about making it robust, I still recommend that you
create a tiny and dedicated web service for this app…
-ev
On Jun 4, 2011, at 04:23, Amy Gibbs wrote:
Thanks
Sounds like dropbox would be a good fit, I'll download the ask and
give it a go.
My current mac app stores the data in a sqllite file that I'm
hoping to just sync with dropbox. However it does currently also
store images in a directory and just store the paths as string
attributes. Not sure of the best solution for those. I'm not
expecting to always have web access on the iPad when the app is
running.
The images would not change too often once the app is initialised
with data. A dozen or so new ones a month, and from the iPad they
would only need to be read.
Perhaps I could store the SQLite file and the images in a directory
that can be stored in the dropbox directory?
Many thanks for all your help.
Sent from my iPad
On 3 Jun 2011, at 19:48, Evadne Wu <email@hidden> wrote:
Dropbox sync is good for a pile of files, but no more than that.
Let’s rebound the requirements:
* there’s a single user Core Data app
* want an iPad version of the app
* the two versions will sync up
Given the requirements, and add the fact that I’m pretty sure that
Dropbox would keep conflicted copies of any file around, so there
is no fear for lost data, and you can probably merge anything…
it’s probably a good fit. If you don’t pull in any external
resources, for example pictures on the filesystem which are only
referenced by path strings in Core Data entities, the only thing
that needs syncing would be the .sqlite file and things can
probably work. If this is not the case then a simple Web service
would go a long way.
Dropbox carries its own stateless JSON based API, but there is a
SDK out there (for prototyping purposes) too.
-ev
On Jun 4, 2011, at 02:16, Amy Heavey wrote:
Thanks, It's an app for just me really. I just prefer to work on
a desktop mac when I'm in the house, and I can't carry my iMac
with me :) I do find typing much easier on an actual keyboard.
Maybe I should just get a keyboard for the iPad?
Many Thanks
Amy
On 3 Jun 2011, at 7:11PM, John Joyce wrote:
On Jun 3, 2011, at 1:04 PM, Amy Heavey wrote:
I hope this appropriate for this list, if not please accept my
apologies.
I've got a fairly basic core data app that I've written for
personal use on my iMac. I'd like to have an iPad version as it
would be very useful to have whilst I was mobile. (It's
basically a customer/product database).
Is there a best way to manage sharing the data between an OS
and iOS version? I assume it will be possible as long as they
use the same datamodel.
I was thinking maybe some kind of dropbox sync would be best as
it wouldn't depend on a network connection, and I wouldn't need
to use both the mac an iPad versions at the same time. I have
absolutely no idea how to do this though. I know some apps have
built in dropbox sync but I fear it may be beyond me as I
haven't found a handy tutorial anywhere.
Can anyone point me in the right direction at all?
Many Thanks
Amy
If it's an app for multiple users to have the same data, you
probably want to have a central database that client apps
retrieve data from.
Core data isn't really a multi-cient database.
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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