Tankenstein
commented
9 years ago I personally feel like the most intuitive way to use a game engine would be to create a class that extends from a base class for different types of objects, and defining methods on those classes. I feel like using mixins with functions would be more convoluted.
An example would be this:
class Hero extends Flockn.Entity {
constructor() {
super();
this.name = 'Hero';
this.texture.image.filename = 'hero_front.png';
}
update(deltaTime) {
this.angle += deltaTime*10;
}
onKeyDown(keyCode) {
switch (keyCode) {
case Flockn.keys.UP: // fallthrough
case Flockn.keys.w:
this.position.y -= 10;
break;
case Flockn.keys.DOWN: // fallthrough
case Flockn.keys.s:
this.position.y += 10;
break;
case Flockn.keys.LEFT: // fallthrough
case Flockn.keys.a:
this.position.x -= 10;
break;
case Flockn.keys.RIGHT: // fallthrough
case Flockn.keys.d:
this.position.x += 10;
break;
}
}
onMouseClick() {
alert('You clicked that hero guy.');
}
}I also feel like onMouseClick there could be refined, by making it more like onKeyDown, so there would be something like onMouse, with some kind of event as an argument.
This class way should feel familiar to anyone that has developed in Unity or the like, so there would be some basic methods like the constructor, update and event handlers.
frostney
This is not something that will be tackled for the 0.1.0 release.
While I really like ES6 classes, I am contemplating if they are really needed in the flockn game engine. Every object is described as a function and not as a class. Internally they are being converted to ES6 classes with a base class. I'm wondering if it that is really needed or we could opt for a more mixin-based approach. I'm even wondering if we need classes all-together, as I feel it might create a rift between how the game engine is implemented and how it is used.