Status of Chromium Embedded Framework (CEF) and Webapps on AGL
summary
Project replaces Chromium WebOS backend with CEF and provides a CEF recipe (added in June) so CEF is now the CEF default backend for the WAM runtime, using official Chromium release tarballs to cut clone/build time. Backend uses gRPC IPC instead of Luna, spawns one browser process plus per-app render processes, and shows a recorded proof of concept works. Maintenance wins: faster updates and security patches; pain points: platform-specific Chromium bugs, C++20/ compiler mismatches, and restoring dynamic app bundling.
AI-written summary · about
chapters (6)
- 0:00Introduction to AGL and WAM
- 2:14Understanding WAM architecture
- 6:14Transitioning to CEF
- 10:18Implementation and hardening
- 13:39Pros, cons, and challenges
- 16:54Q&A session
related talks
41mWeb Applications and UI on the AGL Demo Platform
34mTowards a modern Eclipse UI: Adding Chromium support to the Eclipse IDE
23mOpenCDM/CDMi (Multi DRM) work with WPE & Chromium
49mBuilding End-user Applications on Embedded Devices with WPE
49mEmbedding WPE WebKit - from Bring-up to Maintenance- 49mBuilding End-user Applications on Embedded Devices with WPE
19mGoogle facilitates smartphone-like app experiences in your Chrome browser
24mThe AGL Wayland Compositor, Present and Future Design Work