> Actually, I copied the contents of Sizzle into Selector.js which is > part of MochiKit [1]. Integrating is then just a matter of calling > Sizzle(...) in the correct place in the Selector API. Our plan is to > completely remove the old Selector implementation, i.e. using Sizzle > won't be optional like it looks like your plan for jQuery is.
It's only going to be optional during this development process - I'm planning on integrating it (and making it mandatory) in the upcoming jQuery 1.3 release. > [1] > http://trac.mochikit.com/browser/mochikit/branches/selector_sizzle/MochiKit/Selector.js > > I don't know what other MochiKitters say about including Sizzle.js as > a seperate file. Per, Bob? So it seems like the major difference is that your selector method (findChildElements) is able to take an array of results, correct? --John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
