Implement jQuery-like “Click” Syntax In MooTools 1.2
I've updated this post's content per reader comments. Thanks to everyone for their suggestions!
While I prefer the MooTools syntax over the jQuery syntax, I do respect the jQuery syntax. Here's a quick way to make your MooTools look a little like jQuery by implementing the Element.click() function.
The MooTools JavaScript
Element.implement({
'click': function(fn) {
return this.addEvent('click',fn);
}
});
The MooTools JavaScript Usage
window.addEvent('domready',function() {
//show an alert when the element is clicked.
$('click-me').click(function() {
alert('Clicked');
});
});
This syntax will allow for shorter code if you do a lot of click event programming.
![9 More Mind-Blowing WebGL Demos]()
With Firefox OS, asm.js, and the push for browser performance improvements, canvas and WebGL technologies are opening a world of possibilities. I featured 9 Mind-Blowing Canvas Demos and then took it up a level with 9 Mind-Blowing WebGL Demos, but I want to outdo...
![9 Mind-Blowing Canvas Demos]()
The <canvas> element has been a revelation for the visual experts among our ranks. Canvas provides the means for incredible and efficient animations with the added bonus of no Flash; these developers can flash their awesome JavaScript skills instead. Here are nine unbelievable canvas demos that...
![AJAX Page Loads Using MooTools Fx.Explode]()
Note: All credit for Fx.Explode goes to Jan Kassens.
One of the awesome pieces of code in MooTools Core Developer Jan Kassens' sandbox is his Fx.Explode functionality. When you click on any of the designated Fx.Explode elements, the elements "explode" off of the...
![Cross Browser CSS Box Shadows]()
Box shadows have been used on the web for quite a while, but they weren't created with CSS -- we needed to utilize some Photoshop game to create them. For someone with no design talent, a.k.a me, the need to use Photoshop sucked. Just because we...
Hey, Just wanted to say thanks for your blog, its really helped me along with Mootools, and I enjoy working and creating things with ease.
I just need to know thou,
Should I be switching over to JQuery.
with Microsoft’s decision to incorporate JQuery, I’m wondering if I’m using the wrong framework.
I read the article at juliocapote.com
and well I just need a Yes or a No.
I trust your judgment.
and
Iis the future of Mootools sound?
Nice, but why not just pass the whole ‘fn’ to the ‘addEvent’ function? Eg:
Element.implement({ 'click': function(fn) { this.addEvent('click', fn); } });.. because some coders might probably do this:
$('click-me').click(function(e) { e.stop(); alert('Clicked'); });… and probably some don’t want to ‘stop’ the event by default.
@Lim Chee Aun: Great tip! I was trying to get something similar to work but couldn’t get it going. Thanks for sharing!
@david: No problem. I’m actually working (very slowly) on porting (almost) all jQuery-style syntax to Mootools. Not sure if it will be useful though.
Something I’ve thought of that might be a slight problem, though haven’t tested, is binding.
I could see someone trying to use this keyword, and might even remember to bind it in the click function, but when it gets used in the addEvent part, you didnt bind this.
Like I said, haven’t tested for actual failure, but in theory it sounds breakable :D
In my meager JavaScript dabblings, I’ve always been jealous of jQuery’s event syntax. Needless to say, I’m really happy to see this as an option.
I’m somewhat of a hobbyist, so I apologize in advance for any mistakes. I did a little playing around and it looks like it doesn’t break .bind(this). This, of course, is a trivial implementation and there’s a chance that I totally misused .bind()
If anyone’s curious, the link in my name goes to my uh … ultra-complex tests :P
Element.implement({ click: function(fn){ return this.addEvent('click',fn); } });@david
i think you should “return this”
after implementation
Element.implement({ ‘click’: function(fn) { this.addEvent(’click’, fn); return this } });