Re: Using bindings in AU Cocoa GUI?
Re: Using bindings in AU Cocoa GUI?
- Subject: Re: Using bindings in AU Cocoa GUI?
- From: Kyle Sluder <email@hidden>
- Date: Wed, 22 Feb 2012 22:20:43 -0800
On Wed, Feb 22, 2012 at 8:36 AM, Per Bull Holmen <email@hidden> wrote:
> Hi
>
> Cocoa developers who make complex GUIs are very spoilt with the use of
> bindings. They can make it a breeze to program complex interactions
> between the different controls and the model objects. I was wondering,
> is there something technical prohibiting you from using bindings in a
> Cocoa AU GUI? Things like performance/stability? I know that you'd
> have to still maintain the separation of address space etc., the
> normal requirements for an AU GUI. You'd have to make Objective-C
> classes (pretending to be models) to act as go-betweens between the
> controller objects and the standard parameter/property interface...
> I'm not asking if you think it's a wise design choice from a
> programmer point of view, only of it's recommended against for
> technical reasons.
Why would you need "go-between" objects? That's what the controller
layer is for. You could bind all your fields to a controller object
that communicates with your AU instance via properties.
I'd advise against binding to the standard NSController subclasses
chiefly because the AU problem doesn't map well to this pattern. But I
can see no reason why binding to a controller object of your own
creation would be problematic or inadvisable.
--Kyle Sluder
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden