Oooo! AppKiDo will do. Who cares about polish. As long as it finds
data fast is the goal.
Thank you all. This has helped a ton.
On Thu, May 28, 2009 at 11:24 PM, Kevin LaCoste klaco...@zenvilla.com wrote:
The fact that AppKiDo isn't built in is one of the reasons I like it. When
you update
The fact that AppKiDo isn't built in is one of the reasons I like it. When
you update your docs in Xcode's built-in browser a relaunch of AppKiDo will
cause it to pick up the changes.
Agreed on the loading delay. That's annoying. And it's pretty weak on the
polish side. It does display inherited
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
On 26 May 2009, at 21:48, colo 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
On 26-May-09, at 4:48 PM, colo 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
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
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
I had the same problems with AppKiDo and eventually went back to
Apple's online docs too. They're definitely the most up-to-date
version you're going to find anywhere, and when you've got your own
way of using it, it works really well. I tend to keep the main
framework reference pages
YES! I've been missing that for a long time. Couldn't put my finger on
it until you said it. Bugreporter.apple.com time.
On May 26, 2009, at 6:28 PM, Mark Allan wrote:
FWIW, I initially came from a Java background and something I still
really miss from the JavaDoc style API documentation is
On May 26, 2009, at 4:28 PM, Mark Allan wrote:
FWIW, I initially came from a Java background and something I still
really miss from the JavaDoc style API documentation is the group of
sections entitled Methods inherited from XYZ. Those sections make
it incredibly easy to see at a glance
10 matches
Mail list logo
