Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Core Data document-based app design decision?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data document-based app design decision?

Subject: Re: Core Data document-based app design decision?
From: Uli Kusterer <email@hidden>
Date: Fri, 25 Aug 2006 15:46:27 +0200

Am 25.08.2006 um 11:00 schrieb Jörgen Isaksson:

Is this the correct way to design a Core Data document based application that needs to save some application related data?

Depends on what the data is. It may be a bit heavyweight if you're just saving some preferences (i.e. not lots of data but just ten or so separate small bits). In that case NSUserDefaults and the NSUserDefaultsController may be a better (non-CoreData) way to save your application-specific data.

But otherwise I don't see much wrong with this approach. Then again, I'm not exactly comfortable with CoreData yet, so if someone else contradicts my assertion, better believe them.

Cheers,
-- M. Uli Kusterer
http://www.zathras.de


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: Core Data document-based app design decision?
From: Niels Meersschaert <email@hidden>


References:  
  >Core Data document-based app design decision? (From: Jörgen Isaksson <email@hidden>)




Prev by Date:
Re: dataFromFile

Next by Date:
import Header??

Previous by thread:
Core Data document-based app design decision?

Next by thread:
Re: Core Data document-based app design decision?

Index(es):

Date
Thread