• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect


  • Subject: Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
  • From: Mark Allan <email@hidden>
  • Date: Wed, 27 May 2009 00:28:11 +0100

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 open and then middle-click the classname I'm interested in so that it opens in a new tab and I can quickly jump back and forth between the class listing and others I might be interested in...but that's just me.

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 what methods/messages your class supports without having to load the docs for each of the superclasses in turn until you find (or don't as the case may be!) what you're looking for.

Mark


On 26 May 2009, at 10: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 <email@hidden> 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 (email@hidden)

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:
This email sent to email@hidden
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden



_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
      • From: mmalc Crawford <email@hidden>
    • Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
      • From: Alex Kac <email@hidden>
References: 
 >Recommendations to Reading the Xcode in built Documentation to the fullest effect (From: colo <email@hidden>)
 >Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect (From: Nathan <email@hidden>)

  • Prev by Date: Re: NULL Outlets in one file work in another
  • Next by Date: Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
  • Previous by thread: Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
  • Next by thread: Re: Recommendations to Reading the Xcode in built Documentation to the fullest effect
  • Index(es):
    • Date
    • Thread