ink VS ratatui

What does this have to do with Inkle's Ink? Well, Ink is a form of engine-agnostic game data creation. At heart, Ink is a narrative scripting language but because it was conceived as middleware, it can be used by many game development stacks. The primary integration is Unity which supports many platforms on its own but Ink scripts can also be run in the browser, Defold, Godot, Unreal and more. You can write Ink once, test it using Inky or Inklecate and deploy it using your desired framework. I can personally attest to running the same Ink script in the browser with ink.js and in the Defold, Godot and Unity game engines.

That's awesome, thanks!

I am aware of Inform 7, I think it is awesome. A few months ago I made a quick demo using Inklescript[1], which I found simpler and more suitable to my project (a Star Trek adventure). Inform 7 remains something I wish to explore in the future when I need something more complex.

Thanks! ;)

---

[1] https://www.inklestudios.com/ink/

As others have said, Twine is really a great starting point for text or choice-based games. If you'd like to get into the weeds a little more, I'd also shout out Ink, which is incredibly flexible and really fun imo, altho it def requires a bit more coding experience.

On the technology side, you might want to check out Inkle: https://www.inklestudios.com/ink/

Start writing in ink or twine.

Otherwise, Inkle is also quite good. (and people have made players for it in Unreal and Unity, so it's not hard to attach to existing game projects.) I don't think it has the nifty visual flowchart though, if that's a piece you care about.

I really like Ink. The developers made tons of games with it like the Sorcery! series, so it has a good foundation, and it's quite easy to write and organize, more than twine in my opinion.

> 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