Open mildred opened 8 months ago
Afaik sway and other wlroot based compositors in the tradition of window managers have their own way to autostart applications and ignore desktop entries. Please elaborate what interaction between the compositor and clients registering with this portal do you expect? A standalone application like darkman for settings might be more appropriate.
wlr-foreign-toplevel to get the "background" / non-background / active state + SNI to have notifiers for backgrounded apps seems like it should work. Nothing required from the compositor side (only wlr-foreign-toplevel support which I guess most wlroots based compositors already have). And if a compositor wants to show its own list of "background" applications it could implement its own SNI host within the compositor. Otherwise a user would just need to run some random panel that supports a SNI tray.
The Background portal is required by multiple applications. Epiphany (for their web app), Pika Backup (for the scheduled backups) and probably a few others. Missing portals is making Sway / wlroot compositors perform less than the other desktop environments. I'm opening this issue to track the missing Background portal for wlroots.
Interface : https://github.com/flatpak/xdg-desktop-portal/blob/main/data/org.freedesktop.impl.portal.Background.xml
Discussion extract in the xdg-desktop-portal matrix channel:
It's easy to get the list of applications showing a wingow on Sway using
swaymsg -t get_tree
But this is specific to Sway, is there a way to get it for any wlroots compositor?