Dunno... -- Fábio Miranda Costa front...@portalpadroes Globo.com *github:* fabiomcosta *twitter:* @fabiomiranda *ramal:* 6410
On Mon, Oct 25, 2010 at 7:43 PM, Eneko Alonso <[email protected]>wrote: > Does Element work with jsdom? > > > 2010/10/22 Fábio M. Costa <[email protected]> > > adampbragg, >> >> You should take a look at htmlparser and jsdom, they are the way to go >> when you want DOM on nodejs. >> >> >> - http://github.com/tmpvar/jsdom >> >> >> You can install htmlparser using npm (http://npm.mape.me/) It's just a >> dependency of jsdom. (you can install jsdom using npm too by the way). >> It has worked pretty well for me, but i havent tested it with mootools on >> nodejs. >> >> Give us some feedback if it works fine!! >> Thanks. >> >> -- >> Fábio Miranda Costa >> front...@portalpadroes >> Globo.com >> *github:* fabiomcosta >> *twitter:* @fabiomiranda >> *ramal:* 6410 >> >> >> >> >> On Fri, Oct 22, 2010 at 11:31 PM, adampbragg <[email protected]> wrote: >> >>> I am putting together a server-side stack with MooTools/Node.js/ >>> MongoDB and so far I love it. But, when looking at the existing >>> templating engines and frameworks, I was less than satisfied. I would >>> love to plug something like MooML into the stack but in the sever-side >>> build, Element and others are missing. Is anyone working on getting >>> classes like Element into the server-side build? There is tremendous >>> opportunity on the server-side for DOM work. I just don't want to >>> double up on someone else's work, nor am I committing to doing this >>> work even though I might :) >>> >>> As a related aside, I have an interest in getting the server-side to >>> mirror the client-side closely, at least at the api level, for an idea >>> I have. >>> >>> So, the question is, is anyone working on getting the DOM related >>> classes into the server-side build or has anyone investigated this? >> >> >> > > > -- > Eneko Alonso > Software Engineer > http://enekoalonso.com > San Luis Obispo, California >
