crossterm VS ratatui

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

> If someone plopped me in front of a rust codebase I'd be at the mercy of the manual for quite a long time.

This is not a representative sample of Rust. That's explicitly triggering edge cases which requires abuse of syntax you wouldn't normally see.

Check out this for something more realistic that anyone should understand https://github.com/ratatui-org/ratatui/blob/main/examples/ca...

nice work!

can I use "cargo install --git https://github.com/aabiji/muse"?

I also recommend:

https://github.com/ratatui-org/ratatui

https://github.com/mikaelmello/inquire

for your further development

I also have a Rust CLI music project here if you want to have a look

https://github.com/glicol/glicol-cli

There are apps that are built on ratatui that support mouse already including an example in the repo[1], and crates (and some internal changes to the buffer) to support iterm/kitty/sixel based images.[2]

[1]: https://github.com/ratatui-org/ratatui/tree/main/examples#cu...

[2]: https://crates.io/crates/ratatui-image

Compared to TurboVision, Ratatui has a lot of missing things:

- Containers

- Dialog types (I'm working on this in https://github.com/joshka/tui-prompts)

- Higher order combinations of widgets (e.g. combine the scrollbar and paragraph)

- Menus

- Any event system (apps bring their own - we just handle display)

- etc.

- There's lots of things in TV that are provided as external crates (like editors, treeview, etc.)

The main thing is that Ratatui is at least right now, just the display side of things. Things to do with events or application shell aren't built-in. This somewhat stems from the immediate vs retained mode approach to the library, but this may change in the future.

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