cocos-utils

cocos-utils is a tool to support NPM branch of Cocos2d-html5 only, aims to help developers using cocos2d-html5 easily.

中文详细说明

Installing

• Install nodejs...
• Install ant...

The function cocos publish requires ant, if you don't want to use cocos publish, you don't need to install ant.

• Then type:

npm install cocos-utils -g

You know, it may take a long time to install modules from npm in China, because there is a "Wall". In this case, you can try this:

npm --registry "http://registry.cnpmjs.org" install cocos-utils -g

And when using cocos install and cocos update, you may need to add an option, such as cocos install -r, or cocos install -r "http://registry.cnpmjs.org". The -r option default to be http://registry.cnpmjs.org.

Sometimes, you should type sudo npm install ... in mac or lunix, because npm requires administrator permissions.

Type cocos help to check whether the installing is successful.

HelloWorld

Install all modules of cocos2d-html5

cd your/workspace/
cocos install

Sometimes, you should type sudo cocos install in mac or lunix, because cocos install calls npm install, and npm requires administrator permissions.

Sometimes, you may need to use cocos install -r if you are in China.

Create project of cocos2d-html5

(under your workspace)

cocos new helloworld
cd helloworld
cocos build

Visit dev version

Be sure that your project and modules of cocos2d-html5 have been published in a webServer, then visit http://serverhost:port/your/project/path/index.html in your browser.

Pay attention to this, modules of cocos2d-html5 should also been published in the webServer.

Open it with FireFox if you have not published them in a webServer.

Publishing

(under helloworld)

cocos publish

Visit release version

Be sure that your project has been published in a webServer, then visit http://serverhost:port/your/project/path/release.html in your browser.

Open it with FireFox if you have not published them in a webServer.

Structure of project

- node_modules (dir of engine modules)
    -cocos2d-html5 (core for engine)

- helloworld (project dir)
    - cfg
        - res.js (Config of path of resources, generated by cocos genRes)
        - jsRes.js (Config of path of js sources, generated by cocos genRes)
        - resCfg.js (Config of dependencies for all resources)

    - res (Path of resources)
        - Normal (Normal version)
        - HD (HD version)
        - Audio

    - src (Dir to put sources)
    - test  (Dir to put test sources)

    - node_modules (dir of third party modules)

    - cocos2d.js (Boot config of game)
    - main.js (Main for game)
    - baseCfg.js (Base config for game to load js and so on)
    - index.html (Url of dev version)

    - mini.js (Generated by cocos publish)
    - build.xml (Generated by cocos publish, used for closer compiler)
    - release.html (Url of release version)

    - cocos.json (Config for cocos command)

    - package.json

Files generated by the utils.

There are files generated by the utils, which you should not edit by yourself. Because they may be overwrited while running cocos command again.

• files in __temp
• res.js
• jsRes.js
• baseCfg.js
• build.xml (after publishing)
• mini.js (after publish)
• sourcemap (after publish)

cocos.json

This file is about config of cocos command. If there is something wrong while using cocos command, check this file first.

Click here to see more details.

resCfg

This is the main config for the dependencies of the project. It is the core to load js and resources, just like what resources.js and appFiles of cocos2d.js do in the develop branch. cc.js takes place of jsLoader.js, so jsLoader do not work in this npm branch.

Click here to see more details.

package.json

Same as package.json of npm.

Third party modules will be configured in dependencies. If you add or delete a module (dependencies in package.json or cocos.json), you should run cocos build or cocos genBaseCfg once more.

Unit Test

By default, we have provided some test functions for you. Also you can define your own test functions.

Click here to see more details.

Notes

Do not forget run cocos genRes if you add or delete resources, rename the resources or change the paths of the resources.

Do not forget run cocos genJsRes if you add or delete js, rename js or change the path of js.

Do not forget run cocos genBaseCfg if you install or uninstall modules of cocos2d-html5 which are configured in dependencies of cocos.json, or of third party which are configured in dependencies of package.json.

In fact, you can use cocos build which includes these three command above.

Be sure that each key in your res.js and jsRes.js is unique, which is generated by the file name. The rule of key is :

a.png  :  a_png        //"." will be replaced by "_"
a-b.png  :  a_b_png    //"-" will be replaced by "_"
1a.png  :  _1a_png     //"_" will be add before if the first char is a number
a b.png  :  ab.png     //" " will be replaced by ""

cc.js will be replaced with cc4publish.js when publishing.

There are test cases in each modules of cocos2d-html5, which is quite different from the develop branch. The code is clearer and smaller for developers. And I think it is a better way for developers to learn cocos2d-html5. Keep all modules of cocos2d-html5 in the same folder, boot your web server, then visit it(index.html in each module).