pjs/extensions/python/dom
reed@reedloden.com 32c84ef97b Bug 419765 - "PyDOM script error, Python cannot handle dom events" (Add handling of the additional version argument) [p=toddw@ActiveState.com (Todd Whiteman) r=mhammond (NPOTB)] 2008-02-28 21:32:30 -08:00
..
nsdom Allow JS 1.7 in XBL. Bug 389322, r=brendan, sr=jst, a=brendan 2008-02-15 21:13:16 -08:00
src Bug 419765 - "PyDOM script error, Python cannot handle dom events" (Add handling of the additional version argument) [p=toddw@ActiveState.com (Todd Whiteman) r=mhammond (NPOTB)] 2008-02-28 21:32:30 -08:00
test Correct the semantics of Python global variables in event handlers. 2006-10-26 05:23:08 +00:00
Makefile.in
README.txt
makefiles.sh Bug 380846 - "Make the build system friendlier for XULRunner apps and extensions." r=bsmedberg. Adds confvars.sh files for all major apps and makefiles.sh for all extensions. 2007-05-23 13:08:44 -07:00

README.txt

This is the Python/DOM bindings for Mozilla.

These bindings consist of an XPCOM component implementing
nsIScriptRuntime, nsIScriptContext and related interfaces.  See
http://wiki.mozilla.org/Breaking_the_grip_JS_has_on_the_DOM for
a general description of what this means.

The XPCOM component is implemented in C++ and can be found in
the 'src' directory.  This component delegates to a Python implementation
inside a Python 'nsdom' package, which can be found in the nsdom directory.

This directory is built by configuring the Mozilla build process with
the 'python' extenstion enabled - eg, '--enable-extensions=python,default'

The 'test' directory contains all test related code - notably a 'pyxultest'
chrome application.  If you build with --enable-tests, you can run this test
by opening the chrome URL 'chrome://pyxultest/content' (exactly how you do 
that depends on what project you are building). See test/pyxultest/README.txt
for more.