Comments on: Implement Other Selector Engines (e.g. Sizzle or Peppy) into MooTools?

By: Anthony Alexander

Anthony Alexander — Mon, 25 May 2009 06:03:42 +0000

I use peppy in my framework and its quite great. I had no intention of writing my own selector engine and peppy came to save me right when I felt like I had no choice. I never thought Mr.Resig would detach sizzle from jquery, but I was wrong. Peppy does seem to be giving me different results some time but so far a quick look at sizzle and i cant even begin to understand how I’m going to integrate it. Sizzle’s selectors are far more advanced but it only took me a few hours to completely rework my framework for easy integration with Peppy. I’ll test it this week and post my findings.

By: Henrik Lindqvist

Henrik Lindqvist — Sat, 07 Feb 2009 02:20:55 +0000

LlamaLab got a small and fast selector.

By: Diego Perini

Diego Perini — Thu, 25 Dec 2008 19:21:45 +0000

Javier,
caching is good, it especially very good if it is used for something that never changes. In NWMatcher I compile CSS selectors to Javascript functions and then I cache them indefinitely.

They are not going to change.

Caching of results sets is a different and more complex matter though and in NWMatcher I decided to give the developers the power to switch results caching ON and OFF or flush it as they see fit in their projects.

By: Garrick

Garrick — Mon, 08 Dec 2008 08:19:22 +0000

@Carl, Javier, phiggins
Thank you for your input.

@Diego
MWMatcher huh? I’ll definately take a look at this one. Thank you for sharing.

By: Diego Perini

Diego Perini — Sun, 07 Dec 2008 17:15:55 +0000

W3C specifications compliance is a very difficult thing to achieve.

Failing in the most obvious points is the only real thing these frameworks have in common.

A selector engines considered for inclusion in so many frameworks should at least be able to guarantee the result sets are “document ordered” in any case.

This is not what you get neither from Peppy nor from Sizzle, Mootools, YUI and any other popular framework.

You will say I am just an unknown trying to push his solution instead, but really I have been quite for two years I can keep quite for two years more.

My code was released in 2007 and I released it under MIT License for the exact same scope Sizzle had. Unfortunately it is not easy to convince developers and it requires some time until they realize they have to move.

You will find my “mwmatcher.js” on Google Code:

http://nwevents.googlecode.com/

it is released with a companion Event Manager that also handles delegates cross-browser, this was what pushed me write NWMatcher.

Strange enough everybody knows Peppy and not NWMatcher though, have to work on this a bit.

A new release of NWMatcher (v1.1) will be out in a few more days.

–
Diego

By: Dojo’s Dylan Schiemann and jQuery’s John Resig On My Sizzle Post » Clientcide (Formerly CNET’s Clientside)

Thu, 04 Dec 2008 18:52:59 +0000

[...] are benefits and drawbacks and I’m curious as to what others think about it. Garrick Cheung weighed in with his own blog post, saying: Aaron brings up very good pros and cons. I think we should not follow the trend and switch [...]

By: Carl

Carl — Thu, 04 Dec 2008 17:07:25 +0000

@Javier: Sizzle caches the query results too but only if DOM mutation events are available. Peppy just followed Sizzle in this aspect. See at the bottom: http://jamesdonaghue.com/static/peppy/peppy.js

By: phiggins

phiggins — Thu, 04 Dec 2008 13:04:36 +0000

fwiw, the Dojo vote strictly involves the adoption of the Sizzle project to the Dojo Foundation (which is a lot more than just “the Dojo Toolkit”). The motivation is the IP cleanliness, and licensing. It is not an issue of “should Moo adopt Sizzle, too?” … it is one of “Moo can use this code base because it is cleanly licensed and available”

By: Javier

Javier — Thu, 04 Dec 2008 12:39:40 +0000

I read somewhere that Peppy was using some type of caching. So, in a complete dinamic page, this is useless and speed is not real.

By: Carl

Carl — Thu, 04 Dec 2008 10:25:28 +0000

I think if you look at the source of Peppy and Sizzle then it will be quite clear why Peppy isn’t something to consider
I don’t want to offend it but it’s not quite mature (yet), though it passes all test!