At home I've got fyne_demo in ~/go/bin ; intellij in ~/bin/idea everything is in my $PATH but I can't access it using the runner, we shouldn't need a terminal to launch them

user@FreeBSD$ uname -a
FreeBSD FreeBSD 12.1-RELEASE-p8 FreeBSD 12.1-RELEASE-p8 GENERIC  amd64

user@FreeBSD$ go version
go version go1.14.7 freebsd/amd64

user@FreeBSD$ go build -v fyne.io/fynedesk/cmd/fynedesk
fyne.io/fynedesk/cmd/fynedesk
# fyne.io/fynedesk/cmd/fynedesk
go/src/fyne.io/fynedesk/cmd/fynedesk/main_unix.go:18:14: undefined: wm.NewX11WindowManager
go/src/fyne.io/fynedesk/cmd/fynedesk/main_unix.go:23:39: undefined: wm.NewX11ScreensProvider

here is the full error

> go get fyne.io/fynedesk/cmd/fynedesk
go get: installing executables with 'go get' in module mode is deprecated.
	Use 'go install pkg@version' instead.
	For more information, see https://golang.org/doc/go-get-install-deprecation
	or run 'go help get' or 'go help install'.
# github.com/go-gl/glfw/v3.3/glfw
In file included from go/pkg/mod/github.com/go-gl/glfw/v3.3/[email protected]/native_linbsd.go:10:
In file included from go/pkg/mod/github.com/go-gl/glfw/v3.3/[email protected]/glfw/include/GLFW/glfw3native.h:114:
In file included from /usr/local/include/GL/glx.h:32:
/usr/local/include/GL/gl.h:56:11: warning: 'GLAPIENTRY' macro redefined [-Wmacro-redefined]
go/pkg/mod/github.com/go-gl/glfw/v3.3/[email protected]/glfw/include/GLFW/glfw3.h:5863:10: note: previous definition is here
# github.com/godbus/dbus/v5
In file included from go/pkg/mod/github.com/godbus/dbus/[email protected]/transport_unixcred_freebsd.go:13:
In file included from /usr/include/sys/ucred.h:39:
/usr/include/sys/_lock.h:38:2: error: unknown type name 'u_int'
        u_int   lo_flags;
        ^
/usr/include/sys/_lock.h:39:2: error: unknown type name 'u_int'
        u_int   lo_data;                /* General class specific data. */
        ^
In file included from go/pkg/mod/github.com/godbus/dbus/[email protected]/transport_unixcred_freebsd.go:13:
In file included from /usr/include/sys/ucred.h:40:
/usr/include/sys/_mutex.h:49:11: error: unknown type name 'uintptr_t'
        volatile uintptr_t      mtx_lock;       /* Owner and flags. */
                 ^
/usr/include/sys/_mutex.h:63:11: error: unknown type name 'uintptr_t'
        volatile uintptr_t      mtx_lock;       /* Owner and flags. */
                 ^
4 errors generated.

Add print screen features

• PrintScreen button captures all displays
• Shift+PrintScreen captures the current window with border.

The images are generated in the windowmanager code but our UI overlay then presents it to the user and offers to save.

This PR makes sure to get all the issues reported by staticcheck fixed and marks the ones that can't be fixed to be ignored for now (waiting for Fyne 2.0.0 mostly). It should now be possible to set the GitHub action to be required :+1:

I use videostream, which is a "chrome app" https://chrome.google.com/webstore/detail/videostream-for-google-ch/cnciopoikihiagdjbjpnocolokfelagl?hl=en

If I use the applications launcher, I can't find the app when I type "videostream" (it works with gnome) When I run the app, it does not appear in the bottom app bar and it misses an icon on alt-tab

This is a work in progress towards proper key bindings.

• [x] Started with allowing code to declare shortcuts...
• [x] Moving through modules so they can declare shortcuts.
• [x] Added a settings UI to list shortcuts

TODO

• [x] Reset bindings when modules are loaded / unloaded
• [ ] Make these bindings configurable in settings

Will fix #37

This is unfortunately as far as I could get on my own. There are various issues that I have been unable to solve.

• The windows do not resize correctly when using right position.

• Already open windows do not update when applying the setting in settings.

• The correct selected values are not shown in settings on start. Seems to be an issue in the clock as well so not related to this PR, I guess.

sometimes windows are too big for the screen (an other issue could be open for that) AFAIK there is only one way to reduce height of window, and if the bottom bar is out of the screen because the app overflows, then we can't do it anymore.

We could add a shortcut such as alt-click or alt-F7 to move window over the top to be able to grab the bottom or we could allow to grab the top border to resize.

Both solution should be implemented from my point of view

Caching the app entries we find. This was some development code that is really required for macOS as the lookup is so slow. Should we add it to Linux/BSD code too? What should it's refresh strategy be?

This was better a few weeks ago - I think it has slowed down since the XRandR code additions.

Drag any window, move it around the desktop, notice a significant lag in where the window is to where the pointer has moved to.

I am considering (and looking for feedback on) creating two new repos extracted from fynedesk.

• backgrounds - our standard backgrounds, with a little Go code to help manage them - and in future to discover others installed
• modules - things like battery, brightness etc that could be used in other apps (fin would like to show a subset of the fynedesk widget panel)

This would allow more consistency and code sharing between apps doing desktop-y things. The backgrounds could bundle lots, or with tags provide a minimal setup - this would allow apps built for FyneDesk (or other well configured platforms) to bundle less in the UI if we know what is on the filesystem instead.

Is your feature request related to a problem? Please describe:

Please provide a way to run applications through keyboard shorcuts. Eg, ctrl+alt+t should start a terminal.

Describe the bug:

Unable to start firefox by clicking on firefox app in app drawer

To Reproduce:

Steps to reproduce the behaviour:

1. Click on username in bottom right
2. Click on network to expand the dropdown
3. Click on Firefox Web Browser
4. Firefox does not start
5. Following error is seen in ~/.cache/fyne/io.fyne.fynedesk/fynedesk.log

2022/12/23 14:54:56 At: /home/xxx/src/fynedesk/internal/x11/win/frame.go:282 2022/12/23 14:54:56 Fyne error: Put image error 2022/12/23 14:54:56 Cause: BadDrawable {NiceName: Drawable, Sequence: 6551, BadValue: 10497468, MinorOpcode: 0, MajorOpcode: 72} 2022/12/23 14:54:56 At: /home/xxx/src/fynedesk/internal/x11/win/frame.go:282 2022/12/23 14:54:56 Fyne error: X11 Error: 2022/12/23 14:54:56 Cause: BadGContext {NiceName: GContext, Sequence: 6558, BadValue: 10497470, MinorOpcode: 0, MajorOpcode: 62} 2022/12/23 14:54:56 At: /home/xxx/src/fynedesk/internal/x11/wm/desk.go:340

Device (please complete the following information):

• OS: Ubuntu Linux
• Version: 22.04.1 LTS
• Go version: 1.19.4
• FyneDesk version: b6e12b57e7d4cd32303a7ec165a7451d33016636

Is your feature request related to a problem? Please describe:

It is now common place in Gnome (and possibly KDE Plasma as well) to set a global DBus value depending on dark/light theme preference. Fyne v2.3.0 will start watching this setting (https://github.com/fyne-io/fyne/issues/2657) but we do not currently set it in Fynedesk.

It believe it would be good if we could set it here to make sure that non Fyne apps (if the user has GTK+4+libadwaita apps or anything else that supports it) follow the preference.

Is it possible to construct a solution with the existing API?

I think so but it might be that we are using the fyne_settings application. In that case, it probably only makes sense to set the DBus preference when running inside Fynedesk. It should be up to the desktop environment to set it in my opinion.

Describe the solution you'd like to see:

Switching between light and dark mode sets the DBus setting that makes sure that all applications that support it automatically follow light and dark preferences.

Is your feature request related to a problem? Please describe:

Is Fynedesk (and/or the underlying library) accessible? Does it work with screen readers? Does it have visual bell for the d/Deaf?

Is it possible to construct a solution with the existing API?

Describe the solution you'd like to see:

We should be able to suspend to disk on laptop, I'm used to a few scenarios :

• when low battery
• when screen is locked and laptop not plugged-in for 5 min
• when action is triggered by menu or shortcut