Gui.cs VS Uno Platform

As someone who writes software for moderately boring business operations, I've been wondering making terminal-based apps with lots of keyboard shortcuts would lead to a more productive end user than writing a web app.

I've been looking at https://github.com/gui-cs/Terminal.Gui but haven't tried it yet.

Thanks but I'm sticking with Terminal.Gui

Used this neat library to handle the GUI gui-cs/Terminal.Gui: Cross Platform Terminal UI toolkit for .NET (github.com)

Terminal.GUI - cross platform terminal UI for .NET: https://github.com/gui-cs/Terminal.Gui

Two I've used are Terminal.Gui for .net https://github.com/gui-cs/Terminal.Gui and BubbleTea for Go https://github.com/charmbracelet/bubbletea

In that case you can use console (https://github.com/gui-cs/Terminal.Gui) to make games.

As you can see the tool is always integrated into the terminal because it has built on a cross platform UI toolkit based on a fantastic open source project called Terminal.Gui. Now you can select the objects by using space bar and than confirm the selection with enter. The result will be:

C# - https://github.com/gui-cs/Terminal.Gui

Since you mentioned minimal GUI, have you thought of a TUI? I haven't spiked it out but I would guess Terminal.Gui would work with Native AOT

And Uno Platform (https://platform.uno/) is akin to React Native in terms of native controls usage.

also UNO Platform (C#) which is suitable for simple or complex cross platform business applications : https://platform.uno/

Why is this a problem? At face value, it isn't a problem. Taking a step back at a more global level, what does "uComponents" mean to the rest of the world? Many of the .NET developers who heavily use NuGet may have not even heard of Umbraco CMS, let alone a 3rd party plugin for it. What if people from the Uno Platform community are browsing NuGet for some kind of components extension library? You can see, this could get confusing outside the scope of the Umbraco community/ecosystem. On top of this, uComponents was developed against Umbraco v4, with its last release in 2016, now it's there to be lingering on the NuGet repository until the end of time, set in stone.

Not a fan of XAML after trying to get into it, but there is Uno Platform. It wraps native widgets on mobile, just like React Native (which is good for accessibility), and uses C#. https://platform.uno/

My guess is that it's mainly focused on mobile. On Windows, it has no overhead (behaving like a normal WinUI 3 app), on macOS I think it uses Catalyst by default (which was developed by Apple to make more iOS apps available for Mac desktops) and on Linux it draws its own widgets that the devs try imitating the GTK style with.

On Android and iOS, it just uses the native widgets which I think is a better experience so you can see my reasons for guessing it's mobile-first. That may or may not be what you want.

5- Uno

> ...building UIs with the document/element api

When the whole premise is flawed, JSX or not, does it really matter if there is a better or worse way of misusing a technology not meant for UIs?

Leave HTML and JavaScript to Wikipedia and other hypertext document libraries.

Unfortunately, WASM is not there yet, but people are trying: https://platform.uno.

Uno Platform is fully open source, under Apache 2.0 license. You can see the license here https://github.com/unoplatform/uno/blob/master/License.md