Re: Core Data using only one object
Re: Core Data using only one object
- Subject: Re: Core Data using only one object
- From: Roland Torres <email@hidden>
- Date: Tue, 24 Apr 2007 18:17:39 -0700
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.
Roland
_______________________________________________
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