Re: code data export import strategies
Re: code data export import strategies
- Subject: Re: code data export import strategies
- From: Kyle Sluder <email@hidden>
- Date: Sun, 8 Nov 2009 12:27:22 -0800
On Sun, Nov 8, 2009 at 12:21 PM, Jerry Krinock <email@hidden> wrote:
> Looks like a document to me. Why not make this a document-based
> application? NSPersistentDocument. This has been done before :)
It sounds to me more like Martin wants to export a fragment of his
document, much like someone might send a meeting invitation within
iCal.
NSCoding is usually not what you want here. It is very fragile; you
would need a lot of logic to ensure you didn't start unserializing
older or newer versions of objects than you can handle. NSCoding is
really intended for cases in which the objects themselves are the
important information.
In your situation, Martin, the user's data is the important piece; the
fact that it is stored in an NSManagedObject is irrelevant. You
should use some interchange format to send the data between the
instances of your application. This might be a property list, XML, an
iCalendar-esque format, or even just a custom plain-text format.
--Kyle Sluder
_______________________________________________
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