Wayland Port

Idea

As our strategy of using Chromium as our engine of choice, we need Wayland support as some of our Linux target platforms are using that as the default (please check Roadmap), so we at Intel are committed on doing such changes.

Design

Tasks

Everything should be target upstream, within Chromium community; we haven't identified any tasks that the development should not happen there so far. Tasks should be coordinated with Tiago Vignatti a priori.

• Submit first batch to upstream review:

  • https://github.com/tiagovignatti/misc/tree/master/chromium
  • Intel's ACL with Tiago as a contributor (DONE by Tiago).
  • contact Google lead developers (DONE by Tiago)
  • waiting Google's response how to proceed (BLOCKED on Google)

• port Chrome browser:

  • should be fairly straightforward to be honest
  • task estimation: 1 or 2 weeks.

• use command-buffer instead in-process whenever using 3D contexts:

  • cross-process image transport should be implemented
  • task estimation: 2 weeks.

• Implement cursor routines for DesktopWindowHostWayland

  • cursors changes are not handled at the moment
  • task estimation: a few days

• Use headless Weston for testing units

  • just like xvfb is being used now on X11 platform, we'd need a Weston for Wayland.
  • task estimation: 1 week.

Tasks completed

• native events conversion to Wayland
  • most of the code is there already within the first batch of patches, but in practice content_shell is not receiving the native input events properly.
  • task estimation: 1 or 2 weeks.
  • DONE by Tiago (21 Jun 2013)