Chromium-Blink migration of RDK

Introduction

● RDK - Reference Design Kit

● Chromium - open source browser

● CEF - Chromium Embedded Framework

● Gstreamer using Pepper plugin API

Blink - is the layout engine of Chromium. It was announced in 2013 as a fork of the WebCore part of the WebKit open source project. Compared to WebKit, has a reduced code base and added support for multi-process architecture. Blink is not a standalone framework, and requires the Content Module to provide any meaningful function.

Content Module - is the code base that enables to render a page using Blink. It includes all the HTML5 platform features, GPU acceleration. It provides the Content API integrated Blink/Content module into applications (like Chromium/Chrome).

Content Shell - simple browser implementation on the top of the Content API. The main goal of the content shell is to allow developers rapidly test Content module/Blink features, without the need of building a full browser.

Aura - Is the newly introduced window manager in Chromium. Historically, the Content Module was directly depending on the GTK2 and Windows HWND. The objective of Aura is have one single window manager on all platforms.

Ozone - is an abstraction layer for input events and graphics below the Aura window manager. Its purpose is to abstract away the OS specific windowing systems, like X11, and provide the possibility of integrating Chromium with alternative windowing systems: wayland, mir, etc.

Various ways of integrating Chromium

Framework and API that allows the embedding of Chromium browser into various UI frameworks and applications.

CEF/Chromium on ARM/RDK

GStreamer Pepper API pluginPepper plugin API is a low-level C interface between the browser and browser plugins.

Sample HTML code for playing a TS stream using our Gstreamer Chromium plugin:

Thank you!