ATAC VS ratatui

Many PR about typos fixing or installing GitHub actions to validate spellchecking on various repositories fix typos #4 ccoVeille posted on Apr 15, 2024 Fix typos and style Format README.md file View on GitHub Add Typos GitHub Action #37 ccoVeille posted on Apr 19, 2024 https://github.com/marketplace/actions/typos-action Fixes #28 View on GitHub fix typos #113 ccoVeille posted on Apr 13, 2024 Fix typos in code and tests Fix acronyms and brand names View on GitHub fix typos, brands and acronyms #21 ccoVeille posted on Apr 01, 2024 fix typos in code, test and documentation Fix registered trademark and other acronyms View on GitHub Fix typos in the documentation and code comments #99 ccoVeille posted on Apr 21, 2024 View on GitHub typos suggestion #390 ccoVeille posted on Apr 22, 2024 Check list [X] I have performed a self-review of my code [ ] I have commented my code in hard-to-understand areas [X] I have made corresponding changes to the documentation Description Fix some typos and wordings in README.md Fix headers style Fix exemplī grātiā usage (Latin) Type of change [ ] Bug fix [ ] New feature [ ] Refactor [ ] Breaking change [X] Documentation change Test environment Shell [ ] bash [ ] zsh [ ] fish OS [ ] Linux [ ] Mac OS X [ ] Windows [ ] Others: View on GitHub Fix typo and style #3 ccoVeille posted on Apr 25, 2024 View on GitHub

As a sound and music computing person, I rarely used tui before although I use cli tools often, e.g. SoX. I usually use Audacity to record on Mac. But then I realized I wanted a tool that could quickly open and record inspiration, and that's when TUI came into play: I decided to write my own custom tool called asak (audio Swiss Army Knife) [1]

This way I can quickly record on Mac, and of course, since this is Rust and ratatui [2], this tool should also be cross-platform.

[1] https://github.com/chaosprint/asak

[2] https://ratatui.rs/

> 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