Re: [RFC wayland-protocols] Color management protocol

Carsten Haitzler (The Rasterman) wrote: > i'm curious... is the intent to make it requird that all compositors support > color management (and thus have to support all the possible colorspaces > defined)... or are we going to go the path of: I'd be happy if there was support for core color

Re: [RFC wayland-protocols] Color management protocol

On Fri, 2 Dec 2016 12:30:53 + Daniel Stone said: > Hi Nils, > > On 19 November 2016 at 16:29, Niels Ole Salscheider > wrote: > > it has been some time since I proposed the first two RFCs for a color > > management protocol in weston.

Re: [RFC wayland-protocols] Color management protocol

Niels Ole Salscheider wrote: > Therefore I think that the situation has changed and I'd like to propose this > protocol for inclusion in wayland-protocols again. > What do you think? Hi, I'm prompted to look into the current state of color management in Wayland, by Richard Hughes comment

Re: [RFC wayland-protocols] Add the color-management protocol

Niels Ole Salscheider wrote: Hi, > The ICC profiles to which the zwp_colorspace objects point can be compared > easily: Each ICC profile contains an unique 128 bit fingerprint in the header > so > that only this fingerprint has to be compared. actually, this isn't true. The MD5 fingerprint

Re: [RFC wayland-protocols] Color management protocol

Niels Ole Salscheider wrote: Hi, > The first version of my proposal had such a flag. I removed it and replaced > it > by the described version based on feedback from Zoxc (zox...@gmail.com). Do you have a link to the specifics ? > I can see advantages with both solutions. One advantage with

[PATCH weston v2] xwm: Add icon support to the frame

This fetches the _NET_WM_ICON property of the X11 window, and use the first image found as the frame icon. This has been tested with various X11 programs, and improves usability and user-friendliness a bit. Changes since v1: - Changed frame_button_create() to use

Re: [RFC PATCH 0/8] Meson build system [for libinput this time]

On Tue, Nov 29, 2016 at 04:59:39PM +, Daniel Stone wrote: > [meson is like totally super duper] I tried the same for libinput, work available in https://github.com/whot/libinput/tree/wip/meson I think I'm about 80% of the way there, with more testing needed and a few details being

Re: How to handle DRM crtc_id, connector_id greater than 31

On Wed, 7 Dec 2016 13:30:34 +0200 Pekka Paalanen wrote: > * PGP Signed by an unknown key > > On Tue, 6 Dec 2016 16:21:30 -0800 > Miguel Angel Vico wrote: > > > Hi Eric, > > > > The problem here is we are using crtc_id and connector_id as > >

Re: [PATCH weston] xwm: Add icon support to the frame

On Sunday, 2016-12-04 21:20:47 +, Emmanuel Gil Peyrot wrote: > This fetches the _NET_WM_ICON property of the X11 window, and use the > first image found as the frame icon. > > This has been tested with various X11 programs, and improves usability > and user-friendliness a bit. > >

[TASK] Trivial libs related fixes (Was Re: [PATCH weston 2/6] libweston: Use the monotonic clock in weston_compositor_get_time)

Hi Dima, Your patch reminded me a few trivial fixes/cleanups. In case you/others feel like sorting out some low hanging fruit ;-) - wayland: bring WESTON_SEARCH_LIBS check for dlopen (libdl) and clock_gettime (librt). - weston: replace WESTON_SEARCH_LIBS([JPEG] ...) with

Re: How to handle DRM crtc_id, connector_id greater than 31

On Tue, 6 Dec 2016 16:21:30 -0800 Miguel Angel Vico wrote: > Hi Eric, > > The problem here is we are using crtc_id and connector_id as indexes, > while they aren't. > > Nothing keeps DRM drivers from advertising CRTC and connectors with ids > that aren't sequential and

[PATCH weston] libweston-desktop: don't crash when getting the pid for X clients

X client's don't have a wl_client associated with their weston_desktop_client_create, so check that it is valid. Signed-off-by: Giulio Camuffo --- libweston-desktop/surface.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git