Sub-Surfaces Support Added To Wayland Protocol

[phoronix]

Phoronix: Sub-Surfaces Support Added To Wayland Protocol

After the support has been within Wayland's Weston reference compositor for several months, developers have now added sub-surfaces support to the Wayland core protocol itself. Wayland sub-surfaces can make for efficient use of video players and windowed OpenGL games on Wayland...

http://www.phoronix.com/vr.php?view=MTUxNjY

[DebianLinuxero]

I wonder

I wonder how many of this new features would be added until the first grand desktop environment / Linux distro could release the entire thing in a stable manner.

I mean, Wayland isn't supposed to be a complete and stable protocol at v1.0?
A ready-now protocol for the desktop and applications?

News like this make me wonder how much it will take to achieve that.

[Pawlerson]

It's great to see so many news about Wayland at Phoronix. I hope nvidia will start to support it soon. I give them time to first Fedora/Wayland release. Otherwise I'm switching to AMD.

[jrch2k8]

I wonder how many of this new features would be added until the first grand desktop environment / Linux distro could release the entire thing in a stable manner.

I mean, Wayland isn't supposed to be a complete and stable protocol at v1.0?
A ready-now protocol for the desktop and applications?

News like this make me wonder how much it will take to achieve that.

so, in your planet you do things 100% perfect taking care of the 100% corner cases every time at first version?

well here on earth normally you stabilize a protocol core and release an 1.0 release that must work efficiently for most cases and then you later expand it to optimize the less likely corner cases

[liam]

so, in your planet you do things 100% perfect taking care of the 100% corner cases every time at first version?

well here on earth normally you stabilize a protocol core and release an 1.0 release that must work efficiently for most cases and then you later expand it to optimize the less likely corner cases

Add I understand it this doesn't seem like a corner case to me. For one thing video is an integral part of a computing experience. For another this seems like it only now allows one to handle generic buffer content without incurring a copy penalty.
I'm not saying going 1.0 without these features was wrong since I trust these devs know what they are doing, only that it SEEMS like it should've been included (well that along with complete input handling).

[jrch2k8]

Add I understand it this doesn't seem like a corner case to me. For one thing video is an integral part of a computing experience. For another this seems like it only now allows one to handle generic buffer content without incurring a copy penalty.
I'm not saying going 1.0 without these features was wrong since I trust these devs know what they are doing, only that it SEEMS like it should've been included (well that along with complete input handling).

Well it is a corner case, i mean this does not make videos unplayble or as crappy as X11/flash case. In fact even without this extension Html5 videos plays like heaven with gnome stock browser and wayland.

This extension just make it even more eficient plus some additional corner cases

[Ericg]

Add I understand it this doesn't seem like a corner case to me. For one thing video is an integral part of a computing experience. For another this seems like it only now allows one to handle generic buffer content without incurring a copy penalty.
I'm not saying going 1.0 without these features was wrong since I trust these devs know what they are doing, only that it SEEMS like it should've been included (well that along with complete input handling).

Wayland 1.0 never said "All features are covered." or even "The most basic features are covered."

Wayland 1.0 signified they were confident enough in the protocol and how the protocol is written and done that the protocol and client side libraries are now API stable. Before 1.0 the protocol could break at any time for any reason if they needed to.

[mrugiero]

Add I understand it this doesn't seem like a corner case to me.

No, but it is a case that haven't had taken care of in any of the current solutions yet (which mostly limits to X.org).

[ua=42]

I wonder how many of this new features would be added until the first grand desktop environment / Linux distro could release the entire thing in a stable manner.

I mean, Wayland isn't supposed to be a complete and stable protocol at v1.0?
A ready-now protocol for the desktop and applications?

News like this make me wonder how much it will take to achieve that.

The thing is. This is not an essential feature for a windowing system. It helps speed up a couple use cases, but wayland would work as a display system without it, just unresized videos would be a little slower.

[ssvb]

Basically, Wayland now got something similar (or something that serves similar purpose) to child windows support in X11.