Embedding WPE WebKit - from Bring-up to Maintenance
summary
Any modern 64‑bit SoC running Linux with a GPU and GLES (preferably dmabuf support) can run WPE WebKit; integration uses Wayland/DRM or raw DRM, and common tools are Cog, meta‑webkit in Yocto, Buildroot packaging and WebDriver for automated tests. The project ships two major releases per year, has a WPE history of about six years, and recommends dmabuf to avoid pixel copies. Embedding options: reuse Cog or the new WPE platform library, add UI scheme handlers, user‑script messages or JavaScriptCore extensions for native APIs, and follow upstream security update practices.
AI-written summary · about
chapters (10)
- 0:00WPE WebKit intro
- 2:53WPE WebKit strengths
- 7:25Embed a web engine
- 10:59Hardware bring-up
- 14:31Graphics & Wayland
- 21:38Browser with Cog
- 24:05Web content interaction
- 34:03Updating WPE WebKit
- 39:42Best practices
- 41:08Q&A
related talks
49mEmbedding WPE WebKit - from Bring-up to Maintenance
37mWPE WebKit: HTML5 User Interfaces for Embedded Devices
49mBuilding End-user Applications on Embedded Devices with WPE
43mUnlocking the Full Potential of WPE To Build a Successful Embedded Product
42mReaching the Multimedia Web from Embedded Platforms with WPEWebKit
33mAutomated Testing for Web-based Systems on Embedded Devices
23mOpenCDM/CDMi (Multi DRM) work with WPE & Chromium
58mQtWebEngine – Taming the beast