What? No Blazor support? No mobile support? (Joke) I think console UIs are good for a sweet spot where you need a "just good enough" UI that you can whip up in a few minutes. I hope this meets the sweet spot.
I know you're joking, but I wish I had client-server support with xterm.js or something similar. I'd like to write MUDs (Multi-User Dungeon games) in C#...
Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
11–20 of 83 posts
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#12Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#13Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#14Neat! I wish it also worked with something like xterm.js, a terminal in the browser. Either by compiling .Net to WASM... Like Client-Side Blazor does, right? ...or using client-server technology... Like Server-Side Blazor does, right?
We're working on it [1]
[1] https://github.com/Blazor-Console/HACC/blob/main/README.md
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#15Earlier quoted context omitted.
Tab navigation and hotkeys are enabled by default. It's easy to add other keyboard overrides as well. You do not need a mouse to use it.
I may be showing my age here, but I think most people would expect a TUI to provide arrow key navigation and highlight by default, which is not demonstrated. Simply mapping Gui -> TUI isn't really a good user experience IME. The terminal should generally be keyboard-first/designed with keyboard-only in mind.
We view the mouse as optional. We want the mouse to work perfectly, but it should be optional. If any of the library doesn't work well with just a keyboard, please submit an issue!
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#16What? No Blazor support? No mobile support? (Joke) I think console UIs are good for a sweet spot where you need a "just good enough" UI that you can whip up in a few minutes. I hope this meets the sweet spot.
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#17Earlier quoted context omitted.
I may be showing my age here, but I think most people would expect a TUI to provide arrow key navigation and highlight by default, which is not demonstrated. Simply mapping Gui -> TUI isn't really a good user experience IME. The terminal should generally be keyboard-first/designed with keyboard-only in mind.
Terminal.Gui maintainer here... We view the mouse as optional. We want the mouse to work perfectly, but it should be optional. If any of the library doesn't work well with just a keyboard, please submit an issue!
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#18Way to go, team.
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#19Earlier quoted context omitted.
Terminal.Gui maintainer here... We view the mouse as optional. We want the mouse to work perfectly, but it should be optional. If any of the library doesn't work well with just a keyboard, please submit an issue!
That's good to hear but I have to wonder then why the demo is seemingly exclusively demonstrating the mouse?
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#20First I thought resizing doesn't work but it seems it's only an issue with kitty, on alacritty it works as expected, in case anyone else is wondering the same.