Listen, for me at least, it just isn't productive to
jump into a large framework and attempt to implement
fairly complex behaviors using features of the
framework that I don't understand.
There are lots of different learning styles. In my
case, I like to learn from the bottom up. I am
bothered when I don't know how something works at
least conceptually. If there is a learning style that
prefers jumping in, using "magical" behaviors, and
being surprised every day, I don't understand it.
For me, using bindings and controllers without first
understanding the much more basic accessors and data
source concepts would be fruitless.
> As far as I can tell, there is not one word about
this in the
> documentation for NSArray, NSMutableArray, or
NSArrayController. > There should be.
Why should accessors and Key Value Observing be
documented in NSArray, NSMutableArray, or
NSArrayController ? Nearly every class provides
accessors. Why are NSArray, NSMutableArray, or
NSArrayController special ? Is it because those are
the classes you happen to use in your application ?
Should the concepts of instance variables be explained
in every reference document ? Should Objective-C
message dispatch be explained again in every class
reference?
KVC Compliance
"The key-value coding mechanism tries hard to find a
value for a given key, so that it is actually
difficult not to be KVC compliant for a given
property. Although there are a number of ways to
ensure compliance, it is recommended that you use
accessor methods and follow standard naming
conventions. The general requirements for KVC
compliance are described in Key-Value Coding Accessor
Methods in Key-Value Coding Programming Guide."
http://developer.apple.com/documentation/Cocoa/Conceptual/ModelObjects/Articles/moIntegrating.htmlhttp://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueCoding/Concepts/AccessorConventions.htmlhttp://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueCoding/index.htmlhttp://developer.apple.com/documentation/Cocoa/Conceptual/ModelObjects/Articles/moAccessorMethods.html
I don't mean to be harsh, and I know that learning a
large framework can be overwhelming. Everyone has to
start somewhere. However, basic concepts are already
covered in many places, and covering them redundantly
in every page of class documentation would ruin the
documentation for many users.
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
