• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: When to use Core Data?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: When to use Core Data?


  • Subject: Re: When to use Core Data?
  • From: "Jason T. Slack-Moehrle" <email@hidden>
  • Date: Fri, 18 Jun 2010 14:50:15 -0700 (PDT)
  • Date-warning: Date header was inserted by spool002.mac.com

Jens,


> I have an app where I have 30 small base image files (like 2k each) that could be displayed to a user.
> ...
> What is the best way to store a sequence of images? I dont know when is best to use Core Data.

Core Data sounds like major overkill for this, especially if the images are hardcoded.
All you really need to store is an array of ~30 integers (picture indexes) for each sequence. The sequences themselves might be stored in an array, or in an array of dictionaries if you want to store data about each one, like a name or mod date. This kind of data is really easy to store in memory using NSArray/NSDictionary, and persistently as a property list.

Thanks for keeping me in check, Jens. That would be a much easier and less intensive solution.

Best,
-Jason
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: When to use Core Data? (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: When to use Core Data?
  • Next by Date: Re: Xcode 3.2.3: cannot pair a synthesized setter/getter with a user defined setter/getter
  • Previous by thread: Re: When to use Core Data?
  • Next by thread: Help linking libraries into an xcode project
  • Index(es):
    • Date
    • Thread