[Suggestion] Exporting to Cocos2d+JS

0 favourites
  • 6 posts
  • I noticed that Cocos2d (a mobile, native engine) has a Javascript binding:


    I was thinking that maybe, instead of accelerating the mobile games at the low Canvas calls level like AppMobi probably does, Scirra could create a special Cocos2D based runtime that would accelerate at the entity level (sprites, backdrops).

    My guess is that the Cocos2d JS bindings would allow most of the JavaScript in the runtime and the plugins and behaviors to "just work". any Input or sound related javascript would have to be specially handled at the C2 runtime level, but I guess that is also a requirement in DirectCanvas. Any custom plugin or behavior that relies on canvas or webgl calls would also have to be converted, but I think that is a small percentage of the user-created plugins.

    I understand that such an exporter would not have all of the plugins and behaviors of the HTML5 engine, but neither does DirectCanvas and I would think that the Cocos2d exported games would perform faster than the DirectCanvas.

    What do you all think?

  • DirectCanvas and CocoonJS both effectively do this already. There's no reason Cocos2d would be faster. What's to be gained by using Cocos2d?

  • Mainly performance. The link says that the Cocos2d approach could be faster than DirectCanvas, but again they don't show any numbers so they could be just making that up.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • It's an enormous amount of effort to go to for a non-guaranteed speedup (I don't see any benchmarks backing up their claim). To improve performance, the main thing we are looking for is WebGL support, which Cocos2d does not appear to support. So we will hold off writing any new engines unless we can get that.

  • Any possibilities after 3 years with so much improvements on Cocos2d-X JS?

    We needed to have native exporters if we wanted to make C2 a serious engine.

    We've done a lot of cool projects with C2.

    But, the problem with C2 is its performance on mobile, which is no way near to other engines.

  • Ashley's last post still remains true. There's no real indication that even a native exporter would speed up anything.

    That being said, what if a native exporter was made, and it did not speed up your game?

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)