Any chance of a cross reference of the toolchain classes vs Apple's SDK classes?

Also any chance anybody has ported the examples to Apple SDK for those of us who want to use the new SDK? I know not everything can be ported since they don't exist in the new SDK but there are still a number of useful examples that should work.

Thanks.

If you're planning on publishing via the AppStore, you're right - there are some things that Apple has restricted you from using. We're working on documenting those, but nothing is likely to surface until June, when most NDAs should be going away. Mind you, right now at least, the SDK is relatively volatile and has changed from version to version. So it wouldn't do much good to document the SDK in its present form, as this is likely to change.

If you're not planning on distributing through the AppStore, but rather on your own or through open source distribution methods such as Cydia or Installer, then all of the existing APIs in 1.1 are still present in 2.0; they just need to be added to the SDK. I've put together some How-To's concerning this at http://www.iphone-dev.org (see front page of Wiki). It's very easy to install the private APIs (the one's documented in this book, which are the ones Apple is using) in the SDK so that you can build applications and send it right to a 2.0 device. NES.app now also includes an Xcode project, and builds against the SDK (As an example).

I don't need to distribute my application via the iTunes store, but I do need to directly install it on a few dozen non-jailbroken iPod Touches (via an SDK license). The app is for internal use within within one institution.

If I install the private APIs into the SDK as you described, will I then be able to deploy the code samples from the book onto non-jailbroken iPod Touches using Xcode & the SDK rather than the toolchain?

It's a fantastic book by the way. Even as a general intro to Objective C & Apple-style programming it really shines.

This post has been edited by dmichaelson: Jun 1 2008, 03:01 PM