Is the traditional update-render-loop overkill method for cocos2d / cocos2dx?

So let's say I'm making a board game. I have an array of game boards, my logic should check the location and detection of conflicts, that's all right.

Traditionally using something like directX, you will have a game loop, test some logic, update the array of game boards and finally draw a screen, but with cocos2dx we don’t draw a screen directly, we add a sprite to the layers, and coconut does the rest!

For instance..

  • Initialize the game array that represents the playing field.
  • Initialize game object
  • add objects to array
  • refresh screen (display array on screen)
  • start the game cycle
  • Test for some logical state
  • remove object from array
  • ,

, , cocos2d/cocos2dx, , .

, , - .

, .

- , ?

+3
2

. , , - , . , , .

+1

. .

, , () ( , , , ).

" ", , .

+3

All Articles