Andro.js
maryrosecook.com
maryrosecook.com
However, I think that sprinkling andro.eventer all over the place is a stumbling block to me - it's essentially a global variable.
I realise that you don't want to polute the objects too much, but why not just add bind and emit methods to the composed object? Either that or pass andro as a parameter to the mixin's setup method?
Also, the bind(this, "touch", function...) to me looks like you're binding to the "touch" event of "this". Is the closure tax really so high that you can't store "this", or use something like jQuery.proxy()?
Like I said, I think this approach has a lot of potential, and seems to fit quite naturally the eventful model that the DOM uses.
Yes, andro.eventer is there to avoid polluting the owner object. However, your idea of passing andro to the behaviour's setup() method is a great one. I'm going to give it a try.
The reason I require the behaviour to be passed to bind() is so that the passed function can be run with `this` set to the behaviour. I couldn't see another way to let bind know which behaviour should be bound to the event.
Repeating strings is hard to refactor and comparing strings is much less efficient than comparing integers. Think about making sure every bit in two 2 * 8 * length string of bits plus overhead is the same vs two 32bit integers. The latter far fewer cycles.
var firstTouchBehaviour = {
touchCount: 0,
events: {
firstTouch: 'FirstTouch'
},
setup: function(owner) {
andro.eventer(owner).bind(this, "touch", function(contact) {
if(contact === "added") {
if(this.touchCount === 0) {
andro.eventer(owner).emit(this.events.firstTouch);
}
this.touchCount++;
} else if(contact === "removed") {
this.touchCount--;
}
});
}
};
var soundBehaviour = {
setup: function(owner) {
andro.eventer(owner).bind(this, firstTouchBehaviour.events.firstTouch , function() {
console.log("Rarrrrrwwwwwwwwwwwwwwww");
});
}
};