cyan33 / zion Goto Github PK

TODOs:

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

emmm, good ID.

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.

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.

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