Not looking for an in-depth explanation (I should be able to find/
understand the docs once I get tipped in the right direction), but
can someone briefly hint to me the reason Apple uses key-value
coding in this example code: http://developer.apple.com/documentation/Cocoa/Conceptual/
NSPersistentDocumentTutorial/03_CustomClass/chapter_4_section_3.html
Because, for brevity, the tutorial didn't show the implementation
of the custom accessors.
For current best practice, see <http://developer.apple.com/
documentation/Cocoa/Conceptual/CoreData/Articles/
cdAccessorMethods.html>.
Feel free to file an enhancement request to ensure this is covered
in an update to 10.5 for that tutorial.
I thank you for your reply, but I think your reply was aimed at a
higher level than I meant to ask it.
Please let me add some information. I am developing in and for 10.4
at this time. I am just using basic Cocoa with Bindings. I am not
using Core Data or Managed Objects (I don't think!).
So my question is, do I have any reason to use valueForKey (like the
example I referred to uses) or am I OK using the simple primitive
accessors?
I am interested in doing things Right™ like being KVC/KVO compliant,
but it's just that I am not sure what would spur me to use -
valueForKey: rather than just [myObject myInstanceVariable]
It seems to answer my question that unless I am using Core Data, I
can stick with the simple accessor methods. Maybe someone could just
verify that if it's true. For example, maybe there are reasons for me
to go ahead and use things like -valueForKey even though today I am
not using Core Data. This is where my ignorance lies.
