Re: unconnected TextFields
Re: unconnected TextFields
- Subject: Re: unconnected TextFields
- From: Scott Anguish <email@hidden>
- Date: Sat, 25 Oct 2003 02:01:55 -0400
On Oct 24, 2003, at 4:16 PM, Cameron Hayne wrote:
I agree. This "set<OutletName>" thing needs much more emphasis in
Apple's
docs and in the various Cocoa books.
The "thing" in this case is Key-value Coding.
The Key-Value Coding conceptual material for Panther is much more
complete than it was. It covers all the new features, and clarifies
many of the old ones. It discusses the naming conventions, and how
they're found.
Anytime that the system needs to 'set' or 'get' a value, KVC is likely
in play.
In the past (pre Panther) KVC really was an advanced feature that you
could make use of if you wanted to. In most cases outside of
WebObjects, it was not very mainstream.
However, with the new Cocoa Controller classes and Key-Value Binding,
you'll find that it is going to become much more prevalent, and
highlighted more.
*** FEEDBACK ***
If you see places in the Apple docs that KVC needs to be mentioned,
and it hasn't been, please either file a bug (be specific about the
doc, and make it clear that it is a Documentation (Developer) issue.
And feel free to send me the bug number.
Tech Pubs is committed to making the Cocoa documentation as helpful to
_you_ as possible.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.