Ozone-Wayland Support in Chromium (GENIVI 13th All Member Meeting & AMM Open Days)
•
1 gostou•609 visualizações
By Michael Catanzaro. Ozone is Chromium's platform abstraction layer, which allows porting Chromium to different environments by writing new Ozone backends. This talk will discuss progress in the Ozone-Wayland project, which allows running Chromium on Wayland.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (8)
Semelhante a Ozone-Wayland Support in Chromium (GENIVI 13th All Member Meeting & AMM Open Days)
Semelhante a Ozone-Wayland Support in Chromium (GENIVI 13th All Member Meeting & AMM Open Days) (20)
Mais de Igalia
Mais de Igalia (20)
Último
Último (20)
Ozone-Wayland Support in Chromium (GENIVI 13th All Member Meeting & AMM Open Days)
- 1. Ozone-Wayland Support in Chromium Michael Catanzaro Igalia S.L. October 21, 2015
- 2. Outline 1 GENIVI Browser 2 Chromium Basics 3 Ozone-Wayland
- 3. GENIVI Browser Requirements • Should use Chromium • Should have no user interface • Should provide D-Bus API • Vendors will create derivative browsers utilizing the D-Bus API
- 4. Technology Overview • D-Bus • Chromium • Ozone • Wayland • Ozone-Wayland
- 5. What is D-Bus? • Dominant IPC framework on GNU/Linux • Exposes objects with signals and methods • Intended for UNIX sockets (but can run over TCP too!)
- 6. Technology Overview • D-Bus • Chromium • Ozone • Wayland • Ozone-Wayland
- 7. What is Chromium? • Open source web browser and operating system • Basis for proprietary Google Chrome browser • Chromium is a project, not a product
- 8. Chromium
- 9. Blink • WebKit fork • More specifically, fork of WebCore
- 10. Content API • Content API sits below UI layer • Handles multiprocess management of web views • Roughly equivalent to WebKit2 API
- 11. Technology Overview • D-Bus • Chromium • Ozone • Wayland • Ozone-Wayland
- 12. Ozone • Platform abstraction layer for Chromium • APIs to encapsulate platform-specific details • Implementations: libcaca, GBM, Wayland
- 13. Technology Overview • D-Bus • Chromium • Ozone • Wayland • Ozone-Wayland
- 14. What is Wayland? • Modern replacement for X • Dramatically simpler • Applications can be untrusted
- 15. Technology Overview • D-Bus • Chromium • Ozone • Wayland • Ozone-Wayland
- 17. Ozone-Wayland: Status • Most things work • Pages render well • Many things need implemented • Still generally unstable
- 18. Ozone-Wayland: What Needs Implemented? • Fontconfig integration • Multiseat • Window resizing • Window movement • Minimize • Drag-and-drop • Copy/paste • Text selection • More!
- 19. Building a Browser on Ozone-Wayland • One Wayland connection per application; Ozone-Wayland owns the connection • Derivative browsers should implement nested compositor approach
- 20. Summary • Ozone-Wayland is needed for any Chromium-based browser. • Ozone-Wayland is incomplete and will require additional development effort. • Ozone-Wayland requires long-term maintenance investment.