Quote:
Originally Posted by Kelon
Is there ever any merit in cutting down a lib to the essentials that a particular exercise needs....? Oh I dunno, example if you want one... cutting down MooTools to the essential elements needed by the mRotate script at http://www.piksite.com. Is there ever a scenario where it's worth doing... ever? Is it even feasible (or sensible)?
Yeah, this is one of those wildcard questions isn't it. It's a serious one  , even if it's slightly mad. |
there's a new dependency checker which can look at what your script does and then list only relevant required components to be picked through the mootools.net downloader:
check
http://www.aryweb.nl/projects/mooDeps/
now personally, i believe that using gzip on css and js files + some packer (not eval based, say, yahoo one) will really be a better option in saving bandwith. you remain with a framework with it's full capabilities at little or no cost to the end user. by doing so, you can even reference the google hosted versions of the frameworks and save yourself bandwith anyway.
but should the time come when a feature is needed you may have neglected to include, no "recompile" or re-download of mootools will be necessary (other frameworks' approaches disinterest me)