Wayland Color Management Protocol Might Finally Be Close To Merging

[Ropid]

[...] The colorimeters's sensors wear out even if you don't use them. [...]

This problem seems to be fixed in the current colorimeters, they stopped using organic materials that age in their color filters.

That said, this change is somewhat recent so trying to get a cheap, used colorimeter on eBay is a struggle because the older, bad models being more common there last time I looked. Search terms to use to find if a model is bad is "organic filter", and "dichroic filter" for the good ones.

[Quackdoc]

What about USB game pads? When can we control the Wayland pointer with those? There used to be a X driver for the original xbox controller iirc

probably would be implemented as a seperate utility using the virtual input protocols.

[oiaohm]

What about USB game pads? When can we control the Wayland pointer with those? There used to be a X driver for the original xbox controller iirc

https://github.com/AntiMicroX/antimicrox

https://github.com/AntiMicroX/antimicrox/releases/tag/3.1.7

That was a problem solved end of 2021 for wayland. This is using the generic uinput system.. This is where things get interesting right. Lot of stuff was being done at X11 level that did not need to be. Yes doing it inside X11 server was decreasing X11 server stability.

[Daktyl198]

merged https://gitlab.freedesktop.org/wayla...e_requests/342

Well, so far it doesn't really seem to be having any effect. Hopefully that changes. Also, that was one of 3? proposals he made. What of the others? I tried to search for them myself but their gitlab instance is impossible to navigate and slow as hell.

For the record, I've used Wayland basically since it was available on KDE and I much prefer it to X, but I'm a realist who understands that 3rd party APIs and the hack that is Portals is what's keeping Wayland afloat right now rather than any work done by the Wayland Protocols team in the last 10 years. Either the Wayland protocols need to speed up development, or we'll be stuck in this limbo for another 10 years.

[Quackdoc]

Well, so far it doesn't really seem to be having any effect. Hopefully that changes. Also, that was one of 3? proposals he made. What of the others? I tried to search for them myself but their gitlab instance is impossible to navigate and slow as hell.

For the record, I've used Wayland basically since it was available on KDE and I much prefer it to X, but I'm a realist who understands that 3rd party APIs and the hack that is Portals is what's keeping Wayland afloat right now rather than any work done by the Wayland Protocols team in the last 10 years. Either the Wayland protocols need to speed up development, or we'll be stuck in this limbo for another 10 years.

Are you not on a forum thread about one of the most wanted, and longest awaited protocols being merged?

[smitty3268]

And Frog Protocols didn't catch on specifically because that other valve engineer was going to "fix" the "real" Wayland development cycle. Yeah right. All he did was sabotage our chance to have a functional desktop via Frog Protocols. Now we're right back where we were before: Fucked.

I believe there were 2 protocols in frog.

fifo-v1 was merged upstream into wayland a month and a half ago - https://gitlab.freedesktop.org/wayla...e_requests/256
And color management is presumably what this article is about.

So I'm curious what exactly you think isn't making progress by not using frog protocols. Seems to me like the point was made and people have agreed to start allowing things to go forward.

[stalkerg]

Common init system? SystemD. Done!

OpenRC is still here, and I am on Gentoo. I still use it without any issues.

[smitty3268]

This color management protocol? Yeah, great, maybe KWin and Mutter will implement it in the next 12-36 months or so, in five more years it will be in other 70% of Wayland implementations. The rest 30% or so will never get it. That's madness that no other modern widespread OS has.

You said the same thing about the explicit sync protocol back in May when it was released - actually I think you were even more pessimistic about it. Look at the current support for it. There's zero reason to believe this won't get supported quickly by most compositors, especially since the primary ones have already had working implementations for years. It's just been a matter of protocol approval gridlock, not a lack of implementers.

[fallingcats]

Well, so far it doesn't really seem to be having any effect. Hopefully that changes. Also, that was one of 3? proposals he made. What of the others? I tried to search for them myself but their gitlab instance is impossible to navigate and slow as hell.

For the record, I've used Wayland basically since it was available on KDE and I much prefer it to X, but I'm a realist who understands that 3rd party APIs and the hack that is Portals is what's keeping Wayland afloat right now rather than any work done by the Wayland Protocols team in the last 10 years. Either the Wayland protocols need to speed up development, or we'll be stuck in this limbo for another 10 years.

https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests?scope=all&state=all&author_username=zmike

There. They're all merged. Took about 20s to find out.

[Daktyl198]

I believe there were 2 protocols in frog.

fifo-v1 was merged upstream into wayland a month and a half ago - https://gitlab.freedesktop.org/wayla...e_requests/256
And color management is presumably what this article is about.

So I'm curious what exactly you think isn't making progress by not using frog protocols. Seems to me like the point was made and people have agreed to start allowing things to go forward.

The point of Frog protocols wasn't the initial protocols inside of it. The point was to have a separate, collaborative set of protocols that multiple vendors could work together on and implement that was outside of the glacier that is the official Wayland Protocols committee. More protocol proposals were supposed to make their way into Frog, but the 2nd valve engineer deciding to "fix" the official Wayland Protocols derailed it.

It's nice that a big API is being officially merged, but that was one that's been around for a long time already. The real test is in the dozens to hundreds of protocols that have yet to be decided on that do small but important functionality. Sorry if I don't trust that something so broken for literally 15 years was magically fixed by a single guy saying "hey guys, let's all get along better and speed things up!".