• 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: Struct, Object, or Dictionary?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Struct, Object, or Dictionary?


  • Subject: Re: Struct, Object, or Dictionary?
  • From: mmalc Crawford <email@hidden>
  • Date: Wed, 2 Jul 2008 17:33:26 -0700


On Jul 1, 2008, at 11:45 AM, lbland wrote:

If you have to bind your entities to anything then you might try a Core Data representation.

No, don't do this.
As the documentation takes pains to point out, Core Data is not an entry-level technology. If you're still trying to get your head round memory management and what accessor methods to write, then Core Data is not yet for you.
In addition, there is no need to use Core Data simply to leverage Cocoa Bindings -- again the documentation points out that they are orthogonal (even if in many respects complementary) technologies.


mmalc

_______________________________________________

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


References: 
 >Struct, Object, or Dictionary? (From: "Bridger Maxwell" <email@hidden>)
 >Re: Struct, Object, or Dictionary? (From: lbland <email@hidden>)

  • Prev by Date: Re: Why aren't my bindings firing?
  • Next by Date: Re: saving state of non-document-based agent
  • Previous by thread: Re: Struct, Object, or Dictionary?
  • Next by thread: [Q] Regression of setSize for NSImage?
  • Index(es):
    • Date
    • Thread