Check out Packager and the removables. There are special comments in the source code around stuff that can be removed. You can use Packager to create a specific build that strips those blocks out.
— Thomas Aylott – SubtleGradient – MooTools – Cloudera — On Nov 1, 2010, at 11:57 AM, doubleTap wrote: > Hey Everyone, > > One of the original intentions of most javascript toolkits was to > unify the API for each browser/javascript engine. But, we are coming > into a world where Javascript engines are being used in ways that > exclude the use of other engines for a unique codebase. For example, > the extensions of Chrome and Safari or the V8 based server-side web > servers, do not require the switching for other possible browsers/ > javascript engines accessing the codebase developed for those > installs. > > Off my "preaching to the choir" soapbox, considering this and the > build engines for Javascript Toolkits and Frameworks like those for > MooTools, I think it might be a bit easier to achieve engine specific > builds and maybe it is already done. So, my current need is for a > build that is targeted to V8. Is it already done or maybe easily > possible? If it is not yet completed, what is involved in this task? > > Thank you, > > dobleTap
