Experiences Developing a Wayland-Based IVI HMI - The Linux ...

More documents

Recommendations

Info

Server Side Architectures• HMI Service• Stand-alone• Integrated• Server side architecture remains transparent to the client• Just an implementation detail from the client point of view• Client does not determine where surfaces are placed12
Stand-alone HMI Service• HMI service is another Wayland basedclient• Separate process from compositor• Communicates with compositor just asclient application would• Example: GENIVI style layermanagement13
Page 1 and 2: Experiences Developing aWayland Bas
Page 3: Problems• Mobile and desktop user
Page 6 and 7: HMI Service• Provides “home scr
Page 8 and 9: Application Run-time• Provides re
Page 10 and 11: 10Component Structure
Page 14 and 15: Stand-alone HMI Service - Sequence
Page 16 and 17: Integrated HMI Service - Sequence D
Page 18 and 19: 18HTML5 HMI Problems
Page 20 and 21: Problem: Gap Between HTML5 and Nati
Page 22 and 23: Solution• Compositor• Plugin ex
Page 24 and 25: Desktop Shell-isms• Direct use of
Page 26 and 27: Summary• Wayland• Simple, light
Page 28: LegalINFORMATION IN THIS DOCUMENT I

Experiences Developing a Wayland-Based IVI HMI - The Linux ...

Create successful ePaper yourself

Delete template?

Save as template?