Plugins

[straker]

Here's a draft of what I'm thinking for the plugin architecture. It's just a simple pub/sub architecture that should let anyone subscribe to certain lifecycle events and do what they need from there.

So for example, both kontra.vector and kontra.sprite emit init events that plugins to can use to attach new functionality such as advanced vector functions or auto collision detection for different sprite shapes.

What do you think @BoldBigflank, @jaronwanderley, @Quentie?

[coveralls]

Coverage increased (+0.1%) to 98.738% when pulling 5e7f75c on plugins into f4896a3 on v6.

[BoldBigflank]

Looks good at a glance so far. Is there a way to remove listeners, or off, for loading/unloading many instances.

[straker]

Great idea, I'll add it in

[straker]

Alright, I found a solution I'm pretty happy with. I've added a new Plugin architecture using the Interceptor Pattern that will allow multiple plugins to register functions on the same Kontra object function. I've also added a way to safely extend a Kontra object with new properties without overriding ones that may have been extend already.