Re: Problems subclassing NSTableView and NSOutlineView
Re: Problems subclassing NSTableView and NSOutlineView
- Subject: Re: Problems subclassing NSTableView and NSOutlineView
- From: Todd Blanchard <email@hidden>
- Date: Thu, 7 Jul 2005 00:26:52 -0700
On Jul 6, 2005, at 11:21 PM, mmalcolm crawford wrote:
Per the documentation,
"The other methods—the class method exposeBinding: and the instance
methods exposedBindings and valueClassForBinding:—are useful only
in an Interface Builder palette."
Yes, but the docs imply that exposedBindings need not be written, but
exposeBinding: must be called, valueClassForBinding: is apparently
optional.
Overall, not very clearly spelled out. I see that the docs are
trying very hard to be complete and nooB friendly. They do this at
the expense of essential information and the great annoyance of the
experienced but busy. I would very much like to see something that
explains the interaction pattern, exactly who calls what, what is
already written, and what I have to write, a brief but complete
example, and that's it.
Its also clear that the lack of a public version of NSBinder is a
giant gaping hole in the framework. As soon as I saw the example
code I said "ICK! - That needs to be a class!" OK, so controllers in
general were an even bigger hole, but we are tantalizingly close to
being able to build non-trivial apps without code if only the widgets
were just a smidge more capable. It is quite frustrating.
Todd Blanchard _______________________________________________
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