Getting the info from the Apple documentation -- Re: New Cocoa w/ CoreData book
Getting the info from the Apple documentation -- Re: New Cocoa w/ CoreData book
- Subject: Getting the info from the Apple documentation -- Re: New Cocoa w/ CoreData book
- From: Scott Anguish <email@hidden>
- Date: Thu, 20 Apr 2006 00:45:07 -0400
I'm going to reply to this (moderator's privilege), but it is
relevant to more than just this message.
On Apr 20, 2006, at 12:04 AM, PJ Pritchard wrote:
Hey Scott Anguish, et al ....
If you are out there ... and aren't already writing a book on
Advanced CoreData concepts w/ 10.4 technologies ...
Actually, the Core Data documentation is excellent. And it is much
more up-to-date and responsive to user issues than a printed book
could possibly be.
This is actually the case with most all of the Cocoa documentation
from Apple (but I am biased). Bugs are fixed constantly, items are
clarified, etc.. New versions are pushed to the web (and your local
machine if you opt) every 5-6 weeks.
4) ... would sharply decrease number of hits to this mailing list ...
While this is hard to say (without perhaps angering some folks), one
of the biggest issues with the list traffic is that developers are
not extracting the existing information in the doc. Many questions
are answered in the doc, and often the answer posted here is simply a
URL to the doc.
But why are they asking here? is it because...
- they are not able to find the relevant answers in the doc? (just a
search issue, or a categorization issue)
- they aren't able to understand what is in the doc? (writer's failure)
- the answer isn't in the doc?
- they are not looking in the doc at all?
Issues 1,2, and 3 are best handedly by filing a bug report or
enhancement request at bugreporter.apple.com. 2 and 3 can also be
handled using the Feedback mechanism on _every_ page of the
documentation. Bugs don't necessarily get fixed as fast as users want
(or as those of us who fix them want either), but they do get
attention based on their severity and impact.
Issue 4... that's harder to deal with. But it is a significant
problem.
BTW, tell Apple to open up the NSNib API a little more ... dynamic
nib creation is only a step away ...
bugreporter.apple.com
_______________________________________________
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