Re: Cocoa bindings one- or bi-directional
Re: Cocoa bindings one- or bi-directional
- Subject: Re: Cocoa bindings one- or bi-directional
- From: Scott Anguish <email@hidden>
- Date: Fri, 27 May 2005 05:17:56 -0400
On May 27, 2005, at 5:14 AM, mmalcolm crawford wrote:
On May 26, 2005, at 7:39 PM, mmalcolm crawford wrote:
If you want it the other way round, you'll need to tell brick2 what to observe, too.
This may actually be more appropriate here. If you set both objects to observe each other, then they can keep themselves synchronised...
After all the other writing I omitted the main point: You typically should not bind one model object to another. The primary goal of bindings is to keep user views synchronised with models. You bind an attribute of a UI widget to the property of a model object...
picking one further nit on this..
Always, always use a controller.
So
You bind an attribute of a UI element to the controller, which is bound to the property of an object model.
-- "William Cheeseman ... is said not to be a doofus in real life." - Roger Ebert, Chicago Sun-Times Online, Jan 8, 1998
|
_______________________________________________
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