Re: autostart of app(s) while weston starts

2015-06-24 Thread Pekka Paalanen
On Wed, 24 Jun 2015 09:25:36 -0700 Bill Spitzak wrote: > On Wed, Jun 24, 2015 at 2:05 AM, Pekka Paalanen wrote: > > > On Wed, 24 Jun 2015 09:40:51 +0200 > > Christian Hartmann wrote: > > > > > Hi, > > > > > > is it possible to autostart of app(s) while weston starts ?? > > > Would be nice to h

[PATCH libinput] filter: reduce deceleration to minimal speeds only

2015-06-24 Thread Peter Hutterer
Deceleration at low speeds is intended to enhance precision when moving the pointer slowly. However, the adaptive deceleration we used was badly calibrated, at slow-but-normal speeds the pointer became too slow to manouver. We don't want to drop deceleration completely, the subpixel precision it p

Re: [PATCH libinput v3 3/5] litest: add nexus4 style touch screen without orientation

2015-06-24 Thread Peter Hutterer
On Mon, Jun 22, 2015 at 12:48:06PM +0200, Andreas Pokorny wrote: > This device provides a circular touch point size and and hence lacks > orientation. It will be used to test default value handling. > > Signed-off-by: Andreas Pokorny 1-4 are Reviewed-by: Peter Hutterer , no need to resend them,

Re: [PATCH libinput v3 5/5] libinput: add orientation and size of touch point and pressure to the API

2015-06-24 Thread Peter Hutterer
On Mon, Jun 22, 2015 at 12:48:08PM +0200, Andreas Pokorny wrote: > This change adds four new properties to touch events. > major: diameter of the touch ellipse along the major axis > minor: diameter perpendicular to major axis > pressure: a pressure value mapped into the range [0,1] > orientation:

[PATCH v2 wayland] protocol: add wl_pointer.axis_frame events

2015-06-24 Thread Peter Hutterer
To group separate vertical/horizontal scroll events together. Likewise it enables axis_stop events to be grouped so that the final vector for kinetic scrolling may be calculated correctly. Signed-off-by: Peter Hutterer --- Changes to v1: - drop the option of having multiple axis sources within th

RE: [PATCH 14/14] tests: test set for ivi-shell notification with bad condition in server side

2015-06-24 Thread Tanibata, Nobuhiko (ADITJ/SWG)
Hi Jon, Thank you for your effort to review them! Best regards, Nobuhiko Tanibata > -Original Message- > From: wayland-devel > [mailto:wayland-devel-boun...@lists.freedesktop.org] On Behalf Of Jon > A. Cruz > Sent: Thursday, June 25, 2015 2:05 AM > To: Nobuhiko Tanibata; wayland-devel@li

Re: libinput: proposed patch to remove fake_resolution tests

2015-06-24 Thread Bill Spitzak
Oops. Updated patch to remove an obvious error (I used the inverse of the ratio). Also changed to assume the device units are square and thus the resolution is the same in both directions, rather than guessing as to the shape of the device. And fixed some incorrect replacement of tab with spaces.

libinput: proposed patch to remove fake_resolution tests

2015-06-24 Thread Bill Spitzak
Searching for uses of fake_resolution and equating the two results gives scale factors between resolution and the controller range (called width and height here): evdev-mt-touchpad-buttons.c:535 bottom_area.top_edge height * 0.15 / yres <= 10 (to choose the same branch as fake does now)

Re: [PATCH 14/14] tests: test set for ivi-shell notification with bad condition in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:37 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation, > Following features are tested, > - add notification of ivi-layer with bad parameter > - add notification of ivi-surfac

Re: [PATCH 12/14] tests: test set for ivi-shell notification normal use case in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:36 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation. > Following features are tested, > - notification of adding ivi-layer > - notification of creating ivi-layer > - notific

Re: [PATCH 13/14] tests: test set for ivi-shell notification in bad condition with helper client

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:36 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > helper client. > Following features are tested, > - add notfication of ivi-surface with bad condition > > Signed-off-by: Nobuhiko Tanibata > Revie

Re: [PATCH 11/14] tests: test set for ivi-shell notification normal use case with helper client

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:35 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > helper client. > Following features are tested, > - notification of adding ivi-surface > - notification of ivi-surface configure > - notificat

Re: [PATCH 10/14] tests: make the test context persistent

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:35 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > The TESTs in ivi_layout-test.c may have several server-side parts > (RUNNER_TEST in ivi_layout-test-plugin.c) each. Sometimes we need to > carry state from one RUNNER_TEST to another within one TEST, but not > across m

Re: [PATCH 09/14] tests: test set for ivi-screen with bad condition in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:35 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation, > Following features are tested, > - ivi-screen operation with bad parameter > - render order with bad parameter > - des

Re: [PATCH 09/14] tests: test set for ivi-screen with bad condition in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:35 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation, > Following features are tested, > - ivi-screen operation with bad parameter > - render order with bad parameter > - des

Re: [PATCH 08/14] tests: test set for ivi-screen normal use case in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:35 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation. > Following features are tested, > - ivi-screen id > - ivi-screen resolution > - render order of ivi-layers in ivi-scree

Re: [PATCH 05/14] tests: test set for ivi-layer normal use case in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:34 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation. > Following features are tested for ivi-layer, > - create > - visibility > - opacity > - orientation > - dimension > - p

Re: [PATCH 07/14] tests: test set for ivi-layer with bad condition in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:35 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation. > Following features are tested for ivi-layer, > - create with bad parameter > - visibility with bad parameter > - opaci

Re: [PATCH 06/14] tests: test set for ivi-layer bad condition with helper-client

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:34 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > helper client. > Following features are tested, > - bad render order of ivi-surface on ivi-layer > - call commitchanges after a ivi_surface in rende

Re: [PATCH 04/14] tests: test set for ivi-layer normal use case with helper client

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:34 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These test are implemented on test suite framework, which provides > helper client. > Following features are tested, > - render order of ivi-surfaces on ivi-layer > > Signed-off-by: Nobuhiko Tanibata > Reviewed-by: P

Re: [PATCH 02/14] tests: test set for ivi-surface bad condition with helper client

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:33 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > helper client. > Following features are tested, > - ivi_layout_runner with basic_test_names[] > - surface with bad opacity > - destroy ivi/wl_surfa

Re: [PATCH 03/14] tests: test set for ivi-surface with bad condition in server side

2015-06-24 Thread Jon A. Cruz
On 06/21/2015 11:33 PM, Nobuhiko Tanibata wrote: > From: Nobuhiko Tanibata > > These tests are implemented on test suite framework, which provides > internal method validation. > Following features are tested for ivi-surface, > - destination_rectangle with bad parameter > - orientation with bad p

Re: [PATCH 01/14] tests: test set for ivi-surface normal use case with helper client

2015-06-24 Thread Jon A. Cruz
With those details explained, this looks good. Reviewed-by: Jon A. Cruz On 06/23/2015 05:56 AM, Pekka Paalanen wrote: > On Mon, 22 Jun 2015 17:28:23 -0700 > "Jon A. Cruz" wrote: > >> On 06/21/2015 11:33 PM, Nobuhiko Tanibata wrote: >>> From: Nobuhiko Tanibata >>> >>> These tests are implemen

Re: [PATCH wayland] RFC: Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-06-24 Thread Jasper St. Pierre
I'm for it as well. On Wed, Jun 24, 2015 at 9:53 AM, Dima Ryazanov wrote: > Bringing this up again. What do you guys think? Does it make sense to push > this change? > > On Wed, May 27, 2015 at 1:50 AM, Dima Ryazanov wrote: >> >> (Oops, sent too soon by accident.) >> >> Yep, DISPLAY always needs

Re: [PATCH v4 1/6] Added simple unit/integration test framework and corresponding test program.

2015-06-24 Thread Jon A. Cruz
On 06/24/2015 09:32 AM, Bill Spitzak wrote: > On Tue, Jun 23, 2015 at 9:55 PM, Jon A. Cruz wrote: > >> >> Looking into it more, I think I've figured out much of that on my part >> comes from C++ and other OO languages I've worked in. Especially with >> C++ one should start a class declaration wit

Re: [PATCH wayland] RFC: Require WAYLAND_DISPLAY to be set instead of using wayland-0 as the default

2015-06-24 Thread Dima Ryazanov
Bringing this up again. What do you guys think? Does it make sense to push this change? On Wed, May 27, 2015 at 1:50 AM, Dima Ryazanov wrote: > (Oops, sent too soon by accident.) > > Yep, DISPLAY always needs to be set - and I figured, there's a reason it > is that way, so that's actually why I

Re: autostart of app(s) while weston starts

2015-06-24 Thread Bill Spitzak
On Wed, Jun 24, 2015 at 2:05 AM, Pekka Paalanen wrote: > On Wed, 24 Jun 2015 09:40:51 +0200 > Christian Hartmann wrote: > > > Hi, > > > > is it possible to autostart of app(s) while weston starts ?? > > Would be nice to have such an feature, if its not present yet, > > I can sent an email to way

Re: [PATCH v4 1/6] Added simple unit/integration test framework and corresponding test program.

2015-06-24 Thread Bill Spitzak
On Tue, Jun 23, 2015 at 9:55 PM, Jon A. Cruz wrote: > > Looking into it more, I think I've figured out much of that on my part > comes from C++ and other OO languages I've worked in. Especially with > C++ one should start a class declaration with a single 'public' section > followed optionally by

Re: [PATCH weston] compositor: Separate hardcoded backend related code from compositor

2015-06-24 Thread JoonCheol Park
Thanks pq and all, I didn't think this would be hot topic :-) All reply from all in this thread was very very helpful to understand current weston project for me. 2015-06-24 16:52 GMT+09:00 Pekka Paalanen : > Hi all > > TL;DR: > > Everything is open, let's make small steps only, in priority ord

[PATCH weston] text_backend: make destructor call explicit

2015-06-24 Thread Pekka Paalanen
From: Pekka Paalanen We used to rely on the order in which the weston_compositor::destroy_signal callbacks happened, to not access freed memory. Don't know when, but this broke at least with ivi-shell, which caused crashes in random places on compositor shutdown. Valgrind found the following:

Re: [PATCH v2 weston 00/16] Atomic modesetting support

2015-06-24 Thread Pekka Paalanen
Hello On Wed, 24 Jun 2015 12:22:15 +0100 Daniel Stone wrote: > Hi, > > On 23 June 2015 at 13:28, Pekka Paalanen wrote: > > On Tue, 23 Jun 2015 11:48:56 +0100 > > Daniel Stone wrote: > >> > So, the DRM planes we have not assigned yet but were enabled, shouldn't > >> > they be disabled in the

Re: [PATCH v2 weston 00/16] Atomic modesetting support

2015-06-24 Thread Daniel Stone
Hi, On 23 June 2015 at 13:28, Pekka Paalanen wrote: > On Tue, 23 Jun 2015 11:48:56 +0100 > Daniel Stone wrote: >> This is the reason for the large 'XXX' comment when calling >> populate_atomic_plane inside repaint_atomic. So far, my thought has >> been to add yet another parameter (ugh) to popul

Re: autostart of app(s) while weston starts

2015-06-24 Thread Pekka Paalanen
On Wed, 24 Jun 2015 09:40:51 +0200 Christian Hartmann wrote: > Hi, > > is it possible to autostart of app(s) while weston starts ?? > Would be nice to have such an feature, if its not present yet, > I can sent an email to wayland-devel-request :) *if its not done > already by another user* It's

Re: [PATCH weston] compositor: Separate hardcoded backend related code from compositor

2015-06-24 Thread Pekka Paalanen
Hi all TL;DR: Everything is open, let's make small steps only, in priority order determined by the intended audience. We have as many release cycles of time to use for improving the code and interfaces as we want. On Wed, 24 Jun 2015 02:40:08 +0900 JoonCheol Park wrote: > Hi Giulio, pq! > >

autostart of app(s) while weston starts

2015-06-24 Thread Christian Hartmann
Hi, is it possible to autostart of app(s) while weston starts ?? Would be nice to have such an feature, if its not present yet, I can sent an email to wayland-devel-request :) *if its not done already by another user* greetings, chris ___ wayland-devel