On Dec 4, 2004, at 12:51 PM, Lemont Washington wrote:
It seems as if most examples of bindings use Cocoa controls. Is
bindings performant? How suitable is it to use it at a lower level
than the Cocoa AppKit controls? For instance, lets say you had a
custom view that drew different objects, lets say you were writing a
modeling tool like Visio or had Molecular model data on the screen, If
you made the objects that you drew on the screen Bindings compliant
would that affect performance? Is this feasible?
By "Bindings compliant" I presume you mean simply that the model
objects are KVC and KVO compliant? This is a requirement if they are
to integrate with any bindings-enabled controller/view, whether part of
Cocoa or a custom object. KVC/KVO compliance typically requires no
effort over and above what you should be investing to make an object a
good Cocoa citizen anyway...
it would be great to bind some Cocoa controls such as sliders and the
like to custom objects without writing any glue code.
This makes me wonder if I have understood correctly. It's not clear
how what you're asking for here (binding an NSControl to a custom
object) differs from many of the examples?
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
