3

I have an existing game app written in Cocoa with UIKit views and I want to convert the game view itself to Kobold2D, leaving the start screen and other screens as standard Cocoa/UIKit screens. So I want to embed Kobold2D into the app and activate it just for the game screen.

I've read chapter 15 of Steffan Itterheim's book which says how to do this for Cocos2d. What's the process for Kobold2D?

Paul Masri-Stone
  • 2,843
  • 3
  • 29
  • 51

1 Answers1

3

I personally haven't tried or even attempted embedding Kobold2D in a UIKit app. It just wasn't one of my goals. Right now I can't think of a way that would be straightforward. In any case it'll be easier to move the existing source code and resources into a Kobold2D project, rather than attempting to attach the Kobold2D-Libraries project to an existing project.

Kobold2D runs quite a bit of setup code in main() and app delegate (KKAppDelegate). By the time the app delegate finishes, cocos2d is already set up and running.

You could try stopping the director for the time being, attaching your UIKit views to the already existing window, and later attach the cocos2d view to your game view controller when it needs to be displayed (and also resume the director). Something along that line could work, as long as the cocos2d view is never released.

I would also generally recommend not to re-create the cocos2d view anyway, since it's a costly operation and seems to be very untested. Issues related to re-creating the cocos2d view multiple times are common.

CodeSmile
  • 64,284
  • 20
  • 132
  • 217
  • Thanks for the quick response, Steffan. If I take your suggestion and embed the existing source into a Kobold2D app instead, presumably the sharedDirector will be running from the start. Can I just pause and unpause it as for Cocos2d, i.e. by sending it stopAnimation and startAnimation? – Paul Masri-Stone Sep 19 '12 at 10:00