mainnika
/
weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6900 Commits
1 Branch
0 Tags
14 MiB
Tag: Branch: Tree: 5a701547a4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5a701547a4'
${ noResults }
weston/ivi-shell/weston.ini.in

99 lines
2.0 KiB
Raw Normal View History Unescape

ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[core]
tests: Reshuffle IVI layout tests Rename the IVI tests to be more consistent with the others, and invert the naming of plugin/client to make it slightly more clear what's going to happen. Handle the renaming by using wet_get_binary_path to rewrite the local binaries. As a side-effect, weston.ini ivi-shell-user-interface no longer needs to be given as an absolute path. Signed-off-by: Daniel Stone <daniels@collabora.com> v2: Call ivi-layout.ivi as ivi-layout-test-client.ivi to keep the same name in both the file and the lookup, so that the module map does not need to change the name. Update code comments to reflect the new names. Rename ivi_layout-test-plugin.c to ivi-layout-test-plugin.c. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
9 years ago
shell=ivi-shell.so
modules=hmi-controller.so
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-shell]
tests: Reshuffle IVI layout tests Rename the IVI tests to be more consistent with the others, and invert the naming of plugin/client to make it slightly more clear what's going to happen. Handle the renaming by using wet_get_binary_path to rewrite the local binaries. As a side-effect, weston.ini ivi-shell-user-interface no longer needs to be given as an absolute path. Signed-off-by: Daniel Stone <daniels@collabora.com> v2: Call ivi-layout.ivi as ivi-layout-test-client.ivi to keep the same name in both the file and the lookup, so that the module map does not need to change the name. Update code comments to reflect the new names. Rename ivi_layout-test-plugin.c to ivi-layout-test-plugin.c. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
9 years ago
ivi-shell-user-interface=weston-ivi-shell-user-interface
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
ivi-shell: developer mode debug key bindings Add a weston.ini option for ivi-shell to enable "developer mode". When developer mode is enabled, hook up the debug key bindings. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Acked-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Daniel Stone <daniels@collabora.com>
11 years ago
#developermode=true
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
cursor-theme=default
cursor-size=32
base-layer-id=1000
hmi-controller: allocate base layers for multi-screen A layer ID for screen is set by key: base-layer-id at weston.ini. To support multi screens. It also support offset to offset the layer ID to next ID for next screen. For example, base-layer-id=1000 base-layer-id-offset=10000 Layer id for screen 0: 1000 Layer id for screen 1: 11000 Layer id for screen 2: 21000 To support multi screen, create layers for background and panel bar which located in the below per screens. At the moment, it is only layers. Surfaces to be created at next patch in the patch set. Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
10 years ago
base-layer-id-offset=10000
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
workspace-background-layer-id=2000
workspace-layer-id=3000
application-layer-id=4000
transition-duration=300
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
background-image=@westondatadir@/background.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
background-id=1001
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
panel-image=@westondatadir@/panel.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
panel-id=1002
hmi-controller: allocate background surfaces for multi-screen A surface ID for layer of background/panel image is set by key: background-id or panel-id at weston.ini. To support multi screens, it also support offset, surface-id-offset, to offset the surface ID to next ID for a layer on next screen. According to the above key, hmi-controller and ivi-shell-user-interface who increments the number of screens per notification of wl_output. crate surface and draw background/panel image on multi surface on screens. Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
10 years ago
surface-id-offset=10
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
tiling-image=@westondatadir@/tiling.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
tiling-id=1003
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
sidebyside-image=@westondatadir@/sidebyside.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
sidebyside-id=1004
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
fullscreen-image=@westondatadir@/fullscreen.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
fullscreen-id=1005
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
random-image=@westondatadir@/random.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
random-id=1006
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
home-image=@westondatadir@/home.png
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
home-id=1007
workspace-background-color=0x99000000
workspace-background-id=2001
[ivi-launcher]
workspace-id=0
icon-id=4001
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_flower.png
path=@bindir@/weston-flower
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=0
icon-id=4002
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_clickdot.png
path=@bindir@/weston-clickdot
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=1
icon-id=4003
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_simple-egl.png
path=@bindir@/weston-simple-egl
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=1
icon-id=4004
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_simple-shm.png
path=@bindir@/weston-simple-shm
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=2
icon-id=4005
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_smoke.png
path=@bindir@/weston-smoke
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=3
icon-id=4006
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_flower.png
path=@bindir@/weston-flower
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=3
icon-id=4007
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_clickdot.png
path=@bindir@/weston-clickdot
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=3
icon-id=4008
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_simple-egl.png
path=@bindir@/weston-simple-egl
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=3
icon-id=4009
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_simple-shm.png
path=@bindir@/weston-simple-shm
ivi-shell: a reference of weston.ini for ivi-shell and ivi-hmi-controller. - introduces ivi-shell/weston.ini.in Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
11 years ago
[ivi-launcher]
workspace-id=3
icon-id=4010
ivi-shell: use install paths in example config The example weston.ini file uses source and build directory paths. Therefore, it is only useful when used on the same system that is used to build Weston. We can use install paths instead of build/source paths to fix this problem. v2 changes: - use $(westondatadir) instead of $(datadir) Reported-by: Michael Tretter <m.tretter@pengutronix.de> Signed-off-by: Emre Ucan <eucan@de.adit-jv.com> Reviewed-by: Michael Tretter <m.tretter@pengutronix.de> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com>
8 years ago
icon=@westondatadir@/icon_ivi_smoke.png
path=@bindir@/weston-smoke