Looking in /System/Library/Frameworks/ I see your point. Now I want a roadmap just so I don't take a wrong turn and end up in the DiskArbitration framework.
To me, this is like somebody walking up and asking what all the options are for careers. I wouldn't even know where to start.
Well, there is a giant book of careers put out by some branch of the US government, or at least there was when I was in high school. And I did peruse it out of curiosity. It's certainly not out the realm of possibility that I'm unique in my fondness for poking around in well structured data.
I'm not sure Apple and Sun really have the same sort of needs to address.
True enough. Since I wrote my initial post I've realized that what I liked about the Java documentation so much was that, being generated by JavaDoc, it shared its structure with the classes it was documenting. Lacking the notion of packages this doesn't translate over to Cocoa so well.
That said I still feel that beginners could benefit from some facile treatment of a broad range of subjects. Not necessarily explaining anything in depth, just pointing to the most appropriate documentation on the subject. How best to go about that, however, escapes me right now.
by Nick Rundquist — Jan 23
Looking in
/System/Library/Frameworks/I see your point. Now I want a roadmap just so I don't take a wrong turn and end up in the DiskArbitration framework.To me, this is like somebody walking up and asking what all the options are for careers. I wouldn't even know where to start.
Well, there is a giant book of careers put out by some branch of the US government, or at least there was when I was in high school. And I did peruse it out of curiosity. It's certainly not out the realm of possibility that I'm unique in my fondness for poking around in well structured data.
I'm not sure Apple and Sun really have the same sort of needs to address.
True enough. Since I wrote my initial post I've realized that what I liked about the Java documentation so much was that, being generated by JavaDoc, it shared its structure with the classes it was documenting. Lacking the notion of packages this doesn't translate over to Cocoa so well.
That said I still feel that beginners could benefit from some facile treatment of a broad range of subjects. Not necessarily explaining anything in depth, just pointing to the most appropriate documentation on the subject. How best to go about that, however, escapes me right now.