Chromium To Support Wayland
sfcrazy writes "Chromium developers have started porting Chromium to X11 alternatives such as Wayland. Tiago Vignatti sent a message to the freedesktop mailing list, 'Today we are launching publicly Ozone-Wayland, which is the implementation of Chromium's Ozone for supporting Wayland graphics system. Different projects based on Chromium/Blink like the Chrome browser, ChromeOS, among others can be enabled now using Wayland.'"
Guys! guys! things aren't going quite my way... let me start again from scratch. This should help.
LOL, no one wants to use Mir. Isn't it about time Canonical just sticks a fork in it, admits they were wrong and just start working with upstream instead? Yeah, yeah, who am I kidding. Canonical's culture is based almost entirely on NIH and being a leech.
That's not Canonical, actually. That's RH and X developers.
And Intel.
will it actually increase the overall speed of the browser?
Anons need not reply. Questions end with a question mark.
And what is the problem with being a fag again?
Wait, the answer is nothing. Mod thread down!
Let me know when they remove RLZ Tracking and maybe I'll start to trust them as a web browser.
Source: Matthew Garrett, The state of XMir
I remember sigs. Oh, a simpler time!
By simply asking that question it is clear that you don't know what Wayland is or does. I suggest you start with their FAQ. But in summary Wayland is a repacking for X11 or xorg and all the packages you listed run on top of Wayland not instead of it.
I didn't know loud and annoying Harley riders did that...
Right, because a browser doesn't need to know how large its viewport is, or how much space is available to arrange its title bar and menus, or how to send or receive signals to or from the DM when it is minimized or restored or resized, or any of that kind of silly thing. Multi-tasking operating systems are so out of style...
I thought the UI toolkit was supposed to handle those types of things. Is Chromium a full UI toolkit? I've never used it...
Except that TFA clearly states they are porting Ozone (their graphics toolkit, as they're not using Qt Gtk or anything else) to Wayland.
Common missunderstanding is that Wayland is a display server. It is not. It's a protocol that UI toolkits use to talk to the compositor (KWin, Weston etc.).
I'm pretty sure that Canonical, by now, are more or less certian they will need to provide for apps to talk Wayland to Mir as not everyone will be using one of the big UI toolkits that talk to Mir directly. To those apps, Mir will be just another compositor.
And I don't mean Google, Google is pragmatic enough and has manpower to port Ozone to Mir as well.
It would be nice if they started to maintain a up-to-date ppa for ubuntu. After all it is a contestant for the standard browser for ubuntu. In my recollection the same thing is true for the windows version. If you want the most recent version you have to build it yourself. Which is ridiculous for a piece of software for which it is absolutely crucial to be up-to-date.
It may improve scrolling speed and other compositing functions, compared to unaccelerated graphics drivers. However, Chromium is known to have quite a decent openGL and 2D accelerated X interface already. I think this question should be read as: "Will wayland offer benefits as decreased power usage or better acceleration, compared to using X11?". In that case, I think we will probably have to say it isn't at that point in the foreseeable future.
I was promised a flying car. Where is my flying car?
the inevitable "This thing we thought would be easy turns out to be difficult" part of the project
Ah yes, the part also known as the second 90%...
"Little does he know, but there is no 'I' in 'Idiot'!"
No, Aura/Ozone is the toolkit (Aura being the widget/chrome layer, and Ozone lower level graphic layer).
The real purpose is, when DRM in the browsers is commonplace, one cannot have a remote image display system like X. With a remote display, one could, *gasp*, copy the precious images and re-package the video stream.
The idea is just to lock down the image display path.