• 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: Core Data using only one object
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data using only one object


  • Subject: Re: Core Data using only one object
  • From: Chris Hanson <email@hidden>
  • Date: Tue, 24 Apr 2007 19:52:10 -0700

On Apr 24, 2007, at 6:26 PM, Corey O'Connor wrote:

On 4/24/07, Roland Torres <email@hidden> wrote:
On Apr 24, 2007, at 5:43 PM, John Stiles wrote:

> Honestly, I see where you're coming from, but I also see the OP's
> point that it really isn't stated anywhere. The Core Data docs
> speak in some high-falutin' language sometimes, and this can
> definitely cloud over the actual meaning.

That's pretty much right on. The documentation can seem like its
written for people who already know the subject or at least know what
they need to do with it, not for those who are coming to it for the
first time.

I'll voice my agreement too. The Core Data documentation isn't that
great for this info. The only way I got anywhere was making several
toy projects that used Core Data in various ways. Maybe some tutorials
of the same?

John, Roland, Corey, Steve, others - can you please provide examples of where you feel the Core Data documentation is talking over the heads of developers, especially in the "Core Data Programming Guide" and "Core Data Basics" books?


I'm not asking this to be disagreeable -- it's a genuine, honest question. This seems to be a common issue given the questions on this list, on comp.sys.mac.programmer.help, on Panic's CocoaDev wiki, on #macdev, and elsewhere. I'd really like to know what it is that makes a lot of the available information about Core Data difficult to get one's head around.

Getting to the bottom of it will help everyone -- Apple, the developer community at large, and those of us who try to specifically help developers with the technology. I know I'd like to explain it in the most effective way possible whenever I do... :)

  -- Chris

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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


  • Follow-Ups:
    • Re: Core Data using only one object
      • From: Steve Weller <email@hidden>
    • Re: Core Data using only one object
      • From: mmalc crawford <email@hidden>
References: 
 >Re: Core Data using only one object (From: Matt Neuburg <email@hidden>)
 >Re: Core Data using only one object (From: Steve Israelson <email@hidden>)
 >Re: Core Data using only one object (From: mmalc crawford <email@hidden>)
 >Re: Core Data using only one object (From: Steve Israelson <email@hidden>)
 >Re: Core Data using only one object (From: mmalc crawford <email@hidden>)
 >Re: Core Data using only one object (From: John Stiles <email@hidden>)
 >Re: Core Data using only one object (From: Roland Torres <email@hidden>)
 >Re: Core Data using only one object (From: "Corey O'Connor" <email@hidden>)

  • Prev by Date: Re: Quartz flash screen updates
  • Next by Date: Re: Core Data using only one object
  • Previous by thread: Re: Core Data using only one object
  • Next by thread: Re: Core Data using only one object
  • Index(es):
    • Date
    • Thread