Pyjs: Difference between revisions

Pyjs
Original author(s)	James Tauber, Google
Developer(s)	Luke Leighton, Anthony C Risinger, Kees Bos
Initial release	March 2007; 17 years ago
Stable release	0.8.1a / 9 May 2012; 12 years ago
Repository	github.com/pyjs/pyjs ;
Written in	Python, JavaScript
Operating system	Windows, OS X, Linux
Available in	Python
Type	Ajax framework, Desktop and Web Widget toolkit, Compiler, Widget set
License	Apache License 2.0
Website	pyjs.org

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Inline

Latest revision as of 22:49, 30 April 2024

Pyjs (formerly Pyjamas before May 2012^[2]), is a rich web application framework for developing client-side web and desktop applications in Python. The resulting applications can be run in a web browser or as standalone desktop applications.

It contains a stand-alone Python-to-JavaScript compiler, an Ajax framework and widget toolkit, and through use of these components, developers can write comprehensive applications, to run in all major web browsers, without writing any JavaScript. Pyjs is a port of Google Web Toolkit (GWT) from Java to Python.^[3]

Development

Using pyjs, developers can write web applications in Python instead of JavaScript. The application is compiled to JavaScript. Also included is an Ajax library and widget set^[4] that provides access to the Document Object Model (DOM) of modern JavaScript-capable web browsers. The Ajax library and the widget set library are a hybrid mix of Python and JavaScript. Just as with Google Web Toolkit, pyjs is not its libraries, and neither is it just another Ajax framework. Ajax frameworks are strictly limited to providing pre-prepared specific functionality, written almost exclusively in tailor-made JavaScript. Both GWT and pyjs, being JavaScript compilers, allow the developer to work in the language with which they are familiar (Java or Python, respectively), to write their own custom widgets, either entirely from scratch or based on the existing available widgets, yet still target the full range of modern browsers. So, far from presenting web developers with a ready-made Ajax framework, pyjs gives you the freedom to create your own.

Design

The pyjs compiler is written in the programming language Python, and uses it to compile its input into JavaScript, walking the abstract syntax tree of the program being compiled. Although the compiler is stand-alone, the primary use of pyjs is for web development, so there is additional infrastructure for building web applications.

The DOM.py^[5] model library is an abstraction layer — a thin layer of Python on top of JavaScript code snippets — use of which provides access to the full Document Object Model of the target browser platform. As with any compiler, the JavaScript snippets are treated as inline assembler.

Furthermore, on top of the DOM.py model library is an additional abstraction layer, ui.py,^[6] 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.

Components

The major Pyjs components include:

pyjs Python-to-JavaScript Compiler: Translates the programming language Python into JavaScript.
Python builtin and standard emulation library: JavaScript implementations of the commonly used modules, builtins and classes in the Python standard runtime library (such as strings, lists, dictionaries, tuples, sets, getattr, map, filter, range, etc.; basic exception handling, a basic datetime and a basic math module).
pyjs DOM library^[5]: Modules for manipulating the browser DOM.
pyjs Web UI module^[6]: A module for creating widgets as if the web browser was a desktop widget engine.
pyjs Desktop ports: Support for running pyjs apps as pure Python, under MSHTML (Trident), Gecko (XULRunner) or WebKit. Pyjs Desktop is conceptually close to GWT "Hosted" mode, except that the applications can be deployed live, under pyjs Desktop, rather than be used exclusively as a debugging tool.

pyjs Desktop

The widget set library^[4] that comes with pyjs is so similar to PyQt and PyGTK that a port of pyjs was made to run pyjs applications on the desktop, called pyjs Desktop (formerly PyjamasDesktop^[7] before May 2012 and originally hosted separately prior to version 0.6^[8]). The project uses Webkit, XULRunner or MSHTML as the underlying technology, and it is through these browser engines that pyjs manipulates the DOM model of the application. Together pyjs and pyjs Desktop allow writing cross-platform, cross-desktop, cross-browser and cross-widget applications that run on the web and on the desktop.^[9]^[10]

References

^ "Release 0.8.1a". 9 May 2012. Retrieved 22 July 2018.
^ Infrastructure, endpoint, process changes, clarification by Lex on pyjamas-dev mailing list (May 03, 2012)
^ pyjs README
^ ^a ^b The ui Module Class Hierarchy
^ ^a ^b DOM module
^ ^a ^b ui module
^ PyjamasDesktop history, Python Wiki
^ "Pyjamas Desktop".
^ Pyjamas - Python Applications for Desktop and Web, Luke Kenneth Casson Leighton (August 30, 2008)
^ Coding in Pyjamas: Apps for Desktop and the Web Luke Kenneth Casson Leighton (November 7, 2008)

External links

Pyjs Home

[wikidata-432664666f51f89a91160c8da36e76d1e3274e30-v18-1] "Release 0.8.1a". 9 May 2012. Retrieved 22 July 2018.

[2] Infrastructure, endpoint, process changes, clarification by Lex on pyjamas-dev mailing list (May 03, 2012)

[AtGoogle-3] yjs README

[widgetset-4] The ui Module Class Hierarchy

[dommodule-5] DOM module

[uimodule-6] ui module

[7] PyjamasDesktop history, Python Wiki

[8] "Pyjamas Desktop".

[9] Pyjamas - Python Applications for Desktop and Web, Luke Kenneth Casson Leighton (August 30, 2008)

[Linux2008Pyjamas1-10] Coding in Pyjamas: Apps for Desktop and the Web Luke Kenneth Casson Leighton (November 7, 2008)

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

@@ Line 1: / Line 1: @@
+{{Short description|Rich Internet application framework}}
+{{Multiple issues|
 {{More footnotes|date=April 2009}}
+{{Notability|1=Products|date=January 2021}}
+{{Primary sources|date=January 2021}}
+}}
 {{Infobox software
 | name                   = Pyjs
-| logo                   = Pyjs-logo.png
+| logo                   = Pyjs-logo.svg
 | logo size              = 192px
-| logo alt               = New logo of the Pyjs project (aka Pyjamas), after forking off in 2012.
+| logo alt               = Logo of the Pyjs project (aka Pyjamas), after forking off in 2012.
 | screenshot             =
 | caption                =
@@ Line 10: / Line 15: @@
 | developer              = Luke Leighton, Anthony C Risinger, Kees Bos
 | released               = {{Start date and age|2007|03}}
-| latest release version = 0.8.1a
+| latest release version = {{wikidata|property|reference|edit|P348}}
-| latest release date    = {{Start date and age|2012|05|06}}
+| latest release date    = {{start date and age|{{wikidata|qualifier|P348|P577}}}}
 | latest preview version =
 | latest preview date    =
@@ Line 18: / Line 23: @@
 | platform               =
 | language               = [[Python (programming language)|Python]]
-| status                 = Stalled
 | genre                  = [[Ajax framework]], Desktop and Web [[Widget toolkit]], [[Compiler]], [[Widget set]]
 | license                = [[Apache License 2.0]]
 | website                = {{URL|pyjs.org}}
 }}
-'''Pyjs''' (formerly '''Pyjamas''' before May 2012<ref>[https://groups.google.com/d/msg/pyjamas-dev/3NZ0No2hLUw/EoiTk6fK-O8J Infrastructure, endpoint, process changes], clarification by Lex on pyjamas-dev mailing list (May 03, 2012)</ref>), is a [[rich Internet application]] framework for developing client-side web and desktop applications in [[Python (programming language)|Python]]. The resulting applications can be run in a [[web browser]] or as standalone [[desktop application]]s.
+'''Pyjs''' (formerly '''Pyjamas''' before May 2012<ref>[https://groups.google.com/d/msg/pyjamas-dev/3NZ0No2hLUw/EoiTk6fK-O8J Infrastructure, endpoint, process changes], clarification by Lex on pyjamas-dev mailing list (May 03, 2012)</ref>), is a [[rich web application]] framework for developing client-side web and desktop applications in [[Python (programming language)|Python]]. The resulting applications can be run in a [[web browser]] or as standalone [[desktop application]]s.
 It contains a stand-alone [[Python (programming language)|Python]]-to-[[JavaScript]] compiler, an [[Ajax framework]] and [[widget toolkit]], and through use of these components, developers can write comprehensive applications, to run in all major web browsers, without writing any JavaScript. Pyjs is a port of [[Google Web Toolkit]] (GWT) from [[Java (programming language)|Java]] to [[Python (programming language)|Python]].<ref name=AtGoogle>[https://github.com/pyjs/pyjs/blob/master/README.rst pyjs README]</ref>
 ==Development==
-Using pyjs, developers can write [[web application]]s in [[Python (programming language)|Python]] instead of [[JavaScript]]. The application is compiled to JavaScript. Also included is an Ajax library and widget set<ref name="widgetset">[http://pyjs.org/UIHierarchy.html The ui Module Class Hierarchy]</ref> that provides access to the [[Document Object Model|Document Object Model (DOM)]] of modern JavaScript-capable web browsers. The Ajax library and the widget set library are a hybrid mix of Python and JavaScript. Just as with Google Web Toolkit, pyjs is not its libraries, and neither is it just another Ajax framework. [[Ajax framework]]s are strictly limited to providing pre-prepared specific functionality, written almost exclusively in tailor-made JavaScript. Both GWT and pyjs, being JavaScript compilers, allow the developer to work in the language with which they are familiar (Java or Python, respectively), to write their own custom widgets, either entirely from scratch or based on the existing available widgets, yet still target the full range of modern browsers. So, far from presenting web developers with a ''fait-accompli'' Ajax framework, pyjs gives you the freedom to develop your own.
+Using pyjs, developers can write [[web application]]s in [[Python (programming language)|Python]] instead of [[JavaScript]]. The application is compiled to JavaScript. Also included is an Ajax library and widget set<ref name="widgetset">[http://pyjs.org/UIHierarchy.html The ui Module Class Hierarchy]</ref> that provides access to the [[Document Object Model|Document Object Model (DOM)]] of modern JavaScript-capable web browsers. The Ajax library and the widget set library are a hybrid mix of Python and JavaScript. Just as with Google Web Toolkit, pyjs is not its libraries, and neither is it just another Ajax framework. [[Ajax framework]]s are strictly limited to providing pre-prepared specific functionality, written almost exclusively in tailor-made JavaScript. Both GWT and pyjs, being JavaScript compilers, allow the developer to work in the language with which they are familiar (Java or Python, respectively), to write their own custom widgets, either entirely from scratch or based on the existing available widgets, yet still target the full range of modern browsers. So, far from presenting web developers with a ready-made Ajax framework, pyjs gives you the freedom to create your own.
 ==Design==
 The pyjs compiler is written in the programming language Python, and uses it to compile its input into JavaScript, walking the [[abstract syntax tree]] of the program being compiled. Although the compiler is stand-alone, the primary use of pyjs is for web development, so there is additional infrastructure for building web applications.
-The DOM.py<ref name="dommodule" /> model library is an abstraction layer - a thin layer of Python on top of JavaScript code snippets - use of which provides access to the full [[Document Object Model]] of the target browser platform. As with any compiler, the JavaScript snippets are treated as [[inline assembler]].
+The DOM.py<ref name="dommodule" /> model library is an abstraction layer — a thin layer of Python on top of JavaScript code snippets — use of which provides access to the full [[Document Object Model]] of the target browser platform. As with any compiler, the JavaScript snippets are treated as [[inline assembler]].
 Furthermore, on top of the DOM.py model library is an additional abstraction layer, ui.py,<ref name="uimodule" /> which provides the most useful layer to web developers: a full suite of [[GUI widget|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.
@@ Line 48: / Line 52: @@
 :A module for creating [[GUI widget|widget]]s as if the web browser was a desktop [[widget engine]].
 ;pyjs Desktop ports
-:Support for running pyjs apps as pure Python, under [[Trident (layout engine)|Trident]] (MSHTML), [[Gecko (software)|Gecko]] ([[XULRunner]]) or [[WebKit]]. Pyjs Desktop is conceptually close to GWT "Hosted" mode, except that the applications can be deployed live, under pyjs Desktop, rather than be used exclusively as a debugging tool.
+:Support for running pyjs apps as pure Python, under [[MSHTML]] (Trident), [[Gecko (software)|Gecko]] ([[XULRunner]]) or [[WebKit]]. Pyjs Desktop is conceptually close to GWT "Hosted" mode, except that the applications can be deployed live, under pyjs Desktop, rather than be used exclusively as a debugging tool.
 ==''pyjs Desktop''==
 The widget set library<ref name="widgetset"/> that comes with pyjs is so similar to [[PyQt]] and [[PyGTK]] that a port of pyjs was made to run pyjs applications on the desktop, called ''pyjs Desktop'' (formerly ''PyjamasDesktop''<ref>[https://wiki.python.org/moin/PyjamasDesktop PyjamasDesktop history], Python Wiki</ref> before May 2012 and originally hosted separately prior to version 0.6<ref>{{cite web |title=Pyjamas Desktop |url=http://pyjd.sourceforge.net/}}</ref>). The project uses [[Webkit]], [[XULRunner]] or [[MSHTML]] as the underlying technology, and it is through these browser engines that pyjs manipulates the DOM model of the application. Together pyjs and pyjs Desktop allow writing cross-platform, cross-desktop, cross-browser and cross-widget applications that run on the web and on the desktop.<ref>[http://advogato.org/article/981.html Pyjamas - Python Applications for Desktop and Web], Luke Kenneth Casson Leighton (August 30, 2008)</ref><ref name=Linux2008Pyjamas1>[http://www.ukuug.org/events/linux2008/programme/abstract-LKCLeighton-1.shtml Coding in Pyjamas: Apps for Desktop and the Web] Luke Kenneth Casson Leighton (November 7, 2008)</ref>
-==History==
-{{essay-like|section|date=February 2014}}
-Pyjamas was started by James Tauber as a port of the UI Widget Set and the DOM support libraries from Google Web Toolkit to the [[Python (programming language)|Python language]]. Tauber then wrote the original pyjs compiler.
-In 2008, Luke Leighton took over the project, updated the UI Widget Set, improved the compiler and created the three pyjs Desktop runtimes.
-Bernd Dorn and his colleagues from Lovely Systems did some dramatic compiler improvements released in version 0.5. Kees Bos is responsible for the majority of improvements and the enhanced Python interoperability in the compiler, such as the ''yield'' keyword support and long data types. C Anthony Risinger also joined as lead and administrator of the project.
-In 2012, the project was driven by an extensive community, but on May 2, due to disagreements between project leaders, some members created a pyjamas fork. This new team created pyjs.org, led by Anthony Risinger and including the person who owned the domain. Meanwhile, Luke Leighton continued his work on his own fork through a new domain pyj.be and continues to develop and maintain pyjamas on this branch.
-There was 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 inline|date=February 2014}}, 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 inline|date=February 2014}} feel differently.  Many feel{{weasel inline|date=February 2014}} 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.
-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 Leighton took when he decided to move the pyjamas mailing list from google groups where it was originally created before 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 were actively developed and had formed their own community following.{{update-inline|date=July 2017}}
-==Forks==
-There were two forks of the Pyjamas/Pyjs project: one maintained by the new Pyjs team and another maintained by Luke Leighton.
-===Pyjs.org===
-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 (package manager)|pip]] install and VirtualEnv based development environment
-* Separation of pyjs tools from pyjs GWT widgets to allow other widgets sets to be developed
-* Built-in Closure compiler integration
-* GI Introspection/WebKit-GTK based pyjs-desktop runner
-===Pyj.be===
-Pyj.be, continued to be maintained by Luke Leighton and was still active with bug fixes and new development. As of early 2015, however, the website is not available anymore.
-==Critics==
-Pyjamas has been criticized by heavy users for several aspects:<ref>[http://blog.pyjeon.com/2012/07/29/why-pyjamas-isnt-a-good-framework-for-web-apps/ Why Pyjamas Isn't a Good Framework for Web Apps], Alexander Tsepkov (July 29, 2012)</ref>
-* Browser detection instead of feature detection
-* Bloat and boilerplate hell (Python feature coverage is favored over speed and size)
-* Debugging (perfect with Pyjs Desktop, but that is broken for more than 3 years)
-* Python is not Java, DOM is not a Desktop (the underlying GWT unnecessarily fakes a desktop GUI)
-On the other hand, as a dynamically typed language Python is a specifically good fit for compiling code to JavaScript, actually a more natural fit than GWT's original Java-to-JavaScript approach.<ref>[http://www.advogato.org/article/985.html Thinking alike], comment by user cananian (Nov 5, 2008)</ref>
-==Alternatives==
-Most alternatives to Pyjamas are translators rather than frameworks.<ref>[http://blog.pyjeon.com/2012/09/17/301/ Pyjamas Alternatives for Web Development], Alexander Tsepkov (September 17, 2012)</ref>
-* Brython
-* GlowScript
-* py2js
-* PyCow
-* Pyjaco
-* PyvaScript
-* RapydScript
-* Transcrypt
 ==References==
@@ Line 119: / Line 70: @@
 [[Category:Free software programmed in Python]]
 [[Category:JavaScript libraries]]
-[[Category:Rich Internet application frameworks]]
+[[Category:Rich web application frameworks]]
 [[Category:Software using the Apache license]]
 [[Category:Web development software]]

v t e Web frameworks
Comparison
.NET	ASP.NET Core AJAX Dynamic Data MVC Razor Web Forms Blazor DNN BFC MonoRail Umbraco WebSharper
C++	CppCMS Drogon Wt
ColdFusion	ColdBox Platform
Common Lisp	CL-HTTP
Haskell	Servant Snap Yesod
Java	AppFuse Grails GWT ICEfaces JHipster JWt Mojarra Play Remote Application Platform Seam Sling Spring Stripes Struts Tapestry Vaadin Vert.x Wicket WaveMaker ZK
JavaScript	Angular/AngularJS Backbone.js Closure Dojo Toolkit Ember.js Express.js Ext JS Fastify htmx jQuery Knockout.js Meteor MooTools NestJS Next.js Nuxt.js Node.js OpenUI5 Prototype React Remix Sencha Touch SproutCore Svelte Vue.js
Perl	Catalyst Dancer Maypole Mojolicious WebGUI
PHP	CakePHP CodeIgniter Drupal eZ Publish Fat-Free Flow FuelPHP Grav Gyroscope Horde Joomla! Laminas Laravel li₃ Midgard MODX Phalcon PHP-Fusion PHP-Nuke Pop PHP PRADO ProcessWire Qcodo Silverstripe Symfony TYPO3 WordPress XOOPS Yii
Python	BlueBream CherryPy CubicWeb Django FastAPI Flask Grok Nevow Pyjs Pylons Pyramid Quixote TACTIC Tornado TurboGears web2py Zope 2 more...
Ruby	Merb Padrino Ruby on Rails Sinatra
Rust	Rocket
Scala	Lift Play Scalatra
Smalltalk	AIDA/Web Seaside
Other languages	Application Express (PL/SQL) Grails (Groovy) OpenACS (Tcl) Phoenix (Elixir) Shiny (web framework) (R) SproutCore (JavaScript-Ruby) Yaws (Erlang)