Wayland Port

It's very important to understand that we are dealing with three projects here: Ozone-Wayland, Chromium and Crosswalk. Ozone-Wayland is the Wayland specific implementation of Chromium's Aura UI framework, and Crosswalk should be a consumer only of these two projects.

At the moment the otcshare/ozone-wayland repository is private to otcshare group (https://github.com/otcshare/ozone-wayland) , 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, if not in Chromium upstream wiki.

Ozone-Wayland tasks:

All tasks should be coordinated with Tiago Vignatti and Kalyan Kondapally.

• 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

Crosswalk tasks

All tasks should be coordinated with Caio, DS and Joone.

Tasks completed

• 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 (Done by Tiago)
  • DONE by Tiago (July 2013)

• 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)