Is light-weight window manager possible with Wayland?

2013-05-16 Thread Michael Pozhidaev
Hello! Maybe the things I am asking now are well-known but although I have tried to read various materials about Wayland and Weston some details remain unclear for me. I would like to clarify them and would be very grateful for any help! Is creation of light-weight window manager possible for Way

Re: [PATCH 2/2] Move the EDID parsing to its own file

2013-05-16 Thread Graeme Gill
Bill Spitzak wrote: > The Y of the primaries can be used as alternative method of specifying the > whitepoint. (convert the > 3 Yxy colors to XYZ, add them, then convert back to Yxy and the xy is the > whitepoint, I think). Correct, but this assumes the display is perfectly additive. Real world

Re: [RFC] libinputmapper: Input device configuration for graphic-servers

2013-05-16 Thread David Herrmann
Hi Bill On Thu, May 16, 2013 at 7:48 PM, Bill Spitzak wrote: > David Herrmann wrote: > >> /** >> * @INMAP_CAP_ACCELEROMETER >> * Accelerometer interface >> * >> * Accelerometer devices report linear acceleration data as ABS_X/Y/Z >> * and rotational acceleration as ABS_RX/Y/Z. >> * >> * @TODO thi

Re: [PATCH 2/2] protocol: Support scaled outputs and surfaces

2013-05-16 Thread Jason Ekstrand
On May 16, 2013 1:11 PM, "Bill Spitzak" wrote: > > Jason Ekstrand wrote: > >> I still think we can solve this problem better if the clients, instead of providing some sort of pre-scaled buffer that matches the output's arbitrary scale factor, simply told the compositor which output they rendered f

Re: [PATCH 2/2] protocol: Support scaled outputs and surfaces

2013-05-16 Thread Bill Spitzak
Jason Ekstrand wrote: I still think we can solve this problem better if the clients, instead of providing some sort of pre-scaled buffer that matches the output's arbitrary scale factor, simply told the compositor which output they rendered for. That is equivalent to providing a scale factor

Re: [PATCH 2/2] protocol: Support scaled outputs and surfaces

2013-05-16 Thread Bill Spitzak
al...@redhat.com wrote: Coordinates in other parts of the protocol, like input events, relative window positioning and output positioning are still in the compositor space rather than the scaled space. However, input has subpixel precision so you can still get input at full resolution. If I un

Re: [RFC] libinputmapper: Input device configuration for graphic-servers

2013-05-16 Thread Bill Spitzak
David Herrmann wrote: /** * @INMAP_CAP_ACCELEROMETER * Accelerometer interface * * Accelerometer devices report linear acceleration data as ABS_X/Y/Z * and rotational acceleration as ABS_RX/Y/Z. * * @TODO this collides with ABS_X/Y of absolute pointing devices * introduce ABS_ACCELX/Y/Z */

Re: minimized and stick windows

2013-05-16 Thread Bill Spitzak
Pekka Paalanen wrote: For example the floating shared toolbox with 2 main windows. It should only disappear when *both* main windows are minimized. You very conventiently removed my next sentence, where I already took this into account. - pq Sorry, obviously I did not read very carefully:

Re: [PATCH 2/2] protocol: Support scaled outputs and surfaces

2013-05-16 Thread Jason Ekstrand
On May 16, 2013 8:44 AM, wrote: > > From: Alexander Larsson > > This adds the wl_surface.set_buffer_scale request, and a wl_output.scale > event. These together lets us support automatic upscaling of "old" > clients on very high resolution monitors, while allowing "new" clients > to take advantag

[PATCH 2/2] protocol: Support scaled outputs and surfaces

2013-05-16 Thread alexl
From: Alexander Larsson This adds the wl_surface.set_buffer_scale request, and a wl_output.scale event. These together lets us support automatic upscaling of "old" clients on very high resolution monitors, while allowing "new" clients to take advantage of this to render at the higher resolution w

[PATCH 1/2] protocol: Allow output changes to be treated atomically

2013-05-16 Thread alexl
From: Alexander Larsson This add a wl_output.done event which is send after every group of events caused by some property change. This allows clients to treat changes touching multiple events in an atomic fashion. --- protocol/wayland.xml | 12 +++- 1 file changed, 11 insertions(+), 1 de

[PATCH 0/2] Updated scaling patch

2013-05-16 Thread alexl
From: Alexander Larsson Here is a new version of the scaling work, based on the feedback from Pekka. Changes in this version are: * Better documentation in general, and about coordinate spaces in particular. * Scaling is an integer * Updated wl_compository version as needed * Added a flag to w

Re: [RFC] libinputmapper: Input device configuration for graphic-servers

2013-05-16 Thread David Herrmann
Hi Peter On Thu, May 16, 2013 at 7:37 AM, Peter Hutterer wrote: > On Sun, May 12, 2013 at 04:20:59PM +0200, David Herrmann wrote: [..] >> So what is the proposed solution? >> My recommendation is, that compositors still search for devices via >> udev and use device drivers like libxkbcommon. So l

Re: [RFC] libinputmapper: Input device configuration for graphic-servers

2013-05-16 Thread Todd Showalter
On Thu, May 16, 2013 at 1:37 AM, Peter Hutterer wrote: > why are gamepads and joysticks different? buttons, a few axes that may or > may not map to x/y and the rest is device-specific. > this may be in the thread, but I still haven't gone through all msgs here. Joysticks are designed for a d