Object (and his lil’ bro Hash), Date, Locale work as well, but in Date.js, this line :

var Date = this.Date = {};

has to be commented out (I don’t know why, I haven’t dug deep enough).

Unfortunately, since there’s no window or document object, it looks like Element is going to be a little bit more complicated to implement.

God I miss Jaxer which worked altogether with mootools (Not only Class, but Element, Date, Array, Hash, Window or Event as well).

Is there any way to get Element back into the server build ?

Slick is not only about speed but mostly about accuracy. It doesn’t matter how fast your engine is, if at any time it returns wrong results. You must be able to rely on your selector engine to be correct at all times and this is what we focus on. Also note that Slick is optimized for all selectors and not just a couple of selectors that we assume you use often.

Slick does use qSA if available and appropriate.

SlickSpeed came from a time when selector engines took several hundred ms to match certain elements. As you can see, the difference in all selectors is only a few ms. Microseconds. And this difference probably comes from rounding errors. All selector engines are fast enough and if you experience slowdowns because of the used selector engine you either have inappropriate code (no caching etc.) or a huuuuge document. Please don’t use SlickSpeed any more to compare selector engines. It helped improve engines a few years ago, but the aim SlickSpeed used to have is fulfilled and the project is finished. As said, Slick is about accuracy first, speed second.

Please note that MooTools 2.0 will likely allow to switch out the Finder part of Slick with any other selector engine (Slick.Finder.js, Slick.Parser.js will still be required). I don’t promise it though. I coined it a couple of days ago and we have a possible implementation.

Thanks

Does Mootools use document.querySelector(All) when avaiable?