Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Mon, Apr 03, 2017 at 04:08:21PM -0700, Roderick Colenbrander wrote: > Hi Peter, > > Thanks for sharing this proposal. I have some little comments for a later > stage, but would rather discuss some big items first. > > The feedback I will share comes from a couple different angles as we are >

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Mon, Apr 03, 2017 at 10:19:16PM -0500, Joshua Watt wrote: > > > On 04/03/2017 07:22 PM, Peter Hutterer wrote: > > On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote: > > > On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer > > > > > > said: > > > > >

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On 04/03/2017 07:22 PM, Peter Hutterer wrote: On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote: On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer said: If you're going to do this ... why not just do it for keyboards, mice, touch panels etc. too?

Re: [PATCH 1/2] wayland-web: Update documentation for EFL toolkit web page

On Tue, Mar 21, 2017 at 12:56:07PM -0500, Derek Foreman wrote: > On 21/03/17 09:29 AM, Chris Michael wrote: > >This patch updates the documentation for building EFL with wayland > >support on the wayland web site. > > > >Signed-off-by: Chris Michael > >--- > > efl.html |

[PATCH libinput] configure.ac: drop auto-detection of features

During the work with meson I realised auto-detection is not a good solution. Our dependencies should be well-defined for what is considered 'normal' and explicitly defined for any deviation from that normal build. The normal build includes docs, tools, tests, etc. because we expect developers to

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Tue, Apr 04, 2017 at 08:16:03AM +0900, Carsten Haitzler wrote: > On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer > said: > > If you're going to do this ... why not just do it for keyboards, mice, touch > panels etc. too? all these have desktop interactions that

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Fri, 31 Mar 2017 17:29:19 +1000 Peter Hutterer said: If you're going to do this ... why not just do it for keyboards, mice, touch panels etc. too? My point is - the same reasons these other devices don't be lazy and stick their heads in the sand with these other

Re: [RFC wayland-protocols] inputfd - direct input access protocol

Hi Peter, Thanks for sharing this proposal. I have some little comments for a later stage, but would rather discuss some big items first. The feedback I will share comes from a couple different angles as we are interested in Wayland for various different use cases. Originally we had the gamepad

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

Hi Pekka, > you cannot ignore a wl_registry.bind request. Did you ever try to see > what happens? :-) Admittedly, I didn't go that far! > If you do not create a wl_resource when the protocol spec says "this > creates a new object", then if the client ever refers to the > non-created object, it

Re: [PATCH wayland v2 3/4] wayland-util: build/ship as separate shared library

On 21 March 2017 at 10:05, Pekka Paalanen wrote: > On Mon, 20 Mar 2017 18:21:53 + > Emil Velikov wrote: > >> On 17 March 2017 at 13:32, Pekka Paalanen wrote: >> > On Fri, 17 Mar 2017 12:07:45 + >> > Emil Velikov

Re: [PATCH weston] compositor-wayland: Call weston_compositor_exit when receiving an xdg toplevel close event

On 25.03.2017 17:19, Sergi Granell wrote: > Signed-off-by: Sergi Granell > --- > libweston/compositor-wayland.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/libweston/compositor-wayland.c b/libweston/compositor-wayland.c > index 1900ab08..a76dd08e 100644 >

Re: [PATCH v2] configure: add option to disable tests

On 2 April 2017 at 15:12, Yann E. MORIN wrote: > Hello, > > On 2017-03-08 18:25 +0100, Yann E. MORIN spake thusly: >> When building for a product, tests are not needed. >> >> Besides, one test requires a C++ compiler, which is not always >> available. >> >> So, add an

Re: [PATCH v2] configure: better check for the C++ compiler

On 2 April 2017 at 15:11, Yann E. MORIN wrote: > Hello, > > On 2017-03-08 18:23 +0100, Yann E. MORIN spake thusly: >> When a C++ compiler is not found, then AC_PROG_CXX will set CXX to >> 'false'. >> >> However, we test that we can find $CXX, and indeed false exists in >>

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

On Mon, 3 Apr 2017 09:47:50 -0400 (EDT) Olivier Fourdan wrote: > Hi Quentin, > > > I think it may be worth it to add a little safety net: > > “Compositors are required to restrict this interface to Xwayland alone, > > and raise a protocol error for native Wayland clients.”

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

- Original Message - > I was thinking about your “hide global”[1] API, which does kill the > client. It seems like a perfect use of it to me. > > [1] > Hehe, yes, that's precisely the use

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

On 4/3/17 3:47 PM, Olivier Fourdan wrote: Hi Quentin, I think it may be worth it to add a little safety net: “Compositors are required to restrict this interface to Xwayland alone, and raise a protocol error for native Wayland clients.” Yes, agreed, good point! But do we really need to kill

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

Hi Quentin, > I think it may be worth it to add a little safety net: > “Compositors are required to restrict this interface to Xwayland alone, > and raise a protocol error for native Wayland clients.” Yes, agreed, good point! But do we really need to kill a client that would dare to try to bind

Re: [PATCH 1/2] Introduce keyboard grabbing protocol for Xwayland

Hey Peter, Thanks for the review! > woohoo, grabs. My favourite topic! ;) > > Mostly ok, a few complaints regarding the documentation but the protocol is > fine from my POV. > > On Wed, Mar 22, 2017 at 05:27:22PM +0100, Olivier Fourdan wrote: > > This patch introduces a new protocol for

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Mon, 2017-04-03 at 10:59 +1000, Peter Hutterer wrote: > > Mostly for the archives, Timo Paulssen pointed me to  > https://github.com/denilsonsa/udev-joystick-blacklist > At least for the compositor's side of things this is a good start, > it's > independent of this protocol though. Very

Re: [RFC wayland-protocols] inputfd - direct input access protocol

Hey, On Fri, 2017-03-31 at 12:23 +0300, Pekka Paalanen wrote: > On Fri, 31 Mar 2017 17:29:19 +1000 > Peter Hutterer wrote: > > > + > > +   > > + This event is sent to notify the client of a custom > > property that > > + applies to this device. The

Re: [RFC wayland-protocols] inputfd - direct input access protocol

On Sat, 1 Apr 2017 10:48:40 +1000 Peter Hutterer wrote: > On Fri, Mar 31, 2017 at 12:23:49PM +0300, Pekka Paalanen wrote: > > > + > > > + This event is sent to notify the client of a custom property that > > > + applies to this device. The property is a standard