<div dir="ltr"><div><div>Hi, <br></div>Overall I like that genivi is now a lot more accessible/visible from the outside. I understand the necessity of dealing with layers on a lower level to make use of the efficient blending of display controllers. But that logic should be only implemented within the compositor. Clients should not deal with the set of available layers - their position / size or orientation on screen.<br>
<br>Configuration changes are far more simpler (read: flicker free) to implement when those are only done in one process, with wayland that would be the compositor. In the case of automotive devices the compositor should also be responsible for drawing the main user interface. So the compositor would be well aware of the current scene assembly - like displayed applications. The applications would only deal with providing buffer content. <br>
<br>In the end integrating navigation, camera 3rd party application windows (instead of layers) should be a lot easier.<br><br></div><div>regards<br>Andreas<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/4 Nobuhiko Tanibata <span dir="ltr"><<a href="mailto:NOBUHIKO_TANIBATA@xddp.denso.co.jp" target="_blank">NOBUHIKO_TANIBATA@xddp.denso.co.jp</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff">
<div><font face="MS UI Gothic">Hi,</font></div><font face="MS UI Gothic">
<div><br>This series implements ivi-shell to fulfill use cases of In-Vehicle
Infotainment, IVI. Such use cases are well overviewed in a project; Genivi IVI
layer management.<br><a href="http://projects.genivi.org/ivi-layer-management/node/13" target="_blank">http://projects.genivi.org/ivi-layer-management/node/13</a></div>
<div> </div>
<div>A motivation of this series and basis idea are introduced by Ossama at
Automotive Linux Summit 2012 spring. The series implements ivi-shell part.
Additionally, GENIVI LM Client Library at slide 20 is contributed to
ivi-layer-management project to support compatible interfaces for Genivi Layer
management users.<br><a href="http://events.linuxfoundation.org/images/stories/pdf/als2012_othman.pdf" target="_blank">http://events.linuxfoundation.org/images/stories/pdf/als2012_othman.pdf</a></div>
<div> </div>
<div>Before I start implementation of ivi-shell, Core members of Genivi IVI
layer management defined draft of ivi-shell.xml to fulfill requirements of IVI
layer management, inviting Kristian. The series also includes the ivi-shell.xml
with updates I faced in actual implementation.</div>
<div> </div>
<div>Please give me any suggestions.<br></div>
<div>Best regards,</div>
<div>Tanibata</div></font></div>
<br>_______________________________________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a><br>
<br></blockquote></div><br></div>