ubuntu@Ubuntu-laptop:~$ go install deedles.dev/trayscale/cmd/trayscale@latest # github.com/diamondburned/gotk4/pkg/glib/v2 go/pkg/mod/github.com/diamondburned/gotk4/[email protected]/glib/v2/gfileutils.go:745:12: could not determine kind of name for C.GFileSetContentsFlags go/pkg/mod/github.com/diamondburned/gotk4/[email protected]/glib/v2/gfileutils.go:758:2: could not determine kind of name for C.g_file_set_contents_full

i get these when trying to install

This pull request implements and uses a new command, cmd/gtkbuildergen, which takes a .ui file and generates Go code to initialize templates as if they were their own widgets. The tool is not comprehensive and will probably fail if given a .ui file other than those of cmd/trayscale.

This is only a partial implementation. In particular, clicking on the current page will not navigate properly. This will require a complete replacement of the StackSidebar in order to fix. That's quite a bit more complicated, though, so it'll have to be done later.

This completely eliminates all GtkBuilder usage. In so doing, it also fixes a bug that caused the race detector to crash the app. It seems that some usages of GtkBuilder were being detected by the race detector, and only by the race detector for some reason, as being violations of the cgo pointer passing rules. I'm not sure if they actually were or not, but this seems to have completely fixed it, so... Problem solved, I guess.

Minor changes to the way that prefs are handled when updating. Definitely not as extensive as I'd originally intended, but after looking through the code again I don't see a particular reason to move the polling to the other side of the event, potentially freezing up the UI while a poll happens.

This started out as a quite different pull request, but as I did some experimentation it wound up also including a bit of a rewrite of tailscale. It should be quite a bit more efficient at some stuff now, as well as having a few new features.

Closes #15. Part of #12 and #13.

The info is available via the tailscale.com/net/netcheck package. It should probably be run manually by the user, rather than via a poller like the peer status is.

The Tailscale CLI tool requires all non-default options to be re-specified whenever running tailscale up to change something. This means that if the user has previously run tailscale up --advertise-exit-node, running tailscale up --exit-node=1.2.3.4 will fail unless --advertise-exit-node is also specified again. Alternatively, the user can specify --reset to set all options that aren't specified back to their defaults.

The best option is to find some way to find out what options are set and setting them alongside the others. If necessary, it might be possible to parse the required options out of the error message printed by the call to tailscale up.

Closes #9.

This pull request has expanded a bit and now includes a complete UI rework. It also removes the polkit integration, since it apparently didn't actually work. Instructions on a proper configuration have been added to README.md instead.

The UI is a ton nicer, and works better in general. Unfortunately, every systray implementation that I could find used Gtk2 or Gtk3 GtkStatusIcons internally, which breaks any usage of Gtk4 even if all it does it link to it. As such, this removes the system tray icon completely and uses notifications instead. It's not ideal, but it works.

Thanks to the Prefs() rework from #18, data flow from Tailscale to the UI is a tad strange. It mostly comes from the status, but a few items are from prefs instead, and those are being pulled on demand during the update. This is rather odd, so here's the current plan to fix it:

• [ ] Move status fetching into the GTK event and rework polling loop to just be a simple timer that fires the custom GTK update event.
• [ ] Poll prefs at the beginning of the event.
• [ ] Manually update switches directly via return values from methods.

I'm not sure how technically feasible this is, due to the low-level stuff that Tailscale needs access to, but if possible it would be great to get this packaged up with Flatpak. In particular, that might make it possible to run on the Steam Deck nice and easily, which would be nice, at least until the official support is added.

Questions:

• Is it feasible to interact with the Tailscale daemon and CLI from inside of a Flatpak environment?
• Is it possible to package the Tailscale daemon and CLI inside of the Flatpak, thus eliminating non-Flatpak dependencies?

Peers currently only show their names and a list of their Wireguard IP addresses. More features would be good. Here are a few:

• More information just pulled straight from ipnstate.PeerStatus, such as ID, OS, and Active.
• A better indicator that the top peer is the current machine.
• Ability to send and receive files from a peer, possibly? This one's potentially messy.