bubbles VS www.yaml.org

I recommend looking at the charm libraries. Lip gloss https://github.com/charmbracelet/lipgloss can provide the styling and bubble tea can handle the screen updates and framework https://github.com/charmbracelet/bubbletea there is a premade progress bar component in bubbles library. https://github.com/charmbracelet/bubbles

nhooyr/websocket, shollz/pake, charmbracelet/bubbles, charmbracelet/bubbletea, charmbracelet/lipgloss, muesli/reflow, klauspost/pgzip and many, many more.

You should check bubbletea, bubbles and harmonica

At Charm, we generally use Go for all our libraries like Bubble Tea, Bubbles, and Lip Gloss. Go should be easy to pick up if you know JavaScript and Python. That being said there are also fantastic libraries available for Python (https://github.com/Textualize/rich) and JavaScript as well.

I think you can, but if you're using Go I would recommend using Bubble Tea, Bubbles, and Lip Gloss for better customizability and flexibility (you can also use the gum code as reference).

You picked a good time, too, since the textarea bubble is brand-spanking-new! https://github.com/charmbracelet/bubbles

We started working on Bubble Tea in January 2020 and launched it October 2020! We originally built it for Glow and the mini Charm TUI which developed most of the ecosystem (aka Bubbles.

charmbracelet/bubbles

From a cursory reading of the docs it seems Bubble Tea doesn't implement things like that, but that the author has a "widget" library at https://github.com/charmbracelet/bubbles

First of all, create a file in the root project directories called compose.yaml. YAML is a text format that uses indentation to specify dependencies between configuration options. Be aware that incorrect indentation will cause problems with executing commands properly.

Most commonly written in YAML, these files are large and complex to read and understand. And being written in YAML comes with its challenges (and quirks) since it is an additional programming language that devs need to learn.

YAML Ain't a Markup Language

Note, that this file is a Markdown and YAML file at the same time, and as such human- and machine-readable, if the fields are filled carefully.

Front matter is a bit of text at the start of a file (YAML to be exact) that is placed between two ---

Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.

Personally, I'd love to see them using a standard file format like TOML or YAML so that they're easy to parse and work with using already-existing tools.