Comment by userbinator 9 hours ago
Why not show the device address? There's plenty of room for it and it's important when you have multiple devices with the same name. Or has the abominable trend of excess whitespace infected TUIs too?
I've absolutely had it with shit "designer" UIs hiding useful information and leaving a sea of useless space instead. There's nothing "nicer" about making users go through more effort.
bluetui author there
You can set a window with in the config file (with = positive integer) and TUI will be displayed with this width even in a large screen.
https://github.com/pythops/bluetui?tab=readme-ov-file#custom...
It's a plague under TUI go software too made with Bubbletea. Also, with some mesh related interfaces written in Python. Both slow and with a shitty interface not properly working under an 80x24 terminal with 16 colours.
I remember some hipster fauxretro player with just some playlist made of m3u links, written in Go. The visualization animations made it unusable under my n270 CPU based netbook. Meanwhile, the playlist URL's from the code played perfectly well under mocp with a really low CPU usage. Oh, you want bells and whistles? I think the Cava terminal visualizer can work with MPD and plug any CLI/TUI client you like.
Hardcoding any color than base16 is usually a poor choice. It should be up to the user to use any other color.
And colors should be semantic. If you don’t have any theming ability, just use reverse video to indicate selected state.
My current pet peeve is cli tools using ansi codes for progress bar. And with very poor detection of terminals.
There's probably nicer ways to express that criticism