Chromium Ported To Mir Display Server, Based On Wayland Code

[blackout23]

First non-Canonical Mir app?

Not quite. Chromium was ported by Canonical. The first non-Canonical Mir App would be some Ubuntu Touch app from a hobby programmer. There are already many of them available.

[log0]

they wrote abstraction layer that allows chromium and thus chrome to be ported to an external windowing system. but, i'm sure you already knew that.

You mean the abstraction layer work consisting of copy-pasting ozone wayland, renaming wayland to ui, and wrapping two structs into classes?

... instead of working with everyone else on wayland

[cb88]

Does that really matter. Aren't we wanting a Linux solution for mobiles devices that isn't tied to Google, Facebook, Microsoft, Yahoo, etc...

Canonical is such a company too you know... the whole lot is guilty of "Being Evil".

[e8hffff]

From one side, it's ok.
From another side the history repeat itself: take the wayland code -> change two lines -> rebrand as Mir-related work -> announces that "XYZ can now work on Mir". Then someone will jump in the forum to say "look, the Mir devs achieved the same result with 1/5 of the time needed by the wayland (not-so-smart) devs, ah ah".

Does that really matter. Aren't we wanting a Linux solution for mobiles devices that isn't tied to Google, Facebook, Microsoft, Yahoo, etc...

[benalib]

From one side, it's ok.
From another side the history repeat itself: take the wayland code -> change two lines -> rebrand as Mir-related work -> announces that "XYZ can now work on Mir".
Then someone will jump in the forum to say "look, the Mir devs achieved the same result with 1/5 of the time needed by the wayland (not-so-smart) devs, ah ah".

why not
let other do the heavy tasks and then port it! and it works just compare between the two presentation
and ozone wayland developers are indeed so smart! they develop it using Ubuntu they know Ubuntu just works and Fedora is not development-quality product

[valeriodean]

From one side, it's ok.
From another side the history repeat itself: take the wayland code -> change two lines -> rebrand as Mir-related work -> announces that "XYZ can now work on Mir".
Then someone will jump in the forum to say "look, the Mir devs achieved the same result with 1/5 of the time needed by the wayland (not-so-smart) devs, ah ah".

[benalib]

good work
it looks smoother than ozone-wayland presentation

[curaga]

First non-Canonical Mir app?

[Anarchy]

.. begs the question - which parts of Mir are original?

they wrote abstraction layer that allows chromium and thus chrome to be ported to an external windowing system. but, i'm sure you already knew that.

By now most readers will be familiar with the excellent work by Intel and contributors in creating Ozone Wayland[6]. Initial investigation in to Ozone Mir quickly lead to the observation that a large amount of code would need to be duplicated between them. In order to try to improve this situation, we have instead based our Ozone Mir work off of Ozone Wayland. Ozone Mir creates a new set of interfaces on the GPU process side abstracting the idea of utilizing an external EGL compositor. This results in a layer much more similar to conventional toolkit porting layers, and we hope that one day something similar can be used by all ports of Ozone to an external EGL windowing system[7].

[Ouroboros]

*cough* fragmentation *cough* *cough* cancer *cough*

I can't be the only one thinking it.