I too tried AppKiDo and eventually went back to XCode's built-in
documentation tool. My only peeve with XCode's doc tool is that
copying and pasting code from the doc pages sometimes introduces non-
ascii characters onto my source files. I use an external editor
(BBEdit), rather than XCode's own, so I can't use XCode's code-
completion feature. That, in fact, is something I wish BBEdit's
integration with XCode would provide as well, but that's a peeve for
another list entirely.
Wagner
On May 26, 2009, at 11:20 PM, Nathan wrote:
I used to have the same issue, and AppKiDo was recommended to me as
well. But it's not built into Xcode like Apple's stuff, and it
doesn't recieve doc changes instantly. Plus, it takes a little while
to load which is always annoying. I went back to Apple's stuff and
found that after awhile it worked fine. Class hierarchy-wise, it's
just a matter of learning it and using common sense. Also, at the
top of each class doc there's a list of superclasses, in order. So I
would stick with Apple for a little longer and see if you can't
learn to work with it.
Good luck, Nate
On May 26, 2009, at 4:48 PM, colo <colo0l...@gmail.com> wrote:
I want to really get Cocoa and iphone methods etc... so I find myself
in the Docs every other minute. But I find that it's kinda wonky to
see where things subclass from or what goes with what as examples. I
know there was some sort of guide to navigating it and learning from
it better.
Do you know of such a resource? Tried google. Still trying. Good
stuff, but nothing concrete yet.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
