But at this point it seems rather random when for example compositors based on Wrapland (the kwinft directory) potentially override each others configs but not the ones of wlroots-based ones.
A different idea would to base the subdivision not on the the Wayland plugins but on XDG_SESSION_DESKTOP. For example:
$HOME/.local/share/disman/control/wayland/KDE
$HOME/.local/share/disman/control/wayland/sway
Or directly:
$HOME/.local/share/disman/control/KDE
$HOME/.local/share/disman/control/sway
Alternative
Keep all control files in one directory. Since X11 and Wayland in Disman support the same control files this would in theory allow seamless switching between the session types and different backend plugins when the hash values are computed in the same way, i.e. a certain "UUID" of outputs must be the same cross-backend.
Proposal
Currently all control files are saved in the same directory which is normally:
$HOME/.local/share/disman/control.It could make sense to save the control files in per-plugin separate directories like:
$HOME/.local/share/disman/control/wayland$HOME/.local/share/disman/control/randrMaybe it would even make sense to subdivide the Wayland directory further according to its plugins:
$HOME/.local/share/disman/control/wayland/kwinft$HOME/.local/share/disman/control/wayland/kwayland$HOME/.local/share/disman/control/wayland/wlrootsBut at this point it seems rather random when for example compositors based on Wrapland (the kwinft directory) potentially override each others configs but not the ones of wlroots-based ones.
A different idea would to base the subdivision not on the the Wayland plugins but on XDG_SESSION_DESKTOP. For example:
$HOME/.local/share/disman/control/wayland/KDE$HOME/.local/share/disman/control/wayland/swayOr directly:
$HOME/.local/share/disman/control/KDE$HOME/.local/share/disman/control/swayAlternative
Keep all control files in one directory. Since X11 and Wayland in Disman support the same control files this would in theory allow seamless switching between the session types and different backend plugins when the hash values are computed in the same way, i.e. a certain "UUID" of outputs must be the same cross-backend.