textual VS wtpython

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.

I'm the author of Rich, a Python library for fancy formatting in the terminal. Textual is a framework I'm building around Rich for creating terminal applications. It's powered by async and borrows a number of techniques from web development.

It's still in active development, but it has reached a point where you can play with it. The most recent release adds a tree control which you can use to navigate a directory and pick files.

My hope is that a Textual UI will be at-least as easy to write as a command line interface, and projects will grow a --tui switch to launch an interactive app.

There's already an app using Textual: [wtpython](https://github.com/what-the-python/wtpython)

Textual (https://github.com/willmcgugan/textual) is the TUI and what-the-python aka wtpython (https://github.com/what-the-python/wtpython) is that specific tool.

GitHub: https://github.com/what-the-python/wtpython