• 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: How much does NSObject's bind:toObject:withKeyPath:options: do?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How much does NSObject's bind:toObject:withKeyPath:options: do?


  • Subject: Re: How much does NSObject's bind:toObject:withKeyPath:options: do?
  • From: Mailing list subscriptions <email@hidden>
  • Date: Fri, 22 Sep 2006 17:51:18 +0200

El 22/09/2006, a las 16:49, Matt Neuburg escribió:

There are two aspects to this question - theoretical and practical.

(1) From a theoretical (perhaps I should say "religious") point of view,
this matter has been argued from here to the back of beyond on this list,
and you can easily peruse the archives (at cocoabuilder.com) to study the
entire sordid history.

I always search the list archives before posting and this case is no exception. I searched for "programmatic bindings" and scanned all of the results but none seem to match my question; they mostly deal with using Bindings with standard Cocoa NSViews.


My question really has two parts:

1. How much work does the default NSObject implementation of bind:toObject:withKeyPath:options: do, if anything, or is it always necessary to subclass it?
2. Is it ok to use bindings to bind between models, controllers and other controllers, or is it really only intended for the MVC paradigm in its purest forms?


(2) From a practical point of view, if you want to use bind:... for
something and you want to know how your app will behave, why not try it and
find out?

At the moment my project is not in a buildable state and it will probably be at least a couple of weeks before it is... but even if it weren't, I wouldn't want to embark on this course of action without being sure that it's the "right thing" to do. I *know* I can make this work with either more or less work, but I don't want to do stuff that goes against the intended Cocoa Bindings best practices.


I wrote to the list hoping that someone much more experienced than me could chime in with some wisdom. If you can think of some better search terms than "programmatic bindings" that could help me zero in on the relevant messages in the archives then please let me know. (Although now it occurs to me that perhaps you're talking about the notifictions-versus-bindings thing, but that's really not what I was asking about, as I understand that's more of an issue of personal opinion, or "religious", like you say.)

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: How much does NSObject's bind:toObject:withKeyPath:options: do? (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: strange compiler error
  • Next by Date: Re: Gesture recognition
  • Previous by thread: Re: How much does NSObject's bind:toObject:withKeyPath:options: do?
  • Next by thread: Re: How much does NSObject's bind:toObject:withKeyPath:options: do?
  • Index(es):
    • Date
    • Thread