Just throwing a little fuel on the fire. If anybody cares give this a whirl -- build your own custom jQuery.
Maybe I'll figure out how to do plugins if anyone is interested. http://corey.jquery.com/cgi-bin/make.cgi Corey On Nov 14, 2006, at 9:32 PM, John Resig wrote: > I definitely agree. I'm going to propose this course of action: > > 1) Strip out all "helper" functions into an external plugin. > 2) Change the official (in SVN) plugins to no longer use the helpers. > 3) Change all docs to no longer use the helpers. > > This will clear up documentation and reduce the filesize (win-win!) > I'm going to persue this avenue long before having mutlitple builds > (which only tends to complicate the matter). > > --John > > On 11/14/06, Blair McKenzie <[EMAIL PROTECTED]> wrote: >> I've been thinking the same thing actually. The messiness of three >> functions >> for every event (bind, unbind, and trigger) outweighs the >> convenience. I >> think that all these macros should be spun out into a plugin so >> that they >> can still be included for backwards compatibility when necessary. >> >> Blair >> >> >> On 11/15/06, dave.methvin <[EMAIL PROTECTED]> wrote: >>> >>> >>> John Resig wrote: >>>> >>>> Right now, the jQuery compressed build is teetering around >>>> 18-19KB, I >>>> really want to try and cut this down. Any thoughts on particular >>>> features that should be extracted into a plugin? >>>> >>> I know the macros don't account for _that_ much core code but >>> they do >>> complicate the documentation significantly. We have nice short >>> names like >>> .attr and .css yet those represent the most-macroed properties. >>> Then we >> end >>> up with (justifiable IMO) situations where valuable names >>> like .height() >> are >>> taken by the .css("height") macro to save five--count 'em--five >> characters. >>> The same goes for the event macros, I think they account for more >>> than >> half >>> the names in the API documentation at this point and they end up >>> creating >>> situations like .unload() that are pretty hard to explain. >>> >>> I would like to see jQuery take more of a Perl path than a PHP >>> one, using >> a >>> small number of consistent and powerful concepts plus the ability to >> extend >>> things with plugins. Perl has one simple consistent regexp >>> operator; PHP >> has >>> two completely different regexp engines, each served by a dozen >>> or more >>> differently named functions. >>> >>> >>> -- >>> View this message in context: >> http://www.nabble.com/jQuery-1.1-by-the-end-of-Nov- >> tf2631987.html#a7351892 >>> Sent from the JQuery mailing list archive at Nabble.com. >>> >>> >>> _______________________________________________ >>> jQuery mailing list >>> [email protected] >>> http://jquery.com/discuss/ >>> >> >> >> _______________________________________________ >> jQuery mailing list >> [email protected] >> http://jquery.com/discuss/ >> >> >> > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
