Re: whether to use core data...
Re: whether to use core data...
- Subject: Re: whether to use core data...
- From: Izidor Jerebic <email@hidden>
- Date: Sat, 3 Oct 2009 18:12:14 +0200
On 3.10.2009, at 17:14, Colin Howarth wrote:
Now that's a shame, because save: load: sounds like a persistent
document to me. But if even Apple's documentation says WARNING, Do
NOT attempt to read the Programming GUIDE in order to understand
Core Data -- well, I believe 'em!
On the other hand, somewhere else it says that if I'm starting a new
project (I am) or it does the sort of thing mine does (it does) I
should definitely consider using Core Data. It even says "you should
Definitely Consider it! OK? Got it? Good." which is sort of a threat.
Extremely simplified way of describing CoreData is "easy to use
database". So if you have something like a personal library
application with list of books, CDs, DVDs etc. that can go into 1000s
of items and application has GUI for searching, this would be natural
choice for CoreData.
But not all persistent data is good choice for CoreData. If your
application has few small objects (e.g. less than 100, each smaller
than 10KB), and is using all of them (no searching), then simply
persisting them with NSCoding protocol to a document file is probably
good solution.
You can look at Sketch source code in Developer/Examples folder - this
is a full drawing program with undo that saves its data in a document
file using NSCoding protocol and not CoreData.
izidor
_______________________________________________
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