cyan33 / zion

[Deprecated] A tentative, light-weight 2D game framework based on HTML5 canvas.

Zion

A tentative, light-weight game engine/framework based on HTML5 Canvas game development.

Get Started

npm install --save zion-engine

import zion from 'zion-engine';

Features

Check the document here.

Tutorial and Resources

Building A Canvas Game Engine / Framework From Scratch by Chang

Contribution

All PRs, issues and bug report are welcomed. Here are the steps to contribute:

1. Fork and clone this repo.
2. Make some changes.
3. Commit, push the changes to your forked repo.
4. Compare and make a pull request.

Sample Projects

Having trouble getting started? See the engine in action [.

Acknowledgement

• @jegood95

zion's Issues

Cannot build the network component

ERROR in ./node_modules/socket.io/lib/index.js
Module not found: Error: Can't resolve 'fs' in '/Users/changyan/Documents/repos/zion/node_modules/socket.io/lib'
 @ ./node_modules/socket.io/lib/index.js 7:11-24 9:13-26
 @ ./src/network.js
 @ ./src/index.js
 @ multi ./src/index.js ./src/index.js ./dist/zion.js

Generate the document site using gitbook

Add target usages scenarios and more clarification in the beginning of the doc

The term "Game engine / framework" is too big and ambiguous.

Right now we are at a point where our "game engine" is only limited for certain scenarios, for example, light-weight canvas game. It doesn't support WebGL for advanced rendering techniques. And the performance benchmark is quite unclear.

So I think it quite necessary that we clarify the use scenarios as specific as possible at the very beginning, rather than just say "it's a canvas game engine". I got this feedbacks from a Chinese programmer forum, v2ex.com.

modularization convention discussion

Along the way I'm working around with javascript packages, I noticed that it looks like the best practice is using closures instead of Class when handling modularization.

So in our game framework, I also took this approach, in which case, most of the game components like canvasUtils, drag n drop, AI, should export something like createXX(). But for some of the base class like Sprite and Particle, the intuitive way is to use class. So I think I should just mix them up.

But like you can see, everything inside the src/component folder uses class, while other modules outside uses closure.

Just to clarify things up.

Building error: cannot resolve path

ERROR in ./src/index.js
Module not found: Error: Can't resolve './components/index' in '/Users/changyan/Documents/repos/zion/src'
 @ ./src/index.js 8:23-52
 @ multi ./src/index.js ./src/index.js ./dist/zion.js

You ID changed, the button `here` not work. :)

emmm, good ID.

Production Ready

Is this library/ framework production ready :-)??

Ground re-write of the core code

TODOs:

• A new bundler
• isolated packages
• easy-to-setup fixtures

Make all the APIs uniformed and converge to `Zion`

convert to es6 syntax