Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
1–10 of 83 posts
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#2How fast does it stream a 10gb file though?
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#3What? 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
#4I'm expecting a terminal UI to be primarily keyboard-driven, but the demo uses the mouse a lot. Anyone having experience with this library and able to confirm keyboard navigation is good by default?
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#5I'm expecting a terminal UI to be primarily keyboard-driven, but the demo uses the mouse a lot. Anyone having experience with this library and able to confirm keyboard navigation is good by default?
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.
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#6I'm expecting a terminal UI to be primarily keyboard-driven, but the demo uses the mouse a lot. Anyone having experience with this library and able to confirm keyboard navigation is good by default?
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.
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#7Earlier 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.
Are there any specific examples from the demo that don't show proper highlights (i.e. that don't look exactly like e.g. TurboPascal, Norton Commander or Linux menuconfig in terms of hints/highlight/focus)?
This isn't an emulation of a mouse gui stuck in a terminal, this is literally a port of an older curses lib to the latest .net, so it doesn't feel like it should have any unnecessary influence from desktop ui systems at all.
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#8Neat!
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?
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#9What? 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#...
Re: Terminal.Gui: A Cross Platform Terminal UI Toolkit for .NET
#10Neat! 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?
Correct