Re: Documentation frustrations
Re: Documentation frustrations
- Subject: Re: Documentation frustrations
- From: mmalcolm crawford <email@hidden>
- Date: Mon, 11 Jul 2005 12:09:43 -0700
On Jul 10, 2005, at 7:57 PM, Steve Weller wrote:
I'll turn this around and tell you what I am looking for. Create a
single entity with one attribute. What does this get me that I
cannot get by using a different method? Use examples that do the
same thing in different ways so that the reader understands what
core data is doing for them.
This is what the "Low-Level Core Data Tutorial" <http://
developer.apple.com/documentation/Cocoa/Conceptual/
CoreDataUtilityTutorial/index.html> is aimed at doing, as well as
other parts of the API reference (for example, the descriptions of
the convenience methods in NSEntityDescription, <http://
developer.apple.com/documentation/Cocoa/Reference/CoreData_ObjC/
Classes/NSEntityDescription.html#//apple_ref/doc/uid/TP30001173-
BBCIAAFJ>).
Are these the sorts of thing you mean?
My rationale for jumping into Core Data with both feet is that if I
am to write a new app with no legacy and I have no legacy thinking
in my head I want to use the most powerful tool first and then move
to less powerful tools to fill in the parts that it cannot do. I
think this is the route that many others will follow.
This strategy is unlikely to work, though. Core Data builds on
functionality and techniques elsewhere in Cocoa. The memory
management model, the use of accessor methods, the integration with
Cocoa Bindings and so on it shares in common with the rest of the
framework. Understanding of these fundamentals are a prerequisite to
being able to make use of Core Data. Put another way, you can't use
Core Data in isolation from the rest of Cocoa.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden