tui-rs VS crossterm

The TUI is built with the awesome Ratatui [0] library (formerly tui-rs [1]). UX is certainly not my area of expertise and I would not have been able to create Trippy without this library.

[0] https://github.com/ratatui-org/ratatui

[1] https://github.com/fdehau/tui-rs

Rust has great libraries for TUIs. tui-rs (https://github.com/fdehau/tui-rs) has been used in numerous popular applications, but is unmaintained. ratatui (https://github.com/tui-rs-revival/ratatui) is the maintained version, and is pretty new. Less widely known is cursive (https://github.com/gyscos/cursive), which I have yet to try.

Aside from the libraries, I just wanted to start a project that would make be better at Rust. The easy distribution with cargo is a huge bonus though.

CLI, use Clap. If you want to get fancy, use Tui.

u/lordnacho666 It uses the fabulous https://github.com/fdehau/tui-rs (now revived as https://github.com/tui-rs-revival/ratatui) TUI lib.

This app is based on the these two crate in rust (tui-rs , tui-textarea). The text area provide the Emacs motions and I integrated the vim motions there, but the editor in this app as much simpler than the huge VIM and Emacs systems

If you interested in the TUI apps in rust you can start with the crate tui-rs or its revival ratatui. They have examples inside of them which you can start and see the source code to get the basic functionalities. For the text editor you can check examples in the crate tui-textarea.

For Golang there is Bubbletea [1], Textual [2] for Python and tui-rs for Rust [3].

[1] https://github.com/charmbracelet/bubbletea

[2] https://github.com/textualize/textual

[3] https://github.com/fdehau/tui-rs

You can check tui-rs, is a library to build CLI interfaces and has some examples about using user input without blocking the UI

I have this feeling with all rust apps using crossterm crate as their backend like GitUI for example

I guess you could use EventStream like in this example

Made a small toy using crossterm that simulates the falling sand using the rules laid out by day 14. Bit late to the party but was pretty fun. The moment I saw the prompt I was fully intent on making some sort of visualization for this after getting the solution.

There are plenty of terminal UI libraries that are actually nice to work with. For Python, there's Textual and PyTermGUI. For Rust, there's ratatui and Cursive (or, if you want something a bit lower level, crosster or termion). For Go, there's bubbletea.

Switching the backend of Cursive to crossterm removed dependence on ncurses

I don't know where to start, CrossTerm can read events asynchronously with tokio https://github.com/crossterm-rs/crossterm/blob/master/examples/event-stream-tokio.rs , but I don't have any idea what that really means, I am coming from the HTML Canvas and TypeScript. I want the most simple and basic method possible. Cheers!

Just wondering if anyone has any insight into the current development and maintenance of termion? It currently has 67 issues and 24 merge requests and no code activity has happened since Sep 27 2021, so nothing in over a year. I am of course grateful for the existing project, but just somewhat concerned that it ends up being abandoned or forgotten seeing as it is one of the premiere tui libraries written purely in Rust (other being crossterm).

I might make a gui frontend in the future, but for now i'll focus on the terminal. The terminal doesn't mean it doesnt support mac or windows though, they have terminals too! And the library used for accepting key-input is crossterm which supports windows!

I used crossterm. Really love the simplicity of the API, definitely fit my purposes well.

For the terminal part you could use https://crates.io/crates/crossterm