I agree that it should be as simple as possible for the end user, if only for our sanity because of the potential for increased support requests. I think the most simple and easy solution is to prominently display the (recommended) download, and have 4 other options for people who know exactly what they need:
1. jquery.js (recommended) (everything packed) 2. jquery-ajax.js (core + ajax packed) 3. jquery-fx.js (core + fx packed) 4. jquery-lite.js (core packed) 5. jquery-src.js (everything not packed) I think almost everyone can get what they need from those 5 options, and making the full package the recommended download should minimize the "function not defined" questions from new users. I'm thinking now that a download builder might be overkill. With only 4 main config options, why build something when prebuilding all combos is so trivial. I saw a comment above that suggested that the DOM part of the core was something to be included or excluded as well, but I don't think that at all. The DOM traversal and manipulation and event handling IS the core of jQuery. Exclude DOM handling, and you've not got much left. I also really like, and have been thinking about the idea of defining requirements in plugins. Most plugins I've either written or plan to write will require (or at least utilize if it's available) John's Metadata plugin. The Dimensions, Center, and Form plugins are also often required for others to work. I haven't thought it through enough to post a proposal, but my first thoughts were to wonder whether including a requirements list in the docs specification would be enough, or whether it will require some code to actually check. My leanings at the moment are that the documentation solution is the way to go with probably a @required and @recommended specification that would include a list of name:url pairs. I don't see a point in having a real method defined in the core for saying that what you need isn't there. If a plugin requires a function that may or may not be included, then the docs should be the first place a Dev should look. Plus the fact that it's trivially easy to check for a function you need in your plugin and throw an error if it's not there. I would like to hear more thoughts on this, but perhaps we should start a new thread and keep this one going on John's original questions. Paul _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
