misc:gui_frameworks_for_linux
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
misc:gui_frameworks_for_linux [2017/05/12 06:05] – [Tkinter] mithat | misc:gui_frameworks_for_linux [2017/05/29 19:27] – mithat | ||
---|---|---|---|
Line 4: | Line 4: | ||
==== Tkinter ==== | ==== Tkinter ==== | ||
+ | |||
+ | **TL;DR**: Perhaps OK for small, one-file utility apps | ||
+ | |||
Pros | Pros | ||
* Comes out of the box with Python. | * Comes out of the box with Python. | ||
Line 58: | Line 61: | ||
root.mainloop() | root.mainloop() | ||
</ | </ | ||
- | |||
- | Thoughts | ||
- | * Perhaps ok for small, one-file utility apps. | ||
==== PyGObject ==== | ==== PyGObject ==== | ||
+ | |||
+ | **TL;DR**: Perhaps best option for Linux-centric apps---unless/ | ||
+ | |||
Replacing PyGTK. | Replacing PyGTK. | ||
Pros | Pros | ||
+ | * Workflow (UI layout to code) is pleasant. | ||
* First-class Linux framework. | * First-class Linux framework. | ||
* LGPL | * LGPL | ||
Line 81: | Line 85: | ||
* Poor support on other operating systems. | * Poor support on other operating systems. | ||
* GTK3 is the future and it is built for GNOME. For other desktop environments, | * GTK3 is the future and it is built for GNOME. For other desktop environments, | ||
- | |||
- | |||
- | Thoughts | ||
- | * Workflow (UI layout to code) is pleasant. | ||
- | * Perhaps best option for Linux-centric apps---unless/ | ||
| | ||
- | ==== PyQt ==== | + | ==== wxPython (including Phoenix)=== |
- | Pros | + | <WRAP center round info 90%> |
- | * First class Linux framework. | + | Perhaps best option for multi-platform proprietary apps that have zero budget. |
- | * Excellent multiplatform support (except maybe non-GNOME GTK). | + | </ |
- | * Lots of components (including "we do it differently" | + | |
- | * Used by Spyder and a lot of others. | + | |
- | Cons: | ||
- | * GPL-only or commercial license is at ~$500. (PySide is LGPL, but there has been little development.) | ||
- | * Qt code can be heavy, somewhat verbose. | ||
- | * Possibly PITA to install if not using distro repos (which you want because it moves so fast).((on Debian, '' | ||
- | |||
- | Thoughts | ||
- | * Perhaps best option for multi-platform FOSS apps and for proprietary apps that have a $500 tools budget. | ||
- | |||
- | ==== wxPython (Phoenix)=== | ||
Pros | Pros | ||
* Liberal license. | * Liberal license. | ||
Line 124: | Line 112: | ||
* Events: self.Bind(// | * Events: self.Bind(// | ||
- | Thoughts | + | ==== PyQt ==== |
- | * Perhaps best option for multi-platform proprietary apps that have zero budget. | + | |
+ | **TL; | ||
+ | |||
+ | Pros | ||
+ | * First class Linux framework. | ||
+ | * Excellent multiplatform support (except maybe non-GNOME GTK). | ||
+ | * Lots of components (including "we do it differently" | ||
+ | * Used by Spyder and a lot of others. | ||
+ | |||
+ | Cons: | ||
+ | * GPL-only or commercial license is at ~$500. (PySide is LGPL, but there has been little development.) | ||
+ | * Qt code can be heavy, somewhat verbose. | ||
+ | * Possibly PITA to install if not using distro repos (which you want because it moves so fast).((on Debian, '' | ||
+ | |||
+ | ==== PySide ==== | ||
+ | |||
+ | **TL;DR**: Abandonware? | ||
+ | |||
+ | Classic PySide was released in 2015 and works with Qt 4.8 framework. PySide2, which supports Qt5, is being developed, but it's not production ready, seems to be moving slowly, and doesn' | ||
==== Kivy ==== | ==== Kivy ==== | ||
- | Interesting, | + | **TL;DR**: Not really a desktop application framework. |
Pros | Pros |
misc/gui_frameworks_for_linux.txt · Last modified: 2017/05/29 19:28 by mithat