You are not logged in.
I also have xdg-desktop-portal-wlr installed, we should include that too, IMO
OK I knew nothing about this one, let's put it in if it's useful. What is it good for?
There's a whole load of them:
john@carbon:~$ apt list 'xdg-desktop-portal*'
xdg-desktop-portal-dev/stable 1.20.3+ds-1 all
xdg-desktop-portal-gnome/stable 48.0-2 amd64
xdg-desktop-portal-gtk/stable,now 1.15.3-1 amd64 [installed]
xdg-desktop-portal-hyprland/stable-backports 1.3.11-1~bpo13+1 amd64
xdg-desktop-portal-kde/stable 6.3.5-1 amd64
xdg-desktop-portal-lxqt/stable 1.1.0-2+b1 amd64
xdg-desktop-portal-phosh/stable 0.46.0-2 amd64
xdg-desktop-portal-tests/stable 1.20.3+ds-1 amd64
xdg-desktop-portal-wlr/stable 0.7.1-2 amd64
xdg-desktop-portal-xapp/stable 1.1.0-1 amd64
xdg-desktop-portal/stable,now 1.20.3+ds-1 amd64 [installed,automatic]https://wiki.archlinux.org/title/XDG_Desktop_Portal <- somewhat interesting
Last edited by johnraff (Today 03:07:21)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
hhh wrote:I also have xdg-desktop-portal-wlr installed, we should include that too, IMO
OK I knew nothing about this one, let's put it in if it's useful. What is it good for?
Screenshots and screencasts...
https://packages.debian.org/sid/xdg-desktop-portal-wlr
We only need *-portal-gtk, but think of the poor scrots! ![]()
I don't care what you do at home. Would you care to explain?
Offline
xdg-desktop-portal is Snap and Flatpak support? I didn't know that.
https://packages.debian.org/sid/xdg-desktop-portal
OK, *-portal-gtk description sheds more light on the topic...
xdg-desktop-portal-gtk provides a GTK+/GNOME implementation for the desktop-agnostic xdg-desktop-portal service. This allows sandboxed applications to request services from outside the sandbox using GTK+ GUIs (app chooser, file chooser, print dialog) or using GNOME services (session manager, screenshot provider).
So this also includes AppImages, I would think.
https://packages.debian.org/sid/xdg-desktop-portal-gtk
Last edited by hhh (Today 03:16:36)
I don't care what you do at home. Would you care to explain?
Offline
We've already installed xdg-desktop-portal-gtk in the X11 system because @cog found it was needed to get dark GTK4 themes by default, and you have also referred to it in the past:
https://forums.bunsenlabs.org/viewtopic.php?id=9606&p=2
https://forums.bunsenlabs.org/viewtopic … 11#p147411
https://forums.bunsenlabs.org/viewtopic.php?id=9534
https://forums.bunsenlabs.org/viewtopic.php?id=9571
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
rc.xml
Here is labwc's complete rc.xml showing all the default values:
https://github.com/labwc/labwc/blob/mas … rc.xml.all
and here is a very simple rc.xml:
https://github.com/labwc/labwc/blob/master/docs/rc.xml
We could go three ways:
1) ship a minimal rc.xml with only the values which we want to change - labwc will use default for all the others.
2) ship a full rc.xml with all the values written in so users can immediately see what they are.
3) ship an rc.xml with our values set, and all the default values present but commented-out.
Preferences?
---
Sub-question:
a) make the labwc rc.xml as close as possible to the openbox file so similar sections appear in the same order?
or
b) make our labwc rc.xml as close as possible to the file on labwc's github?
I'm leaning towards 2) + a) but could easily be persuaded otherwise.
---
Third question:
c) keep all the keybinds, mousebinds etc as close as possible to what we now have with openbox?
or
d) keep things as close as possible to the default labwc settings?
Last edited by johnraff (Today 08:07:01)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline