The fact that even the preview isn't a TUI is just lame. Keyboard controls are also non-functional right now.
TUI Studio – visual terminal UI design tool
41–50 of 304 posts
Re: TUI Studio – visual terminal UI design tool
#42Earlier quoted context omitted.
One justification for TUIs is remote access over SSH.
You can tunnel a port over SSH and get a web UI locally, though it's not commonly done. I feel like more people would actually do this if tunneling a port was just ever so slightly easier (like, you're already SSH'd into a box, then you run a command, then you somehow automatically get a tunnel for that command's UI port plus a local browser window open to the page)
(I think terminal-based GUIs are neat just for fluidity of use- you can pop one open during a terminal session and close it without switching to mouse or shifting your attention away from the terminal. They can also be a nice addon to a primarily CLI utility without introducing big dependencies)
Re: TUI Studio – visual terminal UI design tool
#43I mean yes, code editor are great for this but a lot of the TUIs I see are so slow it begs the question why they exist to begin. CLIs are supposed to be remixable and scriptable.
I think a better architecture would be to generally keep CLIs work like CLIs and have separate processes that add terminal rendering functionalities for those that need / want it but in general it is an anti-pattern to start from this as default.
Re: TUI Studio – visual terminal UI design tool
#44This is nonsensical, there is nothing textual about the UIs being shown here. It doesn't stop being a GUI if you have a 1:1 representation of the concept within character cells. The UX actually matters, and TUIs are generally built for effectiveness and power (lazygit being an excellent example). But once you start adding mouse clickable tabs, buttons, checkboxes etc. you left the UX for TUIs behind and applied the U…
Re: TUI Studio – visual terminal UI design tool
#45Am I the only one who thinks the recent TUI explosion is absolutely not necessary? I mean yes, code editor are great for this but a lot of the TUIs I see are so slow it begs the question why they exist to begin. CLIs are supposed to be remixable and scriptable. I think a better architecture would be to generally keep CLIs work like CLIs and have separate processes that add terminal rendering functionalities for those…
Re: TUI Studio – visual terminal UI design tool
#46I really don't want my TUI's to look like GUI's rendered in low res. The appeal to me of a TUI is that it is built specifically to be a TUI, and that means eschewing complexity and detail , and favouring compact text.
Re: TUI Studio – visual terminal UI design tool
#47Earlier quoted context omitted.
One justification for TUIs is remote access over SSH.
You can tunnel a port over SSH and get a web UI locally, though it's not commonly done. I feel like more people would actually do this if tunneling a port was just ever so slightly easier (like, you're already SSH'd into a box, then you run a command, then you somehow automatically get a tunnel for that command's UI port plus a local browser window open to the page)
enter ~C -L 8080:localhost:80Re: TUI Studio – visual terminal UI design tool
#48This is nonsensical, there is nothing textual about the UIs being shown here. It doesn't stop being a GUI if you have a 1:1 representation of the concept within character cells. The UX actually matters, and TUIs are generally built for effectiveness and power (lazygit being an excellent example). But once you start adding mouse clickable tabs, buttons, checkboxes etc. you left the UX for TUIs behind and applied the U…
[flagged]