3 ms·

for Python GUIs (or "TUIs", or "a screen with colorful buttons and controls I can use with the mouse or keyboard but NOT a "GUI" " if that helps some of the res

by zzzeek 3y ago

for Python GUIs (or "TUIs", or "a screen with colorful buttons and controls I can use with the mouse or keyboard but NOT a "GUI" " if that helps some of the responders to get through the day) I recommend considering a console-based GUI using the excellent Textual: https://textual.textualize.io/ https://textual.textualize.io/ this is the most modern GUI (in a console or not) framework you'll find for Python right now.

TheRealPomax 3y ago
Not really a GUI then, though? It's a UI (and from the screenshots, quite nice), but it's lacking the part that makes it "graphical" (which doesn't actually include "colors or borders", of course, we've been able to do those since CGA, and terminals, respectively).
noman-land 3y ago
Wow, Textual looks amazing. Thanks for the link.
deleted 3y ago
[deleted]
1ark 3y ago
I have used React/Preact/React Native/Flutter to build complex UIs. I thought it would be great to use something like this to render TUI and get rid of some of the app complexity for “simpler” one-user apps. I have used it and it is a nightmare when your app gets just slightly complex. Instead of making simple components I ended up traversing the internals of the library. Impressed by some people getting things done with it though. - CSS, why?! It does not really work like CSS when it comes to positioning things, overlapping and so on. Compared to previous versions where these properties were in a dict or sent in to the component, they are now in either big string blocks or in separate files, removing syntax highlighting and/or locality. - Cannot easily use debugging such as PDB because it hijacks Traceback and uses async. Maybe fine if you rely on other debugging tools. - It lacks simple off-the-shelf components such as menu bars, so I built my own, but run into annoying artifacts as mentioned before. Rich, the underlying rendering library is good, and simple enough. I ditched Textual for prompt_toolkit, and can still use Rich to render things in pt.

by zzzeek 3y ago

TheRealPomax 3y ago

Not really a GUI then, though? It's a UI (and from the screenshots, quite nice), but it's lacking the part that makes it "graphical" (which doesn't actually include "colors or borders", of course, we've been able to do those since CGA, and terminals, respectively).

noman-land 3y ago

Wow, Textual looks amazing. Thanks for the link.

deleted 3y ago

[deleted]

1ark 3y ago

I have used React/Preact/React Native/Flutter to build complex UIs. I thought it would be great to use something like this to render TUI and get rid of some of the app complexity for “simpler” one-user apps. I have used it and it is a nightmare when your app gets just slightly complex. Instead of making simple components I ended up traversing the internals of the library. Impressed by some people getting things done with it though. - CSS, why?! It does not really work like CSS when it comes to positioning things, overlapping and so on. Compared to previous versions where these properties were in a dict or sent in to the component, they are now in either big string blocks or in separate files, removing syntax highlighting and/or locality. - Cannot easily use debugging such as PDB because it hijacks Traceback and uses async. Maybe fine if you rely on other debugging tools. - It lacks simple off-the-shelf components such as menu bars, so I built my own, but run into annoying artifacts as mentioned before. Rich, the underlying rendering library is good, and simple enough. I ditched Textual for prompt_toolkit, and can still use Rich to render things in pt.