On Jun 3, 2013, at 6:33 PM, Jens Alfke wrote: On Jun 3, 2013, at 3:19 PM, Alex Zavatone < email@hidden> wrote: Ahh, it's just that the app startup process is more complicated than is easily explained and I'm about to tell the staff, "just ignore the details for now, you put this here and it works”.
“The UIKit UIApplication object has a delegate, which is a custom object that it’ll tell things to and ask things about. Our AppDelegate class has a single instance, and it registers itself as that object. So if you look up the methods in the UIApplicationDelegate protocol in the UIKit docs, you can implement any of those in the AppDelegate class and it’ll get called by the UIApplication as described in the docs. That’s how you can get notified of stuff like the app going to sleep.”
Yeah, that's clear. It's just that I was assuming that I could easily hop through the class references and put together a little paragraph to explain it just like that. I guess I just approached the class references the wrong way.
In reviewing certain class refs last week, I remember running into cases where it a protocol was conformed to by a class, sometimes the top of the class ref would note that it is conformed to through another class. It was confusing that I didn't see the same when attempting to through the docs. Using Dash now, searching for "appDelegate" brings me straight to the UIApplicationDelegate Protocol Reference and things are more clearly exposed.
Sometimes going through the docs ala the organizer is a little less than optimal. Also, couldn’t you find a good book on UIKit development and give that to the new people, instead of having to explain everything yourself?
There are many good ones out there, that I agree on.
In any case, thanks much. Almost back to Couchbase.
|