Re: Problems subclassing NSTableView and NSOutlineView
Re: Problems subclassing NSTableView and NSOutlineView
- Subject: Re: Problems subclassing NSTableView and NSOutlineView
- From: Raffael Cavallaro <email@hidden>
- Date: Thu, 7 Jul 2005 10:47:38 -0400
On Jul 7, 2005, at Thu, Jul 7, 3:26 52 AM, Todd Blanchard wrote:
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.
I think that this stands as a general issue with the Objective-C docs
in general. One gets a very newbie-friendly, but too high level
overview in the conceptual docs, and exhaustive rundown of every
ivar, class method and instance method in the reference docs, but not
much in the way of a practical picture of how things go together in
practice. One is reduced to jumping back and forth among the class
and instance method docs of a dozen different methods in three or
four different classes, plus the conceptual articles just to get
basic things done.
Todd's suggestion of "a brief but complete example" for each class
showing how it is used in practice with the rest of the frameworks
would be worth its weight in gold for those readers who already know
something about object oriented programming. To put it another way,
the idea that reference documentation would contain no sample code at
all is, to my mind, almost perversely frustrating.
In short, the current reference documentation scheme is too
fragmented and lacking in example code for practical use, and the
conceptual documentation is too elementary to do real work with. What
is needed is a middle ground - call it "practical" or "best
practices" that provides sample code that *systematically* covers the
most common uses of all classes. Linking to these "best practices"
samples from the reference documentation would be even more useful.
my $.02, or course.
Raffael Cavallaro, Ph.D.
email@hidden
_______________________________________________
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