apologies to jan but it turned out to be simply necessary and more
convenient: i've spent the past couple of weeks creating a new set of
python webkit DOM model bindings - direct python bindings *not* using
the glib/gobject webkit bindings. but, to do that, i had to
incorporate the whole of pywebkitgtk into webkit itself: it just
turned out to be much easier.
if anyone is interested, code simply can be adapted: instead of
"import webkit" it's "import pywebkit as webkit". as with the
original work done in 2008 to add python bindings on top of the glib/
gobject bindings (pywebkit patch here:
http://code.google.com/p/pywebkitgtk/issues/detail?id=13
) the function to begin gaining access to the DOM is the same:
WebFrame.get_webkit_document() or WebFrame.get_dom_window(). there's
also still WebFrame.get_xml_http_request().
the glib/gobject naming convention ends at that point: the names of
objects, properties and functions from then on conform to W3C standard
naming conventions, because it is truly ridiculous to expect people
used to web development in javascript to have to use different names
for absolutely everything.
the link to the source code from the git repository, and more about
the project, can be found here:
http://www.gnu.org/software/pythonwebkit/
put simply: if you do not need to "interact" with the DOM model of the
web page being displayed, then you do not need python-webkit. however
if you wish to have python function callbacks activated on mouse-
clicks of buttons or other elements, or if you wish to track the mouse
with onmousemove, or if you wish to create and add elements using
python code instead of being forced to execute javascript snippets
that do the same job - doc.body.appendChild(doc.createElement("div"))
for example - then you will _need_ python-webkit because pywebkitgtk
simply does not have this capability.
once again, apologies to jan for having to incorporate and adapt
pywebkitgtk in its entirety rather than provide patches to enhance
pywebkitgtk but if you take a look at the source code in the python-
webkit git repository it will become clear why it has to be done that
way.
l.