weston/.gitignore

114 lines
1.4 KiB
Text
Raw Normal View History

*.announce
*.deps
*.jpg
*.la
*.lo
*.log
2008-11-26 04:18:29 +00:00
*.o
*.pc
*.sig
*.so
*.swp
.*.sw?
.sw?
*.sublime-project
*.sublime-workspace
*.tar.xz
*.trs
2008-12-02 20:18:38 +00:00
*~
ctags
cscope.out
.libs
2014-02-02 06:16:43 +00:00
.dirstamp
/aclocal.m4
/autom4te.cache
/build-aux/
/config.guess
/config.h
/config.h.in
/config.log
/config.mk
/config.status
/config.sub
/configure
/depcomp
/doc/doxygen/*.doxygen
/docs/developer
/docs/tools
/install-sh
/libtool
/ltmain.sh
/logs
/missing
/stamp-h1
/test-driver
/weston.ini
Makefile
Makefile.in
TAGS
2013-10-25 19:15:42 +00:00
protocol/.*.valid
2014-02-06 20:43:19 +00:00
protocol/*.[ch]
00*.patch
2014-02-06 20:43:19 +00:00
weston-calibrator
weston-clickdot
weston-cliptest
weston-confine
2014-02-06 20:43:19 +00:00
weston-dnd
weston-editor
weston-eventdemo
weston-flower
weston-fullscreen
weston-gears
weston-image
weston-nested
weston-nested-client
weston-presentation-shm
2014-02-06 20:43:19 +00:00
weston-resizor
weston-scaler
weston-simple-dmabuf-drm
weston-simple-dmabuf-v4l
2014-02-06 20:43:19 +00:00
weston-simple-egl
weston-simple-shm
weston-simple-touch
weston-simple-damage
2014-02-06 20:43:19 +00:00
weston-smoke
weston-stacking
weston-subsurfaces
clients: add a new touchscreen calibrator The new calibrator uses weston_touch_calibration protocol extension and provides the following features: - chooses the physical touch device to be calibrated by DEVPATH or by the output/head name; device enumeration provided - the compositor ensures the calibrator window is shown in the correct position and size - no matter how wrong the old calibration is, the touch events will always arrive in the application - the calibration is complete, not incremental; the received touch events are guaranteed to be unmodified - computes a libinput style calibration matrix directly, not the WL_CALIBRATION format - supports multiple touch devices: calibrate one device at a time, and show user feedback on touching a wrong device instead of recording bad data - uses four touch point samples: three to compute the calibration, and one to verify the calibration is roughly correct - consistent exit codes - upload the new calibration into the server after successful and verified calibration Due to using special touchscreen calibration protocol extension, this application cannot be tested without touch input from the compositor. Practically all of the above mentioned are unlike how the old calibrator client worked. Co-developed by Louis-Francis and Pekka. v2: - improve help() text - rename wrong_touch_handler() to invalid_touch_handler() - improve debug prints by adding sample number - reorganize code into sample funcs vs. touch funcs - add a state machine to properly process touch and related events Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com> Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> v1 Tested-by: Matt Hoosier <matt.hoosier@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-11-29 21:38:44 +00:00
weston-touch-calibrator
2014-02-06 20:43:19 +00:00
weston-transformed
weston-view
weston-keyboard
libtoytoolkit.a
weston-desktop-shell
weston-ivi-shell-user-interface
2014-02-06 20:43:19 +00:00
weston-info
weston-screenshooter
weston-tablet-shell
weston-terminal
weston-multi-resource
weston-simple-im
weston
weston-launch
spring-tool
*.weston
*.test
tests: ivi_layout test infrastructure Testing the ivi_layout API requires two things: - the tests must be written as a controller module to access the API - the tests need a helper client to create some objects that can then be managed via the API This patch adds all the infrastructure and two different kinds of example tests. Internal ivi-shell (ivi_layout) API tests are listed as ivi-*.la files in TESTS in Makefile.am. Weston-tests-env detects these, and runs Weston with ivi-shell, and loads the given module as a controller module, not as a normal plugin. The test controller module ivi-*.la will launch a helper client. For ivi-layout-test.la the helper client is ivi-layout.ivi. The helper client uses the weston-test-runner framework to fork and exec each TEST with a fresh connection to the compositor. The actual test is triggered by the weston_test_runner protocol interface, a new addition to weston-test.xml. The helper client uses weston_test_runner to trigger a test, and the server side of the interface is implemented by the test controller module (ivi-layout-test.la). The server side of weston_test_runner uses the same trick as weston-test-runner.h to gather a list of defined tests. A test is defined with the RUNNER_TEST macro. If a test defined by RUNNER_TEST succeeds, an event is sent to the helper client that it can continue (or exit). If a test fails, a fatal protocol error is sent to the helper client. Once the helper client has iterated over all of its tests, it signals the batch success/failure via process exit code. That is cought in the test controller module, and forwarded as Weston's exit code. In summary: each ivi_layout test is a combination of a client side helper/setup and server side actual tests. v2: Load weston-test.so, because create_client() needs it. v3: add a comment about IVI_TEST_SURFACE_ID_BASE. v4: Rebased to upstream weston-tests-env changes. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Derek Foreman <derekf@osg.samsung.com> (v2)
2015-03-25 10:50:31 +00:00
*.ivi
2014-02-06 20:43:19 +00:00
wcap-decode
matrix-test
setbacklight
weston.1
weston-drm.7
weston.ini.5
/libweston/git-version.h
/libweston/version.h
/tests/weston-ivi.ini
internal-screenshot-00.png
/zuctest