|
|
|
|
*.deps
|
|
|
|
|
*.jpg
|
|
|
|
|
*.la
|
|
|
|
|
*.lo
|
|
|
|
|
*.log
|
|
|
|
|
*.o
|
|
|
|
|
*.pc
|
|
|
|
|
*.so
|
|
|
|
|
*.swp
|
|
|
|
|
.*.sw?
|
|
|
|
|
.sw?
|
|
|
|
|
*.sublime-project
|
|
|
|
|
*.sublime-workspace
|
|
|
|
|
*.trs
|
|
|
|
|
*~
|
|
|
|
|
ctags
|
|
|
|
|
cscope.out
|
|
|
|
|
.libs
|
|
|
|
|
.dirstamp
|
|
|
|
|
/aclocal.m4
|
|
|
|
|
/autom4te.cache
|
|
|
|
|
/build-aux/
|
|
|
|
|
/config.guess
|
|
|
|
|
/config.h
|
|
|
|
|
/config.h.in
|
|
|
|
|
/config.log
|
|
|
|
|
/config.mk
|
|
|
|
|
/config.status
|
|
|
|
|
/config.sub
|
|
|
|
|
/configure
|
|
|
|
|
/depcomp
|
|
|
|
|
/install-sh
|
|
|
|
|
/libtool
|
|
|
|
|
/ltmain.sh
|
|
|
|
|
/logs
|
|
|
|
|
/missing
|
|
|
|
|
/stamp-h1
|
|
|
|
|
/test-driver
|
|
|
|
|
/weston.ini
|
|
|
|
|
Makefile
|
|
|
|
|
Makefile.in
|
|
|
|
|
TAGS
|
|
|
|
|
protocol/.*.valid
|
|
|
|
|
protocol/*.[ch]
|
|
|
|
|
|
|
|
|
|
00*.patch
|
|
|
|
|
|
|
|
|
|
weston-calibrator
|
|
|
|
|
weston-clickdot
|
|
|
|
|
weston-cliptest
|
|
|
|
|
weston-dnd
|
|
|
|
|
weston-editor
|
|
|
|
|
weston-eventdemo
|
|
|
|
|
weston-flower
|
|
|
|
|
weston-fullscreen
|
|
|
|
|
weston-gears
|
|
|
|
|
weston-image
|
|
|
|
|
weston-nested
|
|
|
|
|
weston-nested-client
|
|
|
|
|
weston-presentation-shm
|
|
|
|
|
weston-resizor
|
|
|
|
|
weston-scaler
|
|
|
|
|
weston-simple-egl
|
|
|
|
|
weston-simple-shm
|
|
|
|
|
weston-simple-touch
|
|
|
|
|
weston-simple-damage
|
|
|
|
|
weston-smoke
|
|
|
|
|
weston-stacking
|
|
|
|
|
weston-subsurfaces
|
|
|
|
|
weston-transformed
|
|
|
|
|
weston-view
|
|
|
|
|
|
|
|
|
|
weston-keyboard
|
|
|
|
|
libtoytoolkit.a
|
|
|
|
|
weston-desktop-shell
|
clients: a reference implementation of UI client how to use ivi-hmi-controller.
- introduces ivi-shell-user-interface.c
This is launched from hmi-controller by launch_hmi_client_process and
invoke a
client process.
The basic flow is as followed,
1/ process invoked
2/ read configuration from weston.ini.
3/ draw png file to surface according to configuration of weston.ini
4/ all parts of UI are ready. request "UI_ready" to draw UI.
5/ Enter event loop
6/ If a surface receives touch/pointer event, followings are invoked
according
to type of event and surface
6-1/ If a surface to launch ivi_application receive touch up, it execs
ivi-application configured in weston.ini.
6-2/ If a surface to switch layout mode receive touch up, it sends a
request,
ivi_hmi_controller_switch_mode, to hmi-controller.
6-3/ If a surface to show workspace having launchers, it sends a
request,
ivi_hmi_controller_home, to hmi-controller.
6-4/ If touch down events happens in workspace,
ivi_hmi_controller_workspace_control is sent to slide workspace.
When control finished, event:
ivi_hmi_controller_workspace_end_control
is received.
Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
10 years ago
|
|
|
weston-ivi-shell-user-interface
|
|
|
|
|
weston-info
|
|
|
|
|
weston-screensaver
|
|
|
|
|
weston-screenshooter
|
|
|
|
|
weston-tablet-shell
|
|
|
|
|
weston-terminal
|
|
|
|
|
weston-multi-resource
|
|
|
|
|
weston-simple-im
|
|
|
|
|
git-version.h
|
|
|
|
|
version.h
|
|
|
|
|
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)
10 years ago
|
|
|
*.ivi
|
|
|
|
|
wcap-decode
|
|
|
|
|
matrix-test
|
|
|
|
|
setbacklight
|
|
|
|
|
weston.1
|
|
|
|
|
weston-drm.7
|
|
|
|
|
weston.ini.5
|
|
|
|
|
|
|
|
|
|
/tests/weston-ivi.ini
|
|
|
|
|
internal-screenshot-00.png
|
