Re: [RFC wayland-protocols] Color management protocol

On Fri, Jan 13, 2017 at 9:03 AM, Pekka Paalanen wrote: > That's an excellent idea! Could you recommend some, so I don't pick a > random "oh, but they're doing it wrong" video? I'd say probably none of them are doing it wrong, but come with editorialization of what's

Re: Monitor profiling (Re: [RFC wayland-protocols] Color management protocol)

On Fri, Jan 13, 2017 at 7:17 AM, Pekka Paalanen wrote: > > If I understand right, the calibrating or monitor profiling process > (are these the same thing?) needs to control the "raw" pixel values > going through the encoder/connector (DRM terminology), hence you need >

Schedule for 1.13 release

Friday the 13th of January seems an auspiciously ominous time to announce the schedule for 1.13. So here's the upcoming dates: - 1.10-alpha around Jan 24th. Major features done by this point. - 1.10-beta in first week of February. - 1.10-rc1 around Feb 14th. - Additional rc's as

Re: Schedule for 1.13 release

Lets try that again: Friday the 13th of January seems an auspiciously ominous time to announce the schedule for 1.13. So here's the upcoming dates: - 1.13-alpha around Jan 24th. Major features done by this point. - 1.13-beta in first week of February. - 1.13-rc1 around Feb 14th.

Re: [RFC wayland-protocols] Color management protocol

Hello, It's very difficult to contribute to this discussion, but here is my delta contribution. I agree with the following proposal with comment bellow. On 19/12/2016 09:27, Carsten Haitzler (The Rasterman) wrote: On Mon, 19 Dec 2016 17:01:50 +1100 Graeme Gill said:

Re: Monitor profiling (Re: [RFC wayland-protocols] Color management protocol)

On 13/01/2017 15:17, Pekka Paalanen wrote: the calibrating or monitor profiling process (are these the same thing?) As far as I know, no they are different, calibrating a monitor is the attempt to set cLUT and monitor setting to be close to a given target, often a given color space with a

Re: [RFC wayland-protocols] Color management protocol

Hello Graeme Gill I read many comments on this topic including yours, and I agree with you about some points in particular about the calibration and profiling procedure, but I very puzzled by your position about some points. It's look like you hate display managers[1] because they are not

Re: [RFC wayland-protocols] Color management protocol

On Fri, 13 Jan 2017 18:08:51 +0200 Pekka Paalanen said: > On Fri, 13 Jan 2017 16:37:57 +0100 > Florian Höch wrote: > > > Am 13.01.2017 um 16:19 schrieb Richard Hughes: > > > On 13 January 2017 at 14:56, Florian Höch

Re: [PATCH libinput v2 3/5] Add evdev_dispatch interface for lid switch

On Thu, Jan 12, 2017 at 2:21 PM, Peter Hutterer wrote: doh. not sure how I missed this in the first one, but this needs an extra check for the event code too, otherwise we'll be sending switch lid events for any switch on the device. We filter for SW_LID but if a

Re: [PATCH libinput 0/5] Disable laptop touchpad on lid close

On Thu, Jan 5, 2017 at 4:15 PM, James Ye wrote: Although a laptop touchpad is usually not accessible when the lid is closed, some laptop models suffer from a hardware bug where the touchpad can be activated even if the lid is closed. This bug can be worked around by

Monitor profiling (Re: [RFC wayland-protocols] Color management protocol)

Hi, there is some controversy in whether this belongs in Wayland or not, but if we assume that it does... On Thu, 5 Jan 2017 12:40:08 +1100 Graeme Gill wrote: > Pekka Paalanen wrote: > > > Designing that is trivial: > > I'm not so sure. > > > GLOBAL cms_calibrator

[ANNOUNCE] libinput 1.5.4

libinput 1.5.4 is now available. Patches included are a few fixes with the help output in the tools and improved disable-while-typing. If fingers aren't moving at the beginning of a gesture, we try to detect the gesture based on the finger position. Finally, the Asus X555LAB has a reduced middle

Did Wayland Release Schedule change ?

Hi, The last release v1.12 is released on September 2016. I expected that the v1.13 will be released on Jan 2017. But there are no ongoing release activities, e.g. release candidate tags etc. Did wayland release schedule change ? Best regards Emre Ucan

Re: weston: recommendations for implementing splashscreen in a custom shell?

Hi, On 13 January 2017 at 11:42, Pekka Paalanen wrote: > Weston's desktop-shell uses an event from the helper client to signal > when it is ready, and fades in only after that (if the fade-in > animation is enabled). I understand you want to keep the boot splash > image

Re: weston: recommendations for implementing splashscreen in a custom shell?

On Fri, 30 Dec 2016 15:07:38 -0600 Matt Hoosier wrote: > Hi, > > I maintain a small Weston shell plugin for an an embedded use-case. On the > embedded device, the bootloader first paints a buffer and installs it as > the scanout buffer to the graphics hardware. At some

Re: App GUI positioning in Desktop-shell for weston

On Wed, 28 Dec 2016 18:58:23 +0530 Ajmal wrote: > -Original Message- > From: "Ajmal" > Sent: ‎28-‎12-‎2016 06:53 PM > To: "wayland-devel@lists.freedesktop.org" > > Subject: App GUI positioning in

Re: [RFC wayland-protocols] Color management protocol

On Thu, 5 Jan 2017 12:51:58 +1100 Graeme Gill wrote: > Pekka Paalanen wrote: > > > I also forgot to mention that surfaces with the cms_calibration_surface > > role, when actually presented, would also guarantee that nothing else > > will be shown on that specific output,

[RFC wayland-protocols] Color management protocol

[ Bunch of replies to different posts crammed into one, apologies in advance. ] Pekka Paalanen wrote: > Would it not be simpler to just say "I'm doing calibration now, make > sure nothing interferes"? Sure, I just hope that "I'm doing calibration now, make sure nothing interferes" still allows

Re: [RFC wayland-protocols] Color management protocol

On 13 January 2017 at 14:56, Florian Höch wrote: > .. also guarantee that nothing else will be shown on that specific output FWIW, I'd be fine just displaying a color swatch on the entire screen with no window decorations; the only reason we use a composited window

Re: [RFC wayland-protocols] Color management protocol

Am 13.01.2017 um 16:19 schrieb Richard Hughes: > On 13 January 2017 at 14:56, Florian Höch > wrote: >> .. also guarantee that nothing else will be shown on that specific output > > FWIW, I'd be fine just displaying a color swatch on the entire screen > with no

Re: [RFC wayland-protocols] Color management protocol

On Fri, 13 Jan 2017 15:56:50 +0100 Florian Höch wrote: > [ Bunch of replies to different posts crammed into one, apologies in > advance. ] > > Pekka Paalanen wrote: > > Would it not be simpler to just say "I'm doing calibration now, make > > sure nothing

Re: [RFC wayland-protocols] Color management protocol

On Fri, 13 Jan 2017 16:37:57 +0100 Florian Höch wrote: > Am 13.01.2017 um 16:19 schrieb Richard Hughes: > > On 13 January 2017 at 14:56, Florian Höch > > wrote: > >> .. also guarantee that nothing else will be shown on that