Thanks for responding, John. I realize the jQuery team might not be interested in doing anything less than supporting the full API, but I think mobile developers would find it useful to have something jQuery-like that implemented the "good parts" to bastardize Crockford's idiom. Chaining, plugins, plus an 80% implementation of the jQuery API in a tight little package would be a boon to a lot of folks, I think.
Am I free to release a WebKit-only/first library that does that? Any restrictions on using jQuery code for it? Any restrictions on mimicking the jQuery API? I realize, no Devo hat for a logo. ;-) On Jul 18, 12:24 am, John Resig <jere...@gmail.com> wrote: > Andrew - > > We've thought about this issue a bunch and, unfortunately, there's just not > a whole lot that can be successfully removed from jQuery. > > For example, if we scale back to just using querySelectorAll then all > filter() operations will fail (since qSA doesn't provide a means of > filtering, only finding). > > It would seem like there are two possible avenues: A custom jQuery version > builder (for customizing the modules that you want to load) or a dynamic > script loader (so that you just load a core version of jQuery and > dynamically load the other modules that you'll use). We can persue this > avenue but, at least for now, it doesn't seem terribly enticing (especially > since you're looking to increase the window beyond just WebKit - which makes > it harder to support more browsers). > > --John > > > > On Fri, Jul 17, 2009 at 8:09 AM, Andrew Hedges <segd...@gmail.com> wrote: > > > Rey Bango indicated that a mobile-optimized version of jQuery is "on > > the radar" of the development team. I'd be interested in contributing > > to efforts in that direction. I've been doing a lot of WebKit-specific > > mobile development lately and it seems to me it ought to be possible > > to offer a version that works on WebKit, Fennec, and Opera that is > > vastly smaller than the full jQuery implementation. > > > E.g., would it not be possible to eliminate the entire Sizzle engine > > (as tight as that code is) by leveraging document.querySelector and > > document.querySelectorAll? Another example on a smaller scale is Ajax. > > There is no need to branch looking for ActiveX in IE in the browsers > > mentioned. FWIW, I'm not as concerned about speed optimizations as I > > am about just reducing the size of the codebase. Some of us live in > > countries where mobile data is exorbitantly priced! ;-) > > > Is there an official effort to create such a library? If not, is there > > any restriction on someone like me implementing a clone of the jQuery > > library focused solely on particular browsers? > > > Regards, > > -Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
