Input and mode configuration in system compositor

[Bill Spitzak]

Does there really need to be two compositors?

It would be nice to run programs for two users on the same screen and 
see them both at once, rather than "fast user switching". Desktop 
switching is nice but I see no reason (except for history) to bind it so 
strongly to "user". What I would like to see is the ability to run a 
program that says "now I want to be this user" and then all programs you 
then launch belong to that user.

Wayland seems well enough designed that this should be possible.

Per-user key setup is nice but all current systems make it a pain to fix 
the setup for all users, this would make that easier. When I buy a new 
keyboard and plug it into the computer, it is not likely that I am going 
to switch back to the old keyboard when a different user is on the 
machine. And you have to face the fact that most of this "configuration" 
is to make the new hardware work correctly, not some kind of "user 
preference".

Léo Gillot-Lamure wrote:
> Hi.
> 
> From what I understand, there are plans for a system compositor laying
> between the kernel and the user compositor, enabling things such as
> fancy Fast User Switching and making it easier to create new
> WMs/compositors as they would only need to speak wayland protocol on
> each side instead of speaking drm+evdev+wayland.
> Thus it will be the system compositor that will choose the screen mode
> and that will do the translation evdev->wayland input event, using
> libxkbcommon and a specific keymap.
> The problem is that the screen mode and the keymap are user settings,
> not system settings. What are the plans to manage that ?
> 
> Regards,
> 
> Léo Gillot-Lamure.
> 
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel