• 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: "Corey O'Connor" <email@hidden>
  • Date: Tue, 24 Apr 2007 18:26:48 -0700

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. And in all fairness, the
> actual sentence in the docs says nothing about the complexity or
> elaborateness of the graphs. Perhaps Core Data could make my life
> easier when dealing with a graph of three nodes—why not? The docs
> don't make an attempt to discourage this line of thinking. Perhaps
> you are confusing what you know for sure, and what is written down.

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. A whole different approach is required. When you're just
learning a technology, you're not too aware of ground-rule things
like appropriateness, applicability, limitations, complexity, etc.
The documentation assumes, for example, you're learning Core Data
because you know enough to know you need/want to use it, which isn't
always the best of assumptions. Core Data is a cool new technology,
but how do I know if its a good fit for what I'm trying to do?

I guess what's lacking is the ground-level documentation, i.e.,
*conceptual* documentation, to give you a good enough understanding
of the forest that you can kinda figure out what to do with all the
trees.
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?

--
-Corey O'Connor
_______________________________________________

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: Chris Hanson <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>)

  • Prev by Date: Re: Core Data using only one object
  • Next by Date: determining minimum bounds to view all content of a view
  • Previous by thread: Re: Core Data using only one object
  • Next by thread: Re: Core Data using only one object
  • Index(es):
    • Date
    • Thread