misc:gui_frameworks_for_linux
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
misc:gui_frameworks_for_linux [2017/05/12 06:51] – mithat | misc:gui_frameworks_for_linux [2017/05/29 19:28] (current) – [wxPython (including Phoenix)] mithat | ||
---|---|---|---|
Line 4: | Line 4: | ||
==== Tkinter ==== | ==== Tkinter ==== | ||
- | TL;DR | + | |
- | | + | **TL;DR**: Perhaps |
Pros | Pros | ||
Line 63: | Line 63: | ||
==== PyGObject ==== | ==== PyGObject ==== | ||
- | TL;DR | + | |
- | | + | **TL;DR**: Perhaps best option for Linux-centric apps---unless/ |
Replacing PyGTK. | Replacing PyGTK. | ||
Line 87: | Line 87: | ||
| | ||
==== wxPython (including Phoenix)=== | ==== wxPython (including Phoenix)=== | ||
- | TL;DR | + | **TL;DR**: Perhaps best option for multi-platform proprietary apps that have zero budget. |
- | | + | |
Pros | Pros | ||
Line 112: | Line 111: | ||
==== PyQt ==== | ==== PyQt ==== | ||
- | TL;DR | + | |
- | | + | **TL;DR**: Perhaps best option for multi-platform FOSS apps and for proprietary apps that have a $500 tools budget. |
Pros | Pros | ||
Line 125: | Line 124: | ||
* Qt code can be heavy, somewhat verbose. | * 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, '' | * 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 ==== | ||
- | TL;DR | + | **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