Sometimes Behaviour is good, sometimes it is bad. For instance, when creating a simple site which only uses JavaScript to create new windows Behaviour is great. Since it is standalone, no other libraries like Prototype or script.aculo.us are required. In those cases you could use this simple code after including Behaviour:
var rules = {
‘#item li’: function(element) {
Event.observe(element, ‘click’, function(event) {
var element = Event.element(element);
element.setStyle({color: ‘#c00′});
});
},
‘#otheritem li’: function(element) {
Event.observe(element, ‘click’, function(event) {
var element = Event.element(element);
element.setStyle({color: ‘#c00′});
});
}
}
However, if you are already using Prototype, Behaviour repeats a lot of the same code. Here’s where event:Selectors comes into the picture. This simple framework is built on top of Prototype and adds a few features like multiple selectors for one function and auto event attachment. Otherwise, it is pretty much the same as Behaviour, just built on top of the Prototype framework. Using event:Selectors, the same code as above is about half the length. If you are using Prototype in your next application, I recommend you use event:Selectors. Hey, I am.
var Rules = {
‘#item li:click, #otheritem li:click’: function(element) {
element.setStyle({color: ‘#c00′});
}
}
0 Responses to “Bad Behaviour”