I'm almost inclined to agree. When planning out the structure for the new documentation I realized that the 'Ajax' section was really more of a "Design Methodologies/Cookbook" section, more than anything else. Whereas the core dom/css is more of a toolset of functionality.
That being said - Ajax functionality is used a lot. If it were extracted, I'd want to have a special jquery+ajax build to go along with it. --John On 11/14/06, Paul McLanahan <[EMAIL PROTECTED]> wrote: > I'm personally not sure that the entire ajax.js should be part of the > core. jQuery to me is about DOM searching and manipulation. Its Ajax > features are excellent, but I wouldn't cry at all if I had to include > the ajax "plugin" or "official extension" or whatever you'd like to > call it, only when I needed it. I've actually done this on several > occasions when I wanted to save some bandwidth and I wasn't using any > of the ajax features. I've commented out ajax.js from build.xml and > packed my own ajax-free jQuery and it works great. It only saves > around 3k packed, but that's significant when we're talking about <20k > total. I realize that the politics surrounding not having the "ajax" > buzzword included in the library by default are a significant issue in > regards to developer addoption and jQuery marketing in general. But > it would further the goal of file size, and it really is pereferial to > the overall goal of jQuery. > > Paul > > On 11/14/06, John Resig <[EMAIL PROTECTED]> wrote: > > Hi Everyone - > > > > I want to start a discussion about the features that should go into > > (or be removed from) the upcoming 1.1 release. I'd like to shoot for a > > release by the end of this month. > > > > I know that Joern already has some event code, ready to be committed - > > and I have the "non-destructive jQuery" code ready to go. Brandon > > mentioned that he wants to rewrite the jQuery.attr() in time for > > release too. > > > > No significant features are going to be added to this release, think > > of it as jQuery 1.0++. > > > > 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? > > > > For example: Since the 'form' plugin already does serialization really > > really well (much better than jQuery's serialization). I'm tempted to > > remove the serialization plugin from core and just defer everyone to > > using the form plugin. > > > > Also, stuff like .height() and .width() could be removed in favor of > > using the (more powerful) methods of the same name in the 'Dimensions' > > plugin. > > > > Let me know if you have any ideas. > > > > --John > > > > _______________________________________________ > > jQuery mailing list > > discuss@jquery.com > > http://jquery.com/discuss/ > > > > _______________________________________________ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
