• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Binding of invisible controls: is lazy data loading possible?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Binding of invisible controls: is lazy data loading possible?


  • Subject: Re: Binding of invisible controls: is lazy data loading possible?
  • From: Quincey Morris <email@hidden>
  • Date: Wed, 21 Jan 2009 02:30:33 -0800

On Jan 21, 2009, at 01:11, mmalc Crawford wrote:

It's not clear why this is any more satisfactory than the previous...

It's just that the previous one appeared to be talking about what to implement, not what to call. *That* is only an issue because the main text at


http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueCoding/Concepts/AccessorConventions.html#/ /apple_ref/doc/uid/20002174-178830-BAJEDEFB

obscures what ought to be obvious or explicit -- that what you implement *is* what you call (or can be). For example, in that section, talking about getters:

Supporting to-many relationships in this manner requires that your class implement two methods using the naming pattern -countOf<Key> and -objectIn<Key>AtIndex:. [...] Implementing these methods allows your application to invoke valueForKey: using the key for the to- many property.

It appears to be making a clear distinction between what you implement and what you call. "Implement this, invoke that." Or, later, for setters:


The key-value coding methods mutableArrayValueForKey: and mutableArrayValueForKeyPath: provide mutable access to a to-many relationship [...]. In order to support these methods, your class must implement two additional methods for each of these keys: - insertObject:in<Key>AtIndex: and -removeObjectFrom<Key>AtIndex:.
Same distinction. "Implement these, mutable access via those", it appears to say. It speaks the truth, just not enough of it.
"'Ensuring KVO Compliance' at <http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueObserving/Concepts/KVOCompliance.html#//apple_ref/doc/uid/20002178 > should make explicit whether a class that allows automatic observer notifications for a property will automatically emit KVO change notifications for KVC-compliant collection mutators."

So this is not the only place that really needs just a little bit of clarifying wording.


_______________________________________________

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Binding of invisible controls: is lazy data loading possible?
      • From: mmalc Crawford <email@hidden>
References: 
 >Binding of invisible controls: is lazy data loading possible? (From: "Vitaly Ovchinnikov" <email@hidden>)
 >Re: Binding of invisible controls: is lazy data loading possible? (From: Quincey Morris <email@hidden>)
 >Re: Binding of invisible controls: is lazy data loading possible? (From: Ken Thomases <email@hidden>)
 >Re: Binding of invisible controls: is lazy data loading possible? (From: Quincey Morris <email@hidden>)
 >Re: Binding of invisible controls: is lazy data loading possible? (From: Ken Thomases <email@hidden>)
 >Re: Binding of invisible controls: is lazy data loading possible? (From: Quincey Morris <email@hidden>)
 >Re: Binding of invisible controls: is lazy data loading possible? (From: mmalc Crawford <email@hidden>)

  • Prev by Date: Re: Getting iPod icon, was Getting the network Machine Icon
  • Next by Date: Flickering while capturing Live Video...
  • Previous by thread: Re: Binding of invisible controls: is lazy data loading possible?
  • Next by thread: Re: Binding of invisible controls: is lazy data loading possible?
  • Index(es):
    • Date
    • Thread