||This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. (April 2009)|
|Original author(s)||James Tauber, Google|
|Developer(s)||Luke Leighton, Anthony C Risinger, Kees Bos|
|Initial release||March 2007|
|Stable release||0.8.1a / May 6, 2012|
|Operating system||Windows, Mac OS X, Linux|
|Type||Ajax framework, Desktop and Web Widget toolkit, Compiler, Widget set|
|License||Apache License 2.0|
Furthermore, on top of the DOM.py model library is an additional abstraction layer, ui.py, which provides the most useful layer to web developers: a full suite of widgets with which desktop application developers will be familiar. At present, the list of available widgets is a mixture of the complete set of widgets that were available in Google Web Toolkit 1.2, along with a few more that have been forward-ported from GWT 1.5.
The major Pyjamas components include:
- Python builtin and standard emulation library
- Pyjamas DOM library
- Modules for manipulating the browser DOM.
- Pyjamas Web UI module
- A module for creating widgets as if the web browser was a Desktop Widget Engine.
- Pyjamas Desktop ports
- Support for running Pyjamas apps as pure Python, under MSHTML, XULRunner or Webkit. Pyjamas Desktop is conceptually close to GWT "Hosted" mode, except that the applications can be deployed live, under Pyjamas Desktop, rather than be used exclusively as a debugging tool.
The widget set library that comes with Pyjamas is so similar to PyQt and PyGTK that a port of Pyjamas was made to run Pyjamas applications on the desktop, called Pyjamas-Desktop. The project uses Webkit, XULRunner or MSHTML as the underlying technology, and it is through these browser engines that Pyjamas manipulates the DOM model of the application. Pyjamas and Pyjamas Desktop allow writing cross-platform, cross-desktop, cross-browser and cross-widget applications that run on the web and on the desktop.
||This section is written like a personal reflection or opinion essay that states the Wikipedia editor's particular feelings about a topic, rather than the opinions of experts. (February 2014)|
On May 2, 2012 the leadership roles of the project came into question. This was a community driven open source project that was extensively developed by many contributors including the people mentioned above. Due to disagreements between members of the group on how to move forward with the infrastructure and direction of the software, some members decided to create their own fork of the pyjamas project. This fork was created by a team led by Anthony Risinger, one of the administrators of the project. This group included the person who owned the pyjs.org domain and he voluntarily decided to assign ownership of the domain to this new fork being created and hence became the new pyjs.org fork of the pyjamas project. Luke Leighton continued his work on his own fork through a new domain pyj.be and continues to develop and maintain pyjamas on this pyj.be fork.
This still left a controversy over the copying of the mailing list data from the old server to create the new mailing list of google groups. This was raised as a violation of the UK Data Protection Act by Luke Leighton. Whether this was actually a legal violation is not really clear and is open to interpretation. This was a community driven open source project. According to many in the community [weasel words], both Luke and Anthony were co-administrators of the project and co-leads to it. It was being forked by a team including Anthony, one of the administrators who had privileges for the server, which Luke Leighton owned. The mailing list was part of the domain. So the ownership of the mailing list data itself isn't very clear. Though Luke claims he personally owned the mailing list and that using it to create a new mailing list for the new pyjs.org fork of the project constituted stealing, many in the community [weasel words] feel differently. Many feel [weasel words] that this was an open source community project and Luke Leighton was a co-lead and co-administrator. Hence the mailing list was actually a community property of the pyjs.org community and not the personal property of Luke. Thus, though some disagree, in the opinion of many in the community [weasel words], using it to create the new google groups was legal.
Even though the ownership of the mailing list data is not entirely clear, when some members complained about being subscribed to the new google groups mailing list, immediate action was taken by the maintainers of the new pyjs.org fork to remove everyone from the new google groups and invited all the members to voluntarily join the new google groups. This being exactly the same approach that Luke Leighton took when he decided to move the pyjamas mailing list from google groups where it was originally created before Luke Leighton took over leadership of the project.
The current membership of the google groups owned and maintained by both forks of the original pyjs.org is now voluntary, created through invitation, and does not violate any privacy and data protection laws. There are no unresolved legal issues at this time nor any pending lawsuits with either forks of the pyjamas project.
Both forks are being actively developed and have formed their own community following.
The Pyjs.org fork has gone through active development
- New github based infrastructure
- Travis-CI based continuous integration for both build, install and automated testing.
- PIP install and VirtualEnv based development environment.
- Separation of pyjs tools from pyjs gwt widgets. To allow other widgets sets to be developed.
- Builtin Closure compiler integration
- GI Introspection/WebKit-GTK based pyjs-desktop runner
Pyj.be continues to be maintained by Luke Leighton and is still active with bug fixes and new development.
Most alternatives to Pyjamas are translators rather than frameworks.
- Pyjamas Home
- PyXPCOMExt Hulahop Tutorial
- Rick Hightower's IBM Developerworks Tutorial
- Slashdot article
- lwn.net article