|
|||||||||
|
|||||||||
|
||||
|
So I know the SDK has interface builder and stuff, so to make toolchain development easier why not use the interface builder and the port for the toolchain? So I hear the SDK uses 1.1.x headers and converts to 2.0. What if we replaced the headers with 2.0 toolchain headers and then developed apps with the SDK then just use the codes to compile the app with the toolchain/SDK and move to an iPhone for testing. I'm short on time so I'll talk more tomorow.
Thanks, DJ McG
__________________
Click here to for Free Stuff (iPhones, Macs, iPods) Sign up for RewardzNetwork iPhone or iPod. Very easy and legit! Visit the Eclipse Dev Blog By Clicking Here Click here to visit iPhone Fanatics |
|
|||
|
An xcode project template has been created to do this:
http://hackint0sh.org/forum/showthread.php?t=38389 The problem is that the 1.1.4 UIKit headers in the toolchain don't play nice with the SDK UIKit headers. Also most of UIKit has changed so the 1.1.4 headers don't even work. My approach has been to use the normal SDK template and interface builder (which is extremely powerful once you learn it) and then drop in a 2.0 class dumped header when needed. For example UIPreferences table is good to add because it has so many custom cells types e.g. text box cell which handles the keyboard and resizes the table, already available. |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|
|
|