Re: [PATCH weston 1/2] config-parser: add support for more color formats

On Fri, Oct 21, 2016 at 04:02:15PM +0100, Eric Engestrom wrote: > On Friday, 2016-10-21 12:30:07 +0200, Quentin Glidic wrote: > > Hi, > > > > On 20/10/2016 00:08, Eric Engestrom wrote: > > > Valid colours start with an optional '0x' or '#', followed by: > > > - AARRGGBB > > > - RRGGBB > > > -

[PATCH v4] Add configuration option for no input device.

As it has been discussed in the past [1], running Weston without any input device at launch might be beneficial for some use cases. Certainly, it's best for the vast majority of users (and the project) to require an input device to be present, as to avoid frustration and hassle, but for those

Re: [PATCH v3] Add configuration option for no input device.

Hi, On 20 October 2016 at 23:12, Daniel Díaz wrote: > As it has been discussed in the past [1], running Weston > without any input device at launch might be beneficial for > some use cases. > > Certainly, it's best for the vast majority of users (and > the project) to

Re: [PATCH weston 1/2] config-parser: add support for more color formats

On Friday, 2016-10-21 12:30:07 +0200, Quentin Glidic wrote: > Hi, > > On 20/10/2016 00:08, Eric Engestrom wrote: > > Valid colours start with an optional '0x' or '#', followed by: > > - AARRGGBB > > - RRGGBB > > - A R G B > > -R G B > > - XYXYXY > > - XX > > I think this is way

Re: [PATCH weston 1/2] config-parser: add support for more color formats

Hi, On 20/10/2016 00:08, Eric Engestrom wrote: Valid colours start with an optional '0x' or '#', followed by: - AARRGGBB - RRGGBB - A R G B -R G B - XYXYXY - XX I think this is way too much, even with minimal code effort. The well-known CSS formats are #RRGGBB and #RGB, and