Making Use Of Chrome's Ozone-GBM Intel Graphics Support On The Linux Desktop

Recently, I published a blog article about making Use Of Chrome's Ozone-GBM Intel Graphics Support On The Linux Desktop. This is about using ChromeOS graphics stack for a regular Linux system.  This article was also mentioned in Phoronix.

Originally, my old colleague started working on this a long time ago, but it has been broken since then. So I have been trying to enable ozone-gbm on a Linux system because this solution would be useful for embedded systems. I'm making a Yocto recipe for this and will open it soon.

My major contributions to Chromium project

I have been working on Chromium project since 2013 and fixed many bugs and implemented some features. Here are my major contributions:

Blink Editing

1. [Issue 226941] Contenteditable issues related to backspace handling
• https://codereview.chromium.org/2064473002
• https://codereview.chromium.org/2117663002
2. [Issue 318925] Copy and paste sometimes removes spaces between words

• https://codereview.chromium.org/2193033004
• https://codereview.chromium.org/2280513004
• https://codereview.chromium.org/2320533002
• https://codereview.chromium.org/2325553002
• https://codereview.chromium.org/2336043006

3. [Issue 310149] ContentEditable:   is forced on SPACE between text nodes
• https://codereview.chromium.org/2175163004
4. [Issue 335955] Unwanted spans inserted in contentEditable elements
• https://codereview.chromium.org/2072093002
5. [issue 571420] chrome hangs on when creating bullet list in contenteditable
• https://codereview.chromium.org/2250133004

6. [Issue 634482] Formatting tags converted to spans with styles on cut/paste
• https://codereview.chromium.org/2229703004
7. [Issue 625802] Unnecessary quote appears after clicking on indent more option in compose box.
• https://codereview.chromium.org/2175433002
8. [Issue 582225] document.queryCommandState isn't working well with _and
• https://codereview.chromium.org/1986563002
9. [Issue 584939] document.queryCommandState returns true for bold, italic, underline, and strikethrough after selecting image
• https://codereview.chromium.org/1960553002
10. [Issue 385374] queryCommandState can return true for both list types
• https://codereview.chromium.org/2268843002
11. [issue 232188] Caret color issue in content editable element
• https://codereview.chromium.org/14098003/ 

Aura and Wayland support:

1. [Issue 408481] System dialogs (e.g. 'Save As...') are not modal on Ubuntu
• https://codereview.chromium.org/1624793002/
2. [Issue 473228] Make *::ShowWithWindowState(minimized, maximized, fullscreen) consistent across platforms
• https://codereview.chromium.org/1125383008
• https://codereview.chromium.org/1138383008
• https://codereview.chromium.org/1159703006
• https://codereview.chromium.org/1130033003
3. Issue 578890 upstream wayland backend for ozone
• https://codereview.chromium.org/2042503002
4. Issue 50485 Korean Hangul typing issue  
• https://codereview.chromium.org/13818036/

Ozone-Wayland

Ozone-Wayland is an Ozone implementation of Chromium, which allows to run Crosswalk and Chromium browser natively on Wayland without any X11 dependence[1].

I have been working on Ozone-Wayland recently. There were two releases since I was involved in the development. In the latest release, I contributed the virtual keyboard support to Ozone-Wayland. You can find how it works in the following video:

The ozone-wayland team has been focusing on graphics accelerations such as WebGL, Canvas 2D, Accelerated Compositing on Wayland. WebGL and Canvas 2D accelerations can be accelerated by off-screen Rendering in GPU process. In the latest release, we started supporting multi-touch and virtual keyboard, which work fine on Tizen IVI as you can the above video.

What is Ozone?
 Ozone is an abstraction layer used by Chromium browsers to separate out the different windowing systems and also abstract surface acceleration for Aura UI framework, input handling, event handling, and other UI-related matters[4]. Ozone-Wayland provides Wayland support for Ozone[2].

Reference

1. Project Homepage: https://github.com/01org/ozone-wayland
2. https://01.org/ozone-wayland/blogs/kalyankondapally/2014/beta-channel-updated-m35
3. Ozone-Wayland Release Adds Virtual Keyboard, Touch Support, Mar. 26,  2014 
4. Chromium On Wayland "Ozone" Continues, Oct. 07, 2013
5. Wayland-Based Chromium Browser Released, Nov. 11, 2013
6. Chromium Ported To Wayland, Now Working, Sep. 18, 2013

Building Chromium browser on your Mac

Copyright © Chromium Project

Building your own browser is the best way to find bugs and fix them. Now, I'd like to introduce how to build Chromium on your mac. I think that the latest code seems more stable(?) and provides more features.

This is a starting point to build Chromium on Mac OS X.
http://code.google.com/p/chromium/wiki/MacBuildInstructions

Installing the depot-tools

http://dev.chromium.org/developers/how-tos/install-gclient

$ svn co http://src.chromium.org/svn/trunk/tools/depot_tools

Add depot_tools to your PATH:
$ export PATH=`pwd`/depot_tools:"$PATH"

Getting the code

A checkout straight from the Subversion (SVN) repository can take a long time. It would be good to download a tar ball from http://build.chromium.org/buildbot/archives/chromium_tarball.html

Then, you can update the code to the latest revision from the SVN repository.
$ gclient sync

Building from the command line

To build all targets (it takes a long time due to test case builds)
$ cd ~/chromium/src/build
$ xcodebuild -project all.xcodeproj -configuration Debug -target All

To build just chrome:
$ cd ~/chromium/src/chrome
$ xcodebuild -project chrome.xcodeproj -configuration Debug -target chrome

Running Chromium

Run Chromium debug build
$ cd ~/chromium/src/xcodebuild/Debug

$ open ./Chromium.app

Run Chromium release build

$ cd ~/chromium/src/xcodebuild/Release

$ open ./Chromium.app

The latest revision of Chromium looks cool.