thatcher / env-js forked from jeresig/env-js

env.js : A pure JavaScript browser environment.
Developed by John Resig (https://ejohn.org)
Major Contributers:
Chris Thatcher (https://github.com/thatcher)
GitHub repositories:
https://github.com/jeresig/env-js/
https://github.com/thatcher/env-js/
Mailing List:
https://groups.google.com/group/envjs
Lighthouse (Bug Tracking):
https://envjs.lighthouseapp.com/projects/21590-envjs/
Build Status:
https://runcoderun.com/thatcher/env-js
Original blog post:
https://ejohn.org/projects/bringing-the-browser-to-the-server/
Rhino (Java-based JavaScript engine)
https://www.mozilla.org/rhino/
Building:
* run "ant concat"
* Creates a platform-agnostic "dist/env.js" file and a Rhino-specific "dist/env.rhino.js" file.
Testing:
* run "ant test"
Java command line:
env.rhino.js can be run either with a "generic" version of the Rhino
library (js.jar), or with the repackaged/extended version of Rhino
supplied with env.js (env-js.jar).  If your application uses multiple
windows, frames, or iframes, or if it depends on precise adherence to
JavaScript object scoping in event handlers, you will have to use
env-js.jar.  Simple applications may be able to run with the generic
version of Rhino.
The command line used for testing env.js can be found in build.xml,
although the general form is:
     java -jar [jar file] [javascript file]
Where "jar file" is either "dist/env-js.jar", "rhino/js.jar", or your
local path to a different version of the Rhino js.jar file.  The
"javascript file" is the path to the JavaScript you wish to execute.
Installing:
1) Include the proper env.js file for your platform.
     load('env.rhino.js'); //if in a Rhino script
2) Tell env.js to load an HTML file from your file system that it should model:
     window.location = "some/file.html";
     Envjs("some/file.html");
   Optionally you can turn on/off settings by passing an options object:
     Envjs("some/file.html", {log: function(msg){ console.debug(msg) }});
3) Optionally trigger "document ready" events in one of these ways:
   a) standard window.load method:
     load('env.rhino.js');
     window.location = "some/file.html";
     Envjs("some/file.html");
   b) jQuery ready method:
     load('env.rhino.js');
     load('jquery-1.3.2.js');
     Envjs("some/file.html");
     load('some-code-that-sets-up-jquery-onready-behaviors.js')
     jQuery.ready();
   c) Other JavaScript frameworks have their own methods of setup, but the general pattern is:
     // load env.js
     // load your framework
     // tell env.js the base DOM to model
     // run any setup code for your framework
     // tell the framework that the document is loaded
Testing jQuery Compatibility:
* run ./bin/test-jquery.sh 1.3.2
* run ./bin/test-jquery.sh 1.3.1
* run ./bin/test-jquery.sh 1.2.6
* Checks out the given jQuery tag from Subversion into test/vendor/jQuery/[version],
  moves dist/env.rhino.js into the correct location in their tree, and runs the test suites.