trayscale VS fyne-cross

There's something like this. I try but my internet stop working when I use that. https://github.com/DeedleFake/trayscale

I've actually just recently used this with both pointer and value reveivers in one of my own projects.

I've got a project that depends on Libadwaita 1.2. The ubuntu-latest runner is 22.04 which only has Libadwaita 1.1 available in its repos, causing all of my CI runs to fail. I don't use Ubuntu personally so maybe this is something I can fix via APT and I just don't know how, but what's the recommended procedure for handling a situation where the runner's version of a dependency of a project is out-of-date? I couldn't seem to find anything in the official documentation or anywhere else via Google.

Source: I deal with this myself quite a bit with the Gtk4 bindings I use for one of my projects.

Here's an actual module that I work on as an example.

I've tried a number of them over the years but my latest attempt at a GUI project uses Gtk4.

#1: Introducing Tailscale SSH | 13 comments #2: Tailscale devs sometimes contribute to Headscale #3: I got annoyed at the lack of a Linux GUI, so I built one myself. It's not finished by any means, but it can at least list peers and their IPs. | 1 comment

Yep. I was using manual WireGuard tunnels for that, but everytime I added a machine I had to configurations from both sides with manual key swaps, plus the fact that it I wanted direct connections between each machine the configuration would literally have increased exponentially. Tailscale handles all of that for me. Literally. It's primarily an automatic WireGuard tunnel coordinator. I just have to install it and log in and voila, it just works. I like it so much that I've actually got a project that wraps a GUI around Tailscale for Linux.

This is very likely. I've been writing a GUI wrapper for the Linux Tailscale client, and part of what I interact with from their libraries uses generics. In particular, they've got a views package that implements immutable containers.

Using https://github.com/fyne-io/fyne-cross makes it super simple to cross compile to other systems and architectures as well.

There may also be some hints in the Docker config that fyne-cross uses for compilation? https://github.com/fyne-io/fyne-cross

The setup should be pretty straight forward, you just need Go and Docker (as per the docs https://github.com/fyne-io/fyne-cross) after that you compile the downloader and it makes an app you can install like a normal native app.

I would personally say that the best option at the moment is Fyne (https://github.com/fyne-io/fyne). It provides a very easy to use interface with easy portability and cross-platform support. All applications can easily be cross-compiled using https://github.com/fyne-io/fyne-cross and a lot of developer information exists on https://developer.fyne.io/.

I think it’s the best for Go because it manages to bring a very easy to use API and still allow for a lot of flexibility. Your app will run on all major desktop operating systems (even NetBSD and OpenBSD with the upcoming release) but also on mobiles. It doesn’t suffer from the same issues that bindings to C-libraries (like GTK and Qt) have and is also super easy to cross-compile using https://github.com/fyne-io/fyne-cross.

Fyne is much better when it comes to cross-compiling that GTK+3 will ever be. The GTK+3 binaries are not statically linked and thus needs a lot more GTK+3 dependencies installed on the target system compared to Fyne which basically needs nothing (just a GPU driver, but you’re not very good off without one either way). Fyne also allow you to cross-compile using https://github.com/fyne-io/fyne-cross with ease, taking care of all of the heavy lifting.

Yes. Fyne-cross has support for building for the Android target. https://github.com/fyne-io/fyne-cross