CocoonJS 1.4.5 Announcment

blog.ludei.com/cocoonjs-1-4-5

The new version of CocoonJS is ready (changelog below). Please, send us your feedback about this 1.4.5 version, it helps to find bugs and determine next improvements. Enjoy!

Added support for iOS7

Dropped support for iOS 4.3

Core

Updated to iOS7 SDK

Slight performance increase due to migration to C++11

Improvements in Core Javascript communication

Launcher

Updated launcher service UI for both iOS and Android

New CocoonJS and Ludei logos!

Javascript

Moved the ?focus? function to Node instead of having it inside HTMLElement and Canvas

Extensions

Multiplayer and Social

Added support for Google Play Games

I haven't looked deeping into this. But does this mean that CJS now supports Google Play multiplayer service? That would be a huge step for Multiplayer and prsonally I feel could lock CJS position as a HTML5 game wrapper..... Too darn bad they won't make a memory manager.

Thing is.. We still would have to wait for them to actually update the C2 plugin and based on the replies we get from Ludei about C2 on their forums. That seems like it will take a long time.

—

LOL, that's sooo true. I'm not sure who is taking responsibility of the plugin. Though we hear tidbits here and there of who it. It seems in practicality each group claims the other :D

I told Ludei to maintain the C2 CocoonJS plugin themselves. There shouldn't be any ambiguity here. They kept making breaking changes to their API, and when I asked, they couldn't even tell me what they'd changed. It didn't seem reasonable for me to try and maintain it under those circumstances - it was a nightmare for me, whereas they know their own API, presumably - and then they asked me to add more features... so I told them to do it themselves!

Ashley

I wish they would. That makes a lot of sense. They know there api in and out. Then it's too bad they don't spend more effort on it :(

Really looking forward to this working.

I recently sent them my whole project to see if it would help them out. My games ready for release, but at the moment it's only really for Tizen, and sadly I can't test that out.

I could release it on pc, as it works great, but thought touch would be best.

I told Ludei to maintain the C2 CocoonJS plugin themselves. There shouldn't be any ambiguity here. They kept making breaking changes to their API, and when I asked, they couldn't even tell me what they'd changed. It didn't seem reasonable for me to try and maintain it under those circumstances - it was a nightmare for me, whereas they know their own API, presumably - and then they asked me to add more features... so I told them to do it themselves!

Gameclosure.

<img src="smileys/smiley19.gif" border="0" align="middle" />

I feel some comment on navigating Italian plumbing is warranted here, but I shall refrain.

Maybe it will magically fix itself in the near future.

I'll get my coat....

Joannesalfa

I agree it's a viable alternative. But Ashley has a point. GameClosure should step up and provide the exporter and Plugin.

however I think Ashley should just use a custom Chrome browser. This isn't and answer for IOS but for Android. I was doing some research and found that anyone can compile Chrome Beta/Canary/Stable for desktop or Android. So with some tinkering right now someone can just compile a custom Chrome browser to run C2 games.

I think that's the route Ashley shuold go since wrappers always seem to have these hurdles.

i wonder if the 1.4.5 launcher updated on ios app store few days ago is this new one? or more waits for this?

I told Ludei to maintain the C2 CocoonJS plugin themselves. There shouldn't be any ambiguity here. They kept making breaking changes to their API, and when I asked, they couldn't even tell me what they'd changed. It didn't seem reasonable for me to try and maintain it under those circumstances - it was a nightmare for me, whereas they know their own API, presumably - and then they asked me to add more features... so I told them to do it themselves!

Forgive me for being so direct but, why dont Scirra make its own exporter?

> I told Ludei to maintain the C2 CocoonJS plugin themselves. There shouldn't be any ambiguity here. They kept making breaking changes to their API, and when I asked, they couldn't even tell me what they'd changed. It didn't seem reasonable for me to try and maintain it under those circumstances - it was a nightmare for me, whereas they know their own API, presumably - and then they asked me to add more features... so I told them to do it themselves!

Forgive me for being so direct but, why dont Scirra make its own exporter?For CocoonJS or for mobile period?

For the former, the post explained why.

For the latter is that they are working on C2 and that if they work on an exported C2's production would cease, in which during the time the wrappers would have improved to the point where their own exporter/wrapper would've been a waste of time since they would only provide minimal feature support due to lack of time.

The main problem Scirra has for tackling it is that they're a 2-3man team, and they just don't have the resources to do that AND make Construct 2. Putting C2 on hold too long is very bad.

What we need is an open source wrapper, essentially Node-Webkit for Android/iOS. That way the project is supported by many people, and either they or Scirra would just have to stay compatible by updating the plugin/exporter. Basically like how they do Node-Webkit for PC.

Chrome can already be compiled for Android with all FLAGS turned on. Chrome can be modified to launch a certain index.html.

At this time Chrome can be used as the wrapper. Someone just has to do it.

In the mean time we are mired in polotics :|