Re: NSObjectController, content outlet and content object question
Re: NSObjectController, content outlet and content object question
- Subject: Re: NSObjectController, content outlet and content object question
- From: Michael de Haan <email@hidden>
- Date: Wed, 1 Jul 2009 09:53:12 -0700
On Jul 1, 2009, at 8:45 AM, Keary Suska wrote:
It might well be possible that I am thinking about the bindings
incorrectly...and in fact all one needs in this case is to bind the
view( textfield and slider) to the controller with the correct
keypath, and that the relationship of a controller to it's content
is the issue I am not completely understanding.
Binding only involves two endpoints (objects). That there are
additional inter-object connections involved in a design is a design
issue and not inherent to bindings in any way. So it is irrelevant
to the view-controller bindings how the controller gets its content,
and there are multiple ways this can be done.
Thanks Keary...yes...I think this is the part I was not completely
seeing.
It appears that you are assuming that bindings involves three
objects ion an MVC pattern. MVC is a design pattern, bindings are
only one way to "connect" objects, such as M-C or V-C, but are not
themselves an implementation of MVC.
Sorry if it came across that way...but you do point out what I was
missing ie the relationship of the controller to it's content
( model). I will think of the content as an ivar/outlet of the
controller, and thus, as you say, the way this is connected to the
model is not the issue in the actual binding.
Thanks for your time.
_______________________________________________
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