FROM : Scott Anguish
DATE : Thu Jul 20 22:14:51 2006
On Jul 20, 2006, at 3:25 PM, George Orthwein wrote:
> I don't think implementing "one way" or "read only" bindings is a
> misuse, though it almost seems that way since there aren't any
> examples or mentions of it in the docs that I remember seeing. I
> think I'll file a doc request.
binding between model objects isn't recommended at all. the bindings
doc is clear about how we recommend doing it (controller to model,
view to controller.. it would be useful to extend that to the
occasional view to model as well though, I'll add it to the list).
We don't say how we don't recommend doing it in general though..
> It does seem to be a sly way of avoiding the observeValueForKeyPath
> bottleneck though.
DATE : Thu Jul 20 22:14:51 2006
On Jul 20, 2006, at 3:25 PM, George Orthwein wrote:
> I don't think implementing "one way" or "read only" bindings is a
> misuse, though it almost seems that way since there aren't any
> examples or mentions of it in the docs that I remember seeing. I
> think I'll file a doc request.
binding between model objects isn't recommended at all. the bindings
doc is clear about how we recommend doing it (controller to model,
view to controller.. it would be useful to extend that to the
occasional view to model as well though, I'll add it to the list).
We don't say how we don't recommend doing it in general though..
> It does seem to be a sly way of avoiding the observeValueForKeyPath
> bottleneck though.






Cocoa mail archive

