Differences between revisions 55 and 57 (spanning 2 versions)
Revision 55 as of 2012-11-25 03:48:54
Size: 12564
Editor: CzarekTomczak
Comment: wiki restore 2013-01-23
Revision 57 as of 2013-02-28 23:51:50
Size: 12412
Editor: DanStromberg
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 3: Line 2:





Line 10: Line 3:
Line 14: Line 6:
Line 17: Line 8:

* ActiveScripting (PythonScript), included in [[PyWin32|PyWin32]]
 * ActiveScripting (PythonScript), included in PyWin32
Line 21: Line 11:

TODO: Add mention of IPython Notebook which can be run remotely, easily on AWS, and used within your browser. The HTML client can also interact with [[JavaScript|JavaScript]] and DOM, though this feature isn't quite merged yet. There's a lot being done on it, but it's already being used and probably should be mentioned here.


TODO: Add mention of IPython Notebook which can be run remotely, easily on AWS, and used within your browser. The HTML client can also interact with JavaScript and DOM, though this feature isn't quite merged yet. There's a lot being done on it, but it's already being used and probably should be mentioned here.
Line 29: Line 15:
Line 32: Line 17:

* Specifically excluded from the list is technology that simply generates static HTML content. So, an HTML pretty-printer library, as the resultant HTML simply uses the browser for "display" purposes rather than using the browser as an "application execution environment", is out. Such technologies can instead be found at [[WebClientProgramming|WebClientProgramming]].
 * Plugins for Web Browsers that provide direct access to the DOM model of the web browser. In exactly the same way that most web browsers have JavaScript by default as a language that can directly access the DOM model of the web browser, a plugin or other system that can do the same thing (with Python using `<script type="text/python" />` instead of JavaScript using `<script language="javascript" />`) should be listed on this page.
 * Specifically excluded from the list is technology that simply generates static HTML content. So, an HTML pretty-printer library, as the resultant HTML simply uses the browser for "display" purposes rather than using the browser as an "application execution environment", is out. Such technologies can instead be found at WebClientProgramming.
 * Plugins for Web Browsers that provide direct access to the DOM model of the web browser. In exactly the same way that most web browsers have JavaScript by default as a language that can directly access the DOM model of the web browser, a plugin or other system that can do the same thing (with Python using `<script type="text/python" />` instead of JavaScript using `<script language="javascript" />`) should be listed on this page.
Line 38: Line 22:
Line 41: Line 24:
Line 43: Line 25:

Line 47: Line 27:
Line 49: Line 28:
 * [[Pyjamas|Pyjamas]] is a Python-to-JavaScript compiler and AJAX-based Web Toolkit and Framework that allows users to write code in standard Python that will be run in a web browser, after translation to JavaScript. pyjs - the compiler - can also be used as a stand-alone JavaScript compiler. There are three main modes: --strict, providing as close to full strict python compatibility and interoperability as is both possible and has been contributed so far (which is quite a lot); -O, providing a subset of python functionality and providing much faster performance as a result; --stupid-mode which falls back to javascript for certain operations, with the result that the output is much easier to read and to compare to the original python from which it was generated, but runs the risk of changing the meaning of the python application and requiring a deep understanding of how javascript operates (stupidly - hence the name of the mode).  * [[Pyjamas]] is a Python-to-JavaScript compiler and AJAX-based Web Toolkit and Framework that allows users to write code in standard Python that will be run in a web browser, after translation to JavaScript. pyjs - the compiler - can also be used as a stand-alone JavaScript compiler. There are three main modes: --strict, providing as close to full strict python compatibility and interoperability as is both possible and has been contributed so far (which is quite a lot); -O, providing a subset of python functionality and providing much faster performance as a result; --stupid-mode which falls back to javascript for certain operations, with the result that the output is much easier to read and to compare to the original python from which it was generated, but runs the risk of changing the meaning of the python application and requiring a deep understanding of how javascript operates (stupidly - hence the name of the mode).
Line 51: Line 30:
 * [[Py2Js|Py2Js]] is an unmaintained project that can still be downloaded [[http://davidf.sjsoft.com/files/py2js|here]]. It is purely a Python-to-JavaScript compiler/translator.  * Py2Js is an unmaintained project that can still be downloaded [[http://davidf.sjsoft.com/files/py2js|here]]. It is purely a Python-to-JavaScript compiler/translator.
Line 54: Line 33:
 * [[http://fiddlesalad.com/python/|Fiddle Salad]] is a web development IDE with HTML and CSS that compiles Python to [[JavaScript|JavaScript]]
 * [[http://fiddlesalad.com/python/|Fiddle Salad]] is a web development IDE with HTML and CSS that compiles Python to JavaScript
Line 58: Line 36:

Line 62: Line 38:

* PyXPComExt has the full Python interpreter embedded. [[http://pyxpcomext.mozdev.org/|PyXPCOMExt]] is the interpreter as a XULRunner extension; [[http://developer.mozilla.org/en/PyDOM|PyDOM]] is a library that will almost certainly be needed, that allows you to manipulate the browser's DOM model using Python. The API is (almost) identical to that of JavaScript. Effectively, where browsers have built-in support for `lang="javascript"`, PyXPComExt adds `<script lang="python"> .... </script>` to Firefox.
 * AppCelerator's [[http://www.appcelerator.com/appcelerator-platform/titanium-architecture/|Titanium]] provides support for `<script type="text/python"> ... </script>`, using [[IronPython|IronPython]] and Silverlight.
 * [[http://ironpython.net/browser/|Ironpython]]
by itself also provides support for `<script type="text/python"> ... </script>`.
 * PyXPComExt has the full Python interpreter embedded. [[http://pyxpcomext.mozdev.org/|PyXPCOMExt]] is the interpreter as a XULRunner extension; [[http://developer.mozilla.org/en/PyDOM|PyDOM]] is a library that will almost certainly be needed, that allows you to manipulate the browser's DOM model using Python. The API is (almost) identical to that of JavaScript. Effectively, where browsers have built-in support for `lang="javascript"`, PyXPComExt adds `<script lang="python"> .... </script>` to Firefox.
 * AppCelerator's [[http://www.appcelerator.com/appcelerator-platform/titanium-architecture/|Titanium]] provides support for `<script type="text/python"> ... </script>`, using IronPython and Silverlight.
 *
[[http://ironpython.net/browser/|Ironpython]] by itself also provides support for `<script type="text/python"> ... </script>`.
Line 67: Line 42:
 * [[http://brython.info/index.html|Brython]] is a Python 3 implementation that runs in a browser, providing <script type="text/python">...</script>.
Line 70: Line 45:

Line 74: Line 47:
Line 76: Line 48:
 * [[PythonWebKit|PythonWebKit]] - [[http://www.gnu.org/software/pythonwebkit|PythonWebKit]] is a Python wrapper around [[http://webkit.org|Webkit]] that provides direct access to the DOM model. PyWebKitGtk has been incorporated into the build, rather than being built separately. Unlike the patched version of PyWebKitGtk, [[PythonWebKit|PythonWebKit]] does not go via gobject to access DOM functions but instead calls the Webkit DOM functions direct.
 * PyWebKitGtk - [[http://code.google.com/p/pywebkitgtk|PyWebkitGtk]] is a Python wrapper around [[http://webkit.org|Webkit]] that embeds the Webkit "engine" as a GTK widget. The standard version of PyWebKitGtk is unable to provide access to the DOM model, treating pywebkit as a hands-off widget that can be used to write your own Web Browser (see demobrowser.py). However, a [[https://bugs.webkit.org/show_bug.cgi?id=16401|patch to webkit]] and a corresponding patch to PyWebKitGtk will soon bring DOM model manipulation to python: see [[PyjamasDesktop|PyjamasDesktop]] for details.
 * PythonWebKit - [[http://www.gnu.org/software/pythonwebkit|PythonWebKit]] is a Python wrapper around [[http://webkit.org|Webkit]] that provides direct access to the DOM model. PyWebKitGtk has been incorporated into the build, rather than being built separately. Unlike the patched version of PyWebKitGtk, PythonWebKit does not go via gobject to access DOM functions but instead calls the Webkit DOM functions direct.
 * PyWebKitGtk - [[http://code.google.com/p/pywebkitgtk|PyWebkitGtk]] is a Python wrapper around [[http://webkit.org|Webkit]] that embeds the Webkit "engine" as a GTK widget. The standard version of PyWebKitGtk is unable to provide access to the DOM model, treating pywebkit as a hands-off widget that can be used to write your own Web Browser (see demobrowser.py). However, a [[https://bugs.webkit.org/show_bug.cgi?id=16401|patch to webkit]] and a corresponding patch to PyWebKitGtk will soon bring DOM model manipulation to python: see PyjamasDesktop for details.
Line 81: Line 53:
 * [[http://wiki.laptop.org/go/HulaHop|HulaHop]] provides Python access to DOM model manipulation - via XUL/Gecko Interfaces. HulaHop is part of the OLPC Sugar Project, but is available stand-alone. It depends on python-xpcom (part of XULRunner). [[HulaHop|HulaHop]] is being removed from Sugar and being replaced by [[WebKit|WebKit]].
 * [[PyWin32|PyWin32]] comtypes can be used (with care!) to create an MSHTML IWebBrowser2 ActiveX window and thus provide access to the full DOM features of the MSHTML (Trident) engine. [[PyjamasDesktop|PyjamasDesktop]] uses this technique to create the [[http://pyjamas.svn.sourceforge.net/viewvc/pyjamas/trunk/pyjd/mshtml.py|mshtml.py]] port. Note that creation and use of `XMLHttpRequest` is also shown in [[PyjamasDesktop|PyjamasDesktop]]'s `mshtml.py`.
 * [[http://wiki.laptop.org/go/HulaHop|HulaHop]] provides Python access to DOM model manipulation - via XUL/Gecko Interfaces. HulaHop is part of the OLPC Sugar Project, but is available stand-alone. It depends on python-xpcom (part of XULRunner). HulaHop is being removed from Sugar and being replaced by WebKit.
 * PyWin32 comtypes can be used (with care!) to create an MSHTML IWebBrowser2 ActiveX window and thus provide access to the full DOM features of the MSHTML (Trident) engine. PyjamasDesktop uses this technique to create the [[http://pyjamas.svn.sourceforge.net/viewvc/pyjamas/trunk/pyjd/mshtml.py|mshtml.py]] port. Note that creation and use of `XMLHttpRequest` is also shown in PyjamasDesktop's `mshtml.py`.
Line 85: Line 57:
Line 87: Line 58:

Line 90: Line 59:

Web Browser Programming in Python

TODO: merge in and research these, found on comp.lang.python

Yes, Python can do it... on Windows.

Two (examples) ways:

TODO: Add mention of IPython Notebook which can be run remotely, easily on AWS, and used within your browser. The HTML client can also interact with JavaScript and DOM, though this feature isn't quite merged yet. There's a lot being done on it, but it's already being used and probably should be mentioned here.

This topic covers ways in which python can be used in web browsers to control, create or manipulate the content within a user's web browser, or a web-based technology (such as WebKit, the technology behind Safari, Midori, the OLPC Browser, Adobe AIR, Google Chrome and much more; XULrunner (the engine behind Firefox and much more); MSHTML (the engine behind IE and much more); and KDE's KHTMLPart.

To clarify what type of technology goes onto this page, some examples of types of technology that can and cannot be added to this section:

  • Specifically excluded from the list is technology that simply generates static HTML content. So, an HTML pretty-printer library, as the resultant HTML simply uses the browser for "display" purposes rather than using the browser as an "application execution environment", is out. Such technologies can instead be found at WebClientProgramming.

  • Plugins for Web Browsers that provide direct access to the DOM model of the web browser. In exactly the same way that most web browsers have JavaScript by default as a language that can directly access the DOM model of the web browser, a plugin or other system that can do the same thing (with Python using <script type="text/python" /> instead of JavaScript using <script language="javascript" />) should be listed on this page.

  • Python-based technology that auto-generates or compiles JavaScript definitely counts, as the resultant JavaScript would be executed by the web browser.

  • Technology that simply uses JavaScript or depends on JavaScript libraries (such as mochikit, extjs or prototype) does not count, but a Python-based wrapper library around a JavaScript engine definitely counts.

This latter example requires some further explanation: Pyjamas, for example, is a Python-to-JavaScript compiler that can include inline JavaScript. So, although the input to Pyjamas is part Python, part JavaScript, the output is pure JavaScript that runs in a web browser, and so any such "mixed" language libraries should be included on this page.

Python-to-JavaScript Compilers

These are tools that convert Python into JavaScript, that can then be run either stand-alone, using technology such as Spidermonkey, Google's V8 engine (for example, using pyv8), or in a web browser (where, in order to be useful, the applications must of course interface with the DOM model of the browser, typically using an AJAX library).

  • Pyjaco, the Python-to-Javascript Compiler is a python-based compiler that will compile most python code into fairly compact javascript. It uses a small (~60KB) standard library to implement all the usual python types like list, dict, int, bool, etc. It supports classes, inheritance, keyword and variable arguments, and much more. It has a comprehensive test suite, and aims to be the most fun and efficient way to create web applications with Python.

  • Pyjamas is a Python-to-JavaScript compiler and AJAX-based Web Toolkit and Framework that allows users to write code in standard Python that will be run in a web browser, after translation to JavaScript. pyjs - the compiler - can also be used as a stand-alone JavaScript compiler. There are three main modes: --strict, providing as close to full strict python compatibility and interoperability as is both possible and has been contributed so far (which is quite a lot); -O, providing a subset of python functionality and providing much faster performance as a result; --stupid-mode which falls back to javascript for certain operations, with the result that the output is much easier to read and to compare to the original python from which it was generated, but runs the risk of changing the meaning of the python application and requiring a deep understanding of how javascript operates (stupidly - hence the name of the mode).

  • Skulpt is a Python-to-JavaScript compiler that is focussing on providing (only) full Python syntax. The demo includes a Python interpreter prompt, which is actually running in the user's web browser, not on a server, as pure JavaScript.

  • Py2Js is an unmaintained project that can still be downloaded here. It is purely a Python-to-JavaScript compiler/translator.

  • Py2js is a maintained project that provides a Python-to-JavaScript compiler.

  • PyCow is an unmaintained project to translate Python code to Javascript with Mootools

  • Fiddle Salad is a web development IDE with HTML and CSS that compiles Python to JavaScript

Embedding Python inside Web Browsers

This section describes projects where a Python interpreter itself has been embedded into the web browser. Instead of downloading the standard Python executable and libraries, these projects come with the CPython runtime and libraries pre-embedded (and, as such, are typically very large downloads).

  • PyXPComExt has the full Python interpreter embedded. PyXPCOMExt is the interpreter as a XULRunner extension; PyDOM is a library that will almost certainly be needed, that allows you to manipulate the browser's DOM model using Python. The API is (almost) identical to that of JavaScript. Effectively, where browsers have built-in support for lang="javascript", PyXPComExt adds <script lang="python"> .... </script> to Firefox.

  • AppCelerator's Titanium provides support for <script type="text/python"> ... </script>, using IronPython and Silverlight.

  • Ironpython by itself also provides support for <script type="text/python"> ... </script>.

  • Firebreath is an NPAPI plugin that extends access to the full features of DOM programming out to other programming languages, including python.

  • Brython is a Python 3 implementation that runs in a browser, providing <script type="text/python">...</script>.

Python Wrappers around Web "Libraries" and Browser Technology

This section describes projects where you can (or have to) create your own web browser application in Python. It includes web browser "engines" that have Python interfaces to access, control and present web pages and web-relevant rich media content (such as Adobe Flash).

  • CefPython provides python bindings for the Google Chrome browser by using Chromium Embedded Framework, a web browser control based on the Chromium project.

  • PythonWebKit - PythonWebKit is a Python wrapper around Webkit that provides direct access to the DOM model. PyWebKitGtk has been incorporated into the build, rather than being built separately. Unlike the patched version of PyWebKitGtk, PythonWebKit does not go via gobject to access DOM functions but instead calls the Webkit DOM functions direct.

  • PyWebKitGtk - PyWebkitGtk is a Python wrapper around Webkit that embeds the Webkit "engine" as a GTK widget. The standard version of PyWebKitGtk is unable to provide access to the DOM model, treating pywebkit as a hands-off widget that can be used to write your own Web Browser (see demobrowser.py). However, a patch to webkit and a corresponding patch to PyWebKitGtk will soon bring DOM model manipulation to python: see PyjamasDesktop for details.

  • PyWebkitQt4 is a python wrapper again around Webkit but this time as a Qt4 widget. An extremely limited subset of bindings to the DOM model have been added to PyWebkitQt4, along with the means to execute JavaScript code snippets. Whilst in principle this sounds like a fantastic idea, in practice it is insane to work with, especially for event callbacks and for anything beyond the most absolute and basic DOM manipulation. PyWebkitQt4 is best avoided for significant DOM manipulation, or is best treated as nothing more than a means to display HTML (and other web-based media such as Flash and Java applications).

  • PyKDE - KDE contains Python bindings to KHTMLPart (which is very similar to Webkit). This allows you to embed HTML into an application window. The Python bindings to the DOM model are slightly... obtuse. to say the least, and PyKHTML - PyKHTML makes them much more tolerable (see dom.py). However, there are limitations in PyKDE's DOM bindings (that many people will never encounter) that you should investigate thoroughly before utilising PyKDE for seriously heavy-duty DOM model manipulation. To avoid those limitations you should ensure that the entire KDE platform is compiled with C++ RTTI enabled (it is typically disabled by most distributions, by default).

  • WebKit with the Objective-C bindings (MacOS X users only). Webkit itself has Objective-C bindings, on MacOS X. MacOS X's Objective-C technology comes with automatic bindings to all major programming languages, including Python (using pyobjc). Consequently, you can directly manipulate the DOM model from Python. However, unlike the use of MSHTML, and unlike XULrunner and the patched version of WebKit, the Objective-C WebKit bindings are limited to just the DOM model, and are limited to strict accordance with the W3C standards (rather than the de-facto standards defined by real-world JavaScript usage). So, for example, XMLHttpRequest is not included in the Objective-C bindings (whereas it is in XULRunner); and the embed element takes width and height strictly as integers, rather than accepting 100px and stripping off px.

  • HulaHop provides Python access to DOM model manipulation - via XUL/Gecko Interfaces. HulaHop is part of the OLPC Sugar Project, but is available stand-alone. It depends on python-xpcom (part of XULRunner). HulaHop is being removed from Sugar and being replaced by WebKit.

  • PyWin32 comtypes can be used (with care!) to create an MSHTML IWebBrowser2 ActiveX window and thus provide access to the full DOM features of the MSHTML (Trident) engine. PyjamasDesktop uses this technique to create the mshtml.py port. Note that creation and use of XMLHttpRequest is also shown in PyjamasDesktop's mshtml.py.

  • python-wxWebKit is beginning to provide Python access to DOM model manipulation - via python bindings that are auto-generated using SWIG. The goal of the project is to provide full access to the entire DOM model, and this goal is, as of May 2011, approximately 25% completed.

Python Wrappers around Web Browser "Test Suite" Libraries

This section describes projects where you can test web applications, initiated from the command-line with python bindings.

  • Selenium, the browser test suite, has python bindings: Install HOWTO. Selenium is a suite of tools to automate web app testing across many platforms.

  • Windmill is a web testing tool designed to let you painlessly automate and debug your web application. Like selenium, it also has Python bindings.

WebBrowserProgramming (last edited 2022-05-08 08:36:36 by Olivier Pirson)

Unable to edit the page? See the FrontPage for instructions.