[PATCH weston 00/11] XWayland update for 1.0

Tiago Vignatti tiago.vignatti at linux.intel.com
Wed Nov 7 09:06:20 PST 2012

Hi Daniel,

On 11/07/2012 04:51 AM, Daniel Stone wrote:
> Here's the somewhat-delayed XWayland update for 1.0.  With this and my
> updated X server, I've been able to run XWayland just fine under Weston
> from current git master.

I was thinking only about porting XWayland for the new registry scheme 
and the surface atomic commit we've introduced in 0.95 -> 1.0. In fact, 
I've applied on X server these patches:

XWayland: Add init_complete protocol
XWayland: Port to Wayland 1.0 API

and on Weston this one:

XWayland: Only initialise WM on signal from the server

and now XWayland is working like expected against Wayland 1.0. I'm quite 
sure we can even work better the WM initialization (maybe calling
weston_wm_create in the idle handler) and remove the need for the 
init_complete request you're introducing. Moreover, WM initialization 
touches exactly the guts of the work I've been carrying on lately, to 
split it as a client. So we'll be changing it anyway on the next. Then 
you're patching also the resize logic and the decoration drawing on XWM. 
Both I've worked already on xwm-as-a-client and would be changing 
drastically if we go with that solution.

I mean, my point is whether is worth to change that much now for 1.0.x 
only given we have the other XWayland private protocol I've been 
designing done in parallel.



More information about the wayland-devel mailing list