Wayland protocols

[Pier Luigi Fiorini]

On Tuesday 19 August 2014 11:03:48 Martin Gräßlin wrote:
> On Tuesday 19 August 2014 10:51:43 Pier Luigi Fiorini wrote:
> > 
> > *) ksmserver is a Wayland client that binds kf5_shell
> > *) ksmserver is asked to lock (via loginctl, plasmoid or context menu)
> > *) ksmserver calls the kf5_shell.lock request
> > *) kwin hides all surfaces, prevent input and maybe turn the screen off,
> > this is all independent from the greeter being running or not
> > *) kwin emits the prepare_lock_surfaces and ksmserver picks it up
> > *) ksmserver runs the greeter which will create the surfaces
> > *) ksld use set_surface_role to set the lock role on those surfaces
> 
> how does ksld know about the surfaces? They are created by the greeter
> process. If that requires to pass surface information between ksmserver and
> the greeter I'm wondering what we gain compared to letting KWin handle it
> directly.

I mistaken ksld with the greeter.