Go grab it here:
You can use the Kobold2D API References even if you’re not using Kobold2D, since the API References of the 3rd party libraries are unmodified. For example this includes the only Box2D API Reference that’s available online, and separate API References for cocos2d (iOS) and cocos2d (Mac).
Additional Release Notes
Obviously Kobold2D 2.0 uses cocos2d-iphone 2.0 (rc2) now.
The Project Upgrader tool works for v1.x projects but please understand that the Cocos2D API has undergone many cosmetic and some radical internal changes from v1.0 to v2.0. The Project Upgrader can’t auto-magically fix your code to interface correctly with the latest cocos2d-iphone version. However, I tried upgrading several simple projects using only basic Cocos2D features and much to my surprise they built and ran fine. So definitely give it a shot.
I also improved the package installer. Several users complained about Kobold2D folders having read/write permission only for system and root/admin users, which causes a numnber of problems. I found a loophole in the installer that caused Kobold2D to be installed to /Kobold2D (root folder of the HD) instead of ~/Kobold2D in the user’s home directory. In that case, the currently logged in user had no write permissions to that folder. Now the installer should only allow installation to ~/Kobold2D. After installation you can then of course move the folder to anywhere else on your system.
Although I found this great PackageMaker Problems & Solutions article, I could not find a solution for the “user has no write permission” issue if I allowed installation to custom folders. PackageMaker is one big §$&%/§! Well actually it’s not that bad, it’s just not very well documented, in particular concerning side effects and behavior on different OS versions and the various modes (flat or non-flat; package or distribution; patch, update or new install).
For those of you who rely on Cocos3D or Chipmunk Spacemanager: Cocos3D is incompatible with cocos2d 2.0 and therefore not included. Chipmunk Spacemanager is not fully compatible with cocos2d 2.0 either – it generally works but it won’t rotate sprites. I still included the Spacemanager, hoping that a fix is forthcoming.
The automatic Ad banner feature is currently disabled. I had no time to re-integrate it with CCDirectorIOS now being the new UIViewController. The KKAdBanner class is still available however but I’m not sure if it needs any updates. Maybe it’s just as simple as adding it as a view to CCDirectorIOS, I haven’t tried that.
Finally, CCDirector doesn’t have the setDeviceOrientation method anymore. Instead use [UIDevice currentDevice].orientation. The enums are the same, just using a different prefix (UI instead of CC). You have to use the Supported Device Orientations toggle buttons in your project’s target Info pane to enable/disable the available orientations. If you select more than one supported orientation your app will autorotate automatically. You can override this behavior by adding the -(BOOL) shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation method to your project’s AppDelegate.m file and returning YES for the (currently) allowed orientations.
|Follow @gaminghorror||Follow @kobold2d|