Differences

This shows you the differences between two versions of the page.

--- misc:gui_frameworks_for_linux [2017/05/13 01:37] – mithat
+++ misc:gui_frameworks_for_linux [2017/05/29 19:28] (current) – [wxPython (including Phoenix)] mithat
@@ Line 5: / Line 5: @@
 ==== Tkinter ====
-<WRAP center round info 90%>
+**TL;DR**: Perhaps OK for small, one-file utility apps
-Perhaps OK for small, one-file utility apps
-</WRAP>
 Pros
@@ Line 66: / Line 64: @@
 ==== PyGObject ====
-<WRAP center round info 90%>
+**TL;DR**: Perhaps best option for Linux-centric apps---unless/until some GNOME goofiness happens.
-Perhaps best option for Linux-centric apps---unless/until some GNOME goofiness happens.
-</WRAP>
 Replacing PyGTK.
@@ Line 91: / Line 87: @@
 ==== wxPython (including Phoenix)===
-<WRAP center round info 90%>
+**TL;DR**: Perhaps best option for multi-platform proprietary apps that have zero budget.
-Perhaps best option for multi-platform proprietary apps that have zero budget.
-</WRAP>
 Pros
@@ Line 118: / Line 112: @@
 ==== PyQt ====
-<WRAP center round info 90%>
+**TL;DR**: Perhaps best option for multi-platform FOSS apps and for proprietary apps that have a $500 tools budget.
-Perhaps best option for multi-platform FOSS apps and for proprietary apps that have a $500 tools budget.
-</WRAP>
 Pros
@@ Line 135: / Line 127: @@
 ==== PySide ====
-<WRAP center round info 90%>
+**TL;DR**: Abandonware? If not now, later?
-Abandonware? If not now, later?
-</WRAP>
 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't seem to have much mindshare.
 ==== Kivy ====
-<WRAP center round info 90%>
+**TL;DR**: Not really a desktop application framework. Well-suited to touch interfaces.
-Not really a desktop application framework. Well-suited to touch interfaces.
-</WRAP>
 Pros