• 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: Why use NSObjectController?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why use NSObjectController?


  • Subject: Re: Why use NSObjectController?
  • From: Seth Willits <email@hidden>
  • Date: Sun, 10 Aug 2008 21:45:42 -0700

On Aug 10, 2008, at 9:39 PM, Gordon Apple wrote:

I don't use CoreData. Frankly, the main use I have made of
NSObjectController is to decrease my typing in IB bindings. For example, my
inspectors have a large number of controls that are bound through a fairly
long chain of references to their controllers. By using an
NSObjectController to handle the long chain, my individual bindings are much
shorter. Your mileage may vary.

So far that's the only use I've found for it. :)

It seems like it's really there just as somewhat of an abstract base class for the other controllers, but then I wonder why the CurrencyConverter example uses it, because it works perfectly fine by simply binding directly to the Converter object itself.


-- Seth Willits




_______________________________________________

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


References: 
 >Re: Why use NSObjectController? (From: Gordon Apple <email@hidden>)

  • Prev by Date: Re: Why use NSObjectController?
  • Next by Date: Re: Why use NSObjectController?
  • Previous by thread: Re: Why use NSObjectController?
  • Next by thread: NSPopupButton, Null Placeholder, image
  • Index(es):
    • Date
    • Thread