Hello, note that anything on my 2.0wip branch is purely experimental. You might wanna check out my guest blog post on David Walsh (FTW) Blog: http://davidwalsh.name/mootools-nodejs which supports MooTools 1.3
Currently we have no plans to namespace and subclass any of the native types. The extensions to native objects on an ES5 implementation are fairly minimal. Why exactly is this an issue for you? Bye On Nov 12, 3:29 pm, gabriel munteanu <[email protected]> wrote: > Hi, > i took the server side mootools from > here:http://github.com/cpojer/mootools-core/tree/2.0wip > and built it with packager. > all goody. > now, when i load it in another module with require: > var MT = require('mootools.js'); > i get MT.Class as expected, but i get Array global object polluted. > i don't think this is good. if i would like mootools flavored Array, i > would create a var myArr = new MT.Array(); > is it possible to have MT.Array, and not pollute the global Array ? > > thank you in advance.
