Howdy everyone,
I have done searching on Google and these forums and can't seem to find many complete answers to this question. I am a new iphone developer with one simple app awaiting approval using the vanilla sdk. I am now moving to more complex ideas and would like to use cocos2d for many reasons. My main question is this:
Are there best practices to implementing a main game loop with cocos2d or is this unnecessary because of something inherent to cocos2d for iPhone? I have read much about scheduling, but no clear advice if you should only schedule ticks in your classes while handling touch events or just schedule one game loop with the scheduler, calling the classes to update themselves in the main loop. I am most familiar with a main game loop using a game state engine having a lot of experience in the Windows & C++ arena. Perhaps this is just what you're most comfortable with because of the flexibility already there?
Thank every one in advance for any useful insight. If this information is already out there in some form and I missed, a point in the right direction would be appreciated.
