nitriding VS fyne

Go has an io library that enables a developer to access the host file system. Building a GUI application that interacts with the native file system requires the developer to try to make the user experience the same, or similar, across platforms. We want a user to be able to work with the application without having to learn multiple ways to respond to application prompts to open files. Fortunately, fyne.io provides a fairly robust cross-platform toolset with which to accomplish this task.

The CPU monitor dashboard layout was fairly straightforward using the fyne.io framework. Like most GUIs, you create all your display objects and widgets, add containers for structuring the objects in columns, rows, and grids, and then place the containers into a window. I set up some control buttons with associated functions that get invoked when they are pressed. I also set up some label widgets to display specific CPU fields and data. I decided that it would be simpler for displaying memory if I pre-formatted memory in blocks of strings before placing them in containers. I created an UpdateAll() function that the controller called whenever it had new data to display.

If you want to look at something a bit bigger I can also suggest looking at Fyne (the toolkit that I’m working on and using to build the app): https://github.com/fyne-io/fyne

Tauri is definitely a hot SEO keyword!

I had not heard of https://wails.io before for Golang GUIs, only https://fyne.io which renders its own controls.

And this is how https://github.com/go-gst/go-gst, https://github.com/go-gl/glfw, and even https://fyne.io/ are using system libraries to propose a lot of functionalities.