| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This has run-by-default enabled.
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I99c85373965339a990476eec1772a27cfd360d6c
|
|
- Use Qt/QtWayland to set-up an app_id for the main surface. We use that
surface and pass it to waylandsink. Waylandsink create a sub-surface
with the parent the Qt/QtWayland one.
- Install a handler for handling bus messages With it, it allows to pass
the wl_display with the help of a context and the surface backing up
the Widget.
- Installs a timer to wait for Qt to create/get the xdg_surface and
attach a buffer to it. Without we won't be able receive the commit
for the parent event in order to handle it.
Bug-AGL: SPEC-3382
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I4237b7dad110ce36e3a01226e67cb508b6d9a6d9
|
|
The ilm_init function has moved to the new libilmCommon library in
Wayland IVI extension 2.x, so switch to using the ilmCommon package
config in the application CMakeLists.txt. ilmCommon has a dependency
on ilmControl, so that still gets pulled in.
Change-Id: Id9cefd7cb1ceec826d44011d91ad1f196e7e19b2
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
|
Demo instrument cluster receiver application to receive a h264 stream
sent via RTP from another host running Wayland and Weston with the
gst-recorder feature for streaming a virtual display patched in.
The gstreamer pipeline used is based on what was being used with
gst-launch-1.0 in the previously hand-constructed instrument cluster
demo. The use of vaapisink likely constrains use to Intel based
platforms at present, future work should allow working on other
platforms.
The app/surface.{hpp,cpp} files are adapted from code from
xdg-launcher:
https://gerrit.automotivelinux.org/gerrit/staging/xdg-launcher
Note that they are MIT licensed while all other source files are
Apache 2.0. Other than significant refactoring to ease integration,
the functional differences from the runxdg code in xdg-launcher are
that homescreen support has been removed, as the instrument cluster
platform does not use it, and the logging has been reworked to use the
hmi-debug mechanism used by the windowmanager and homescreen.
There is also an implicit assumption that the windowmanager
configuration is such that the "app" role will map the receiver's
surface to the desired location in the center of the dashboard.
Change-Id: Ieddef6463efb744d9c9c28b1508cc930a32981a4
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
|
Marius Vlad
Scott Murray