Wayland Port

Development

Chromium's Wayland implementation happens in a separate module of the Chromium upstream tree:

https://github.com/otcshare/ozone-wayland

At the moment the otcshare/ozone-wayland repository is private to otcshare group, but once we get the open-source PDT approval then we'll be open to the general public. Therefore, all the information concerning Crosswalk, tasks, priorities and Intel specific should be kept on this wiki, while the ones targeting more general development of Ozone-Wayland will go there.

Tasks

This are the tasks

Everything should 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)

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

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

• 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: 2 weeks.

• Implement cursor routines for DesktopWindowHostWayland

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

• port Chrome browser:

  • should be fairly straightforward to be honest but priority is low in face of Crosswalk.
  • task estimation: 1 or 2 weeks.

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)