On Jun 3, 2013, at 1:22 PM, Alex Zavatone < email@hidden> wrote: But, if the standard is to create an AppDelegate.h that does so,when creating an iOS app project in Xcode, shouldn't that be up in the UIApplication Class Reference? An explanation with a stipulation stating: "I conform to the UIApplicationDelegate by extending the UIResponder in the auto generated AppDelegate.h"? Or at least something more elegantly worded?
I … don’t understand what you’re getting at. AppDelegate isn’t a system class, It’s just some class in your app that acts as the delegate of the UIApplication. You don’t have to have such a class at all, AFAIK, although it would probably limit what your app could do. Xcode’s templates happen to create such a class for you, because it’s convenient, but that class isn’t in any way fixed so there’s no reason to document it in the class reference.
It’s true that if your app has a class Foo that acts as the app delegate, then that class has to implement the UIApplicationDelegate protocol. But that’s already made explicit in the fact that UIApplication’s `delegate` property has type id<UIApplicationDelegate>. In fact those two statements say the same thing.
I think you might have some confusion about what a protocol is in Obj-C, which might be making it hard to frame your question in terms that make sense to the rest of us.
—Jens |