Wayland and Weston 1.0.3 releases out

Hello, We now have the weston test suite under control and as promised, here's the 1.0.3 release with those fixes: f71a3fb5b6534cce35ac7456a5fd540fc3806fc1 wayland-1.0.3.tar.xz ce1f41251a07600ed8c6b2e3dc1e868008aeb33a wayland 1.0.3 tag 583589cf7dd8f3300eef2bfb7b1968875a155e2a west

Re: [PATCH wayland] protocol: Add set_xwayland request for new shell surface type

On 12/14/2012 06:12 AM, Pekka Paalanen wrote: On Thu, 13 Dec 2012 14:13:04 -0200 Tiago Vignatti wrote: I don't see a problem on having xwayland typical applications linked with "desktop" style of interfaces. X11 and its WM standards are flexible enough for building different graphics interface

Re: [PATCH 0/8] Fixes for fullscreen with "driver" method

On Fri, Dec 14, 2012 at 01:37:22PM -0200, Ander Conselvan de Oliveira wrote: > From: Ander Conselvan de Oliveira > > There were a few bugs with this feature. The first two patches make > transformed optionally use that fullscreen method. The next four > patches fixes bugs that prevented that for

[PATCH 8/8] compositor-drm: Reduce code duplication on drm_output_switch_mode()

From: Ander Conselvan de Oliveira Call drm_output_init_egl() instead of duplicating the gbm surface and gl renderer state initialization code. Note that this makes error handling a bit worse. Before, if we failed to allocate a gbm surface we could still recover. Failing the renderer state creati

[PATCH 7/8] compositor-drm: Move output gl state initialization to own function

From: Ander Conselvan de Oliveira --- src/compositor-drm.c | 59 ++ 1 file changed, 36 insertions(+), 23 deletions(-) diff --git a/src/compositor-drm.c b/src/compositor-drm.c index 1aec473..d443c63 100644 --- a/src/compositor-drm.c +++ b/src/com

[PATCH 6/8] compositor-drm: Don't do a mode set on drm_output_switch_mode()

From: Ander Conselvan de Oliveira At this point, we reallocated the gbm surface, but we don't have an fb with the right size to use. If we're going to a larger mode, the fb would be too small and the mode set would fail. Besides, the repaint logic will already do a mode set if necessary, so rely

[PATCH 5/8] compositor-drm: Fix a return value check in drm_output_switch_mode()

From: Ander Conselvan de Oliveira gl_rederer_output_create() returns 0 on success, but drm compositor would consider this a failure. --- src/compositor-drm.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/compositor-drm.c b/src/compositor-drm.c index 3f2cd0c..22a3ac8

[PATCH 4/8] compositor: Don't let pointers get outside of an output on mode switch

From: Ander Conselvan de Oliveira When an output suffers a mode switch, it is possible that a pointer was inside the old output area but falls outside of it with the new size. In that case, move the cursor to the output's bottom-right corner. Otherwise, there's a crash in clip_pointer_motion(). -

[PATCH 3/8] compositor: Update output state after mode switch

From: Ander Conselvan de Oliveira After a mode switch, the output region and transformation matrix need to be updated. The call to weston_output_move() would do the former but not the latter, but calling that when the output remains in the same coordinate doesn't make much sense. Instead, update

[PATCH 2/8] transformed: Add options for using debuging driver fullscreen method

From: Ander Conselvan de Oliveira Add options for setting width, height and using the driver fullscreen method. --- clients/transformed.c | 57 ++--- 1 file changed, 54 insertions(+), 3 deletions(-) diff --git a/clients/transformed.c b/clients/trans

[PATCH 1/8] window: Allow clients to choose the fullscreen method

From: Ander Conselvan de Oliveira --- clients/window.c | 11 ++- clients/window.h |3 +++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/clients/window.c b/clients/window.c index 29f6c87..0bc9526 100644 --- a/clients/window.c +++ b/clients/window.c @@ -219,6 +219,7

[PATCH 0/8] Fixes for fullscreen with "driver" method

From: Ander Conselvan de Oliveira There were a few bugs with this feature. The first two patches make transformed optionally use that fullscreen method. The next four patches fixes bugs that prevented that for working and the last two patches refactors code to reduce code duplication in that path

Re: Sub-surface protocol

On 12/14/2012 12:29 AM, John Kåre Alsaker wrote: > On Thu, Dec 13, 2012 at 11:47 PM, Bill Spitzak wrote: > >> It will also force the floating >> window api to allow the client to be in final control of the stacking order, >> a deficiency in all existing window systems. > Do you have an example of

Re: Sub-surface protocol

On Thu, 13 Dec 2012 12:33:33 -0500 Kristian Høgsberg wrote: > On Thu, Dec 13, 2012 at 04:07:44PM +0100, John Kåre Alsaker wrote: > > > > On Thu, Dec 13, 2012 at 3:30 PM, Pekka Paalanen wrote: > > > > > > On Thu, 13 Dec 2012 14:51:17 +0100 > > > John Kåre Alsaker wrote: > > > > > >> I see that

Re: Sub-surface protocol

On Thu, 13 Dec 2012 14:47:57 -0800 Bill Spitzak wrote: > FLOATING WINDOWS: > > PLEASE consider reusing this code for "floating windows". THEY ARE THE > SAME THING!!! The only difference is that the compositor can insert > other surfaces between floating children and the parent. > > This would

Re: [PATCH wayland] protocol: Add set_xwayland request for new shell surface type

On Thu, 13 Dec 2012 15:10:25 -0800 Bill Spitzak wrote: > Tiago Vignatti wrote: > > > About the availability of it to regular Wayland clients, I agree, it's a > > problem. Bill Spitzak pointed this out on the previous set. It sets a > > bad example because it exposes global position to all regu

Re: [PATCH wayland] protocol: Add set_xwayland request for new shell surface type

On Thu, 13 Dec 2012 14:13:04 -0200 Tiago Vignatti wrote: > > On 12/13/2012 05:38 AM, Pekka Paalanen wrote: > > > > On Wed, 12 Dec 2012 13:26:33 -0200 > > Tiago Vignatti wrote: > > > >> X11 apps use global coordinates most of the time for window placement and > >> the > >> current approach we h