Sizzle and Peppy Selector Engines in MooTools
A few weeks back I touched on how you could implement the Peppy and Sizzle selector engines in MooTools. Both posts showed how to remove the default Moo engine from use and instead make each respective selector engine the one and only. It doesn't have to be that way. You could use all three engines within the page as well.
Peppy, Sizzle, and Moo Together
//assuming that the JavaScript files we brought in via simple XHTML above...
/* MooTools */
var divs = $$('div');
/* Sizzle */
Window.$Sizzle = function(selector){
return new Elements(new Sizzle(selector));
}
//sizzle usage
var divs = $Sizzle('div');
/* Peppy */
Window.$Peppy = function(selector){
return new Elements(new peppy.query(selector));
}
//Peppy usage
var divs = $Peppy('div');
Why do this? Each engine has its advantages. Sizzle generally does better with Internet Explorer so if you detect that the user is using IE, you may want to use Sizzle to grab the elements instead.
In most cases the overhead of bringing in each engine makes this strategy overkill. It's definitely an option though.
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![7 Essential JavaScript Functions]()
I remember the early days of JavaScript where you needed a simple function for just about everything because the browser vendors implemented features differently, and not just edge features, basic features, like addEventListener and attachEvent. Times have changed but there are still a few functions each developer should...
![CSS Fixed Position Background Image]()
Backgrounds have become an integral part of creating a web 2.0-esque website since gradients have become all the rage. If you think gradient backgrounds are too cliche, maybe a fixed position background would work for you? It does provide a neat inherent effect by...
![Sexy Album Art with MooTools or jQuery]()
The way that album information displays is usually insanely boring. Music is supposed to be fun and moving, right? Luckily MooTools and jQuery allow us to communicate that creativity on the web.
The XHTML
A few structure DIVs and the album information.
The CSS
The CSS...
Is there any REAL and REAL-WORLD benefit to actually do this or include one of the other selector engines? Does one get the performance from Sizzle when just using its selector engine? .. :f
Great shit though David. :)
I can’t wait to test sizzle. Where can I get a break down of each engine’s benefits?