developing Chromium on Wayland

A few weeks ago we released Ozone-Wayland and now we’d like to detail for you the development process and strategy behind it… ah, and the title is not developing Chromium, the browser; it’s developing Chromium, the project! You will understand why next.

communities

There are three main projects involved in here: Chromium, Wayland and Ozone-Wayland. In Chromium, there is a very big and geek community that mainly produces Chrome browser and Chrome-OS. Very near to that one there’s Blink engine’s community, which interacts (and overlaps) a lot with the Chromium’s; I can’t tell exactly in numbers but there’s huge number of people, vendors and commercial involved in Chromium and, more important to us, there’s a lot of quality code being cooked in there for leveraging Web technologies in general.

In the other side, we have Wayland, the project that hosts the development of a Linux graphics system. Its goal is to give to applications the best graphics performance that can be extracted from the hardware. The community in there mainly produces the Wayland client/server libraries and Weston, the window server to hosts applications.

Now, somewhere in between Wayland’s and Chromium’s, the Ozone-Wayland community will start to grow. Ozone, the Chromium’s meta-platform for supporting different windowing systems, has given the possibility of building the whole Wayland support outside the Chromium and Wayland code-bases — basically each project then has its own code base. It may take a second of reflexion, but it’s an wonderful way of organizing the development because a community doesn’t need to step on the other. And that’s the main point because, grossly speaking, Web developers don’t want know core graphics and hardware details, while the window system’s don’t want to know about Web technologies. Using this kind of organization, Ozone-Wayland therefore hosts the tough task of bridging Wayland graphics for Chromium, and on doing so also diminishes the burden of the two other big communities having to interact directly with each other.

products cheat-sheet.

It’s good to remember what each of these three projects are building. A quick guide follows:

- Chromium: Blink Web engine, Content Shell (used for runtime’s, browsers, etc), Chrome browser, Ash UI, Chrome-OS, among others.

- Wayland: libwayland-server, libwayland-client, Weston window compositor, Desktop Shell (a “toy” shell UI, for testing purposes).

- Ozone-Wayland: libozone-wayland, that relying on libwayland-client and linking with all Chromium based products. So Ozone-Wayland basically leverage any of those products that the Chromium project develops.

web page and how-to.

A few people came asking me how to setup Ozone-Wayland and etc. I’m not sure you guys noticed, but we’re hosting there in Github something that we call our “Web page”, detailing a bit more how Chromium code-base plays together with the Wayland specific bits. In particular, there’s a how-to for people that wants to give a try and check out the development. There’s a small wiki as well.

Github infrastructure.

We’re coordinating the development via Github’s tracking issue system and trying to avoid mailing list so far — Welcome to the 21st century… let’s see how long we can stay in there and avoid going back to the 20th again :)

So you can “star” and “watch” Ozone-Wayland, as a subscription mechanism to get notifications of all sort of updates. Do it now!

IRC.

we hang out in freenode.net, #ozone-wayland channel; everyday and in the timezone you wish :)

About these ads

Tags: , , , , , , , ,

8 Responses to “developing Chromium on Wayland”

  1. Tomasz Says:

    What about Atomic Display Framework? Isn’t it like competition for Wayland?

  2. Robert Kroeger Says:

    w00t!

  3. vignatti Says:

    hmm interesting, I just haven’t heard anything about the Atomic Display Framework until now. Anyhow the bet in here is with Wayland which is an already product-quality software.

  4. diy tips to burn fat Says:

    diy tips to burn fat

    developing Chromium on Wayland | Tiago Vignatti

  5. automatem.pl Says:

    Thank you for sharing your info. I really appreciate your efforts
    and I am waiting for your next post thank you once
    again.

  6. https://delicious.com/sillyquibble8446 Says:

    Is just a leading supplier for tens of thousands of goods, companies, and solutions
    of impartial evaluations and rankings. Your objective, at, is to
    give truthful and precise opinions which can be representative of
    the business in-question. We will help you locate another instructor
    or refund your complete purchase if for any purpose you aren’t pleased after your training.

    LVMPD sgt DEBRA WEBB and RYAN T. My privileges were broke by DEWEY as well.

  7. plumbers Says:

    In the amount of electricity passes to your machinery that benefit from
    check out here it.

  8. Playa del Carmen real estate Says:

    Useful information. Fortunate me I found your website accidentally, and
    I’m stunned why this twist of fate didn’t happened earlier!

    I bookmarked it.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Follow

Get every new post delivered to your Inbox.

%d bloggers like this: