I've been working on env.js again, lately - some initial results here: http://github.com/jeresig/env-js/tree/master
A big thing that I'm pushing for is trying to get as much of the script converted into pure-JavaScript as possible. This includes having a pure-JS HTML parser (previously it only parsed XML), pure-JS threading (for setTimeout/setInterval), a pure-JS CSS engine (parsing CSS rules and dynamically updating them), and a pure-JS DOM. I'm also working on flushing out the DOM implementation to be more complete. Please let me know about any parts that were affecting you and I'll see what I can do to help. --John On Jun 26, 7:02 am, Nick Thompson <[EMAIL PROTECTED]> wrote: > Jresig's env.js is very incomplete i'm afraid. I think he > did close to the minimal amount necessary to make it > run the jquery test suite. > > I think this because i extended env.js to run parts of the mjt > test suite and it was still a woefully incomplete browser > implementation. There has been more recent work on env.js that > i haven't followed, somebody forked it or maybe continued > development somewhere in jquery svn? But it's a big project. > The httpunit people are on the front lines of this one with an > impressive rhino-based browser emulator, and it's complicated. > > In the end i realized that i didn't actually want most browser > features on the server. It's a very different world when you > are delivering static chunks of html instead of manipulating a > live on-screen document. Note well that people doing server-side > php or whatever don't use anything resembling DOM or XHR - because > template languages and synchronous i/o models are better tools > for generating static pages. The browser dom has one advantage, > which is that it allows dynamic behavior (though even then you need > jquery to write reasonably expressive dom manipulation code). > > That said, rhino users would benefit from some standard libraries for > http requests and html/xml parsing. Maybe "extension" is a better term > than "library" because most of it would be glue to existing java > libraries... > > nick > > Terry Braun wrote: > > John Resig - ejohn.org - implemented some html, web simulator that > > might help do what you want. > > > Martin Honnen wrote: > >> Michael Bodin wrote: > > >>> "Cannot find function getElementById"? > > >>> am I dong something wrong or isn't getElementById implemented yet? (is > >>> this > >>> possible to do in this way?) > > >> The script engine does not implement DOM methods like getElementById. > >> The script engine implements the JavaScript core language as documented > >> here:http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference > > > _______________________________________________ > > dev-tech-js-engine-rhino mailing list > > [EMAIL PROTECTED] > >https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
