• 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
Using bindings in AU Cocoa GUI?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Using bindings in AU Cocoa GUI?


  • Subject: Using bindings in AU Cocoa GUI?
  • From: Per Bull Holmen <email@hidden>
  • Date: Wed, 22 Feb 2012 17:36:05 +0100

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.

Per
 _______________________________________________
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


  • Follow-Ups:
    • Re: Using bindings in AU Cocoa GUI?
      • From: Paul Davis <email@hidden>
    • Re: Using bindings in AU Cocoa GUI?
      • From: Kyle Sluder <email@hidden>
  • Prev by Date: IO Cycle Telemetry and Xcode 4.3
  • Next by Date: problem on loading the instrument unit plugin
  • Previous by thread: IO Cycle Telemetry and Xcode 4.3
  • Next by thread: Re: Using bindings in AU Cocoa GUI?
  • Index(es):
    • Date
    • Thread