statik VS fyne

Yep and to avoid having the front-end files in the distributable I use https://github.com/rakyll/statik to bundle them into the main binary.

> I've had this a few times, most recently with "how do I add this data file to my binary". At least that one made it to master now, and will be in 1.16!

And before 1.16, there is statik: https://github.com/rakyll/statik.

Aren't our web assets part of the system as well? So to make it completely Go, we've gotta some how make them part of the Go code. The most obvious choice for that is to turn them into binaries and embed right inside our backend code. This task is relatively simple with a wide range of tools to choose from. For this project, I went with statik, and simply generate the embeddings with this command.

It seems it's using https://github.com/rakyll/statik -- probably some assets?

statik - https://github.com/rakyll/statik

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.

It would be great if we could add support for Flatpak portals in https://github.com/fyne-io/fyne but I find the portal documentation complicated (especially if preferring to use D-Bus instead of accessing libportal using C). Does anyone have code examples for using portals from Go code?

If you fancy Go, there's Fyne. I don't work in the space so I cannot judge it.

https://github.com/fyne-io/fyne