textual VS Gooey

The Textual project has a lot of screenshots in its documentation. These screenshots are built with the docs, so they are always up to date.

https://textual.textualize.io/

Textual[0] does this for CLI apps. That’s not for full GUI apps, but it’s very DOM-like, uses CSS selectors, etc. and a cool option when it meets your needs.

[0] https://github.com/Textualize/textual

For future projects that need a TUI beyond normal printing to a terminal, I'd recommend taking a look at Textual.

https://jupyterbook.org/en/stable/content/code-outputs.html#...

`less -R` is not the default.

FWIW, textual (and urwid) does ANSII escape codes well: https://github.com/Textualize/textual

  touch file$'\n'name

After installing logmerger, you can run a self-contained demo by running logmerger --demo, to view two log files before and after they are merged, and to play with the user-interface features provided by textual.

I think it just survived naturally, filling in the cracks left by Java / C++.

And not the era of Textual (https://textual.textualize.io/) is here, python may get the spotlight even more.

The name conflicts with a similar python module that allows one to turn any Python console program into a GUI with one line.

https://github.com/chriskiehl/Gooey

Hey! Cool project! I have a question: why do you dump out sys.argv to a local file in the CWD? [0] tmp.txt is hardly a unique name… or am I missing something and this never triggers?

[0] https://github.com/chriskiehl/Gooey/blob/be4b11b8f27f500e732...

This might be of interest to you:

> Gooey - Turn (almost) any Python 3 Console Program into a GUI application with one line

https://github.com/chriskiehl/Gooey

I love gooey: https://github.com/chriskiehl/Gooey

It allows me to quickly slap a GUI on an existing script that accepts command-line-arguments. In the end, I get the best of both world: Discoverability from the GUI, automation through the script, and automatic feature parity between the two.

Downside: Control over the GUI layout is basic, and only "standard" GUI features work, but I never felt limited when using it.

similar for local/individual usage:

https://github.com/chriskiehl/Gooey - take a python-CLI, make a TK-windows

and then probably even simple dashboarding like streamlit.

Like Gooey?

As for how I'd handle it, I would probably combine both into one command-line program, with all filepaths using pathlib and letting argparse handle the options. That way you could optionally generate a GUI with gooey with little extra effort, although this would also add a dependency.