I also want to share with you the next step of Cocos2d-JS:
After a long discussion in the forum and many times offline discussion in the Cocos2d team, we have made a choice for the future of Cocos2d-x and Cocos2d-JS
The long discussion: http://discuss.cocos2d-x.org/t/discuss-the-next-step-of-cocos2d-x/21182/
The General Idea
Generally, we want to merge back Cocos2d-JS into Cocos2d-x.
We don’t want our user to choose between different product or packages anymore. No matter which language you use, cpp, js or lua, no matter which platform you want to distribute, desktop, android, ios, wp or web, you can use the same and the one Cocos2d-x. End of the confusions.
How to do it
We will merge both the web engine and the native engine into Cocos2d-x repo (This is already done).
Cocos2d-x and Cocos2d-JS will still release their v3.7 separately.
But the future version will be totally merged.
How to upgrade
In fact, we have a solution which won’t make a big change in user’s project. We also want the upgrade will be as smooth as possible. Although the framework folder structure won’t be the same at all, but we ensure the user project to remain the same structure. There will be only one difference:
The old project structure:
The new project structure:
We will also provide a upgrade tool to help users to upgrade their project to new versions.
If you have any thoughts, please let us know, you can join the discussion here