Automotive Linux Wiki

This is an old revision of the document!

Review target: https://wiki.automotivelinux.org/_media/eg-ui-graphics/170606_agl_hmi-fw_arch_0_2_3.pdf

* Nobuhiko Tanibata
  * When layout change is triggered by Homescreen, efficient transition animation of surfaces shall be supported.

• Takashi Matsuzawa
  • The document should describe which part of it is mandatory and which parts are optional/selectable (e.g. I understand that 2 windows up/down layout is just one example of OEM profile - though it is very good that we have one example OEM profile and demo homescreen/window manager is written for it.)
  • Regarding the API calls apps make, the document (or manual document) should clarify them into the following two categories, so that audience can know which part is AGL specific.
    • API calls/actions that ordinal wayand-ivi apps will do (not specific to AGL)
    • API calls/actions that are specific to AGL
  • Graphics toolkits (e.g. Qt or others) here are expected to hide such API details from application developers or not, including AGL additions?