[PATCH wayland v4 1/5] protocol: define the concept of wl_surface role

[Pekka Paalanen]

On Thu, 21 Aug 2014 09:08:56 -0700
Jason Ekstrand <jason at jlekstrand.net> wrote:

> That applies to the whole series, BTW
> 
> 
> On Thu, Aug 21, 2014 at 9:03 AM, Jason Ekstrand <jason at jlekstrand.net>
> wrote:
> 
> > LGTM
> > Reviewed-by: Jason Ekstrand <jason.ekstrand at intel.com>

Thank you, Jason. :-)

Jasper already acked this in irc, but I would like to get an official
R-b, too.

Then, once we have an implementation for Weston, I can land this. Quite
likely it means after 1.6.0, though, unless I can whip it up today...
quite probably I won't have the time for that, though.


Thanks,
pq

> > On Thu, Aug 21, 2014 at 2:52 AM, Pekka Paalanen
> > <ppaalanen at gmail.com> wrote:
> >
> >> From: Pekka Paalanen <pekka.paalanen at collabora.co.uk>
> >>
> >> Define what a role is, and what restrictions there are.
> >>
> >> A change to existing behaviour is that a role cannot be changed at
> >> all once set. However, this is unlikely to cause problems, as
> >> there is no reason to re-use wl_surfaces in clients.
> >>
> >> v2: give more concrete examples of roles, define losing a role,
> >> Jasper rewrote the paragraph on how a role is set.
> >>
> >> v3: make role permanent, there is no such thing as "losing a role".
> >> Re-issuing the same role again must be allowed for
> >> wl_pointer.set_cursor et al. to work.
> >>
> >> v4: clarify the semantics of destroying a role object.
> >>
> >> Signed-off-by: Pekka Paalanen <pekka.paalanen at collabora.co.uk>
> >> ---
> >>  protocol/wayland.xml | 33 +++++++++++++++++++++++++++++++--