News for hackers. Stuff that matters.
Re:Fedora 25 to Run Wayland by Default by srslack on Sunday August 21, 2016 @05:49PM (#12332881)
Needs to be implemented in each compositor, like most other missing details on Wayland.
Re:Fedora 25 to Run Wayland by Default by vertex-four on Sunday August 21, 2016 @06:01PM (#12332916)
Actually... Wayland fully supports transparent windows assuming you have a buffer with alpha transparency, and windows have no decoration by default. It would take a very small protocol extension to allow overlay windows which don't accept input of their own, allowing for Redshift (and other tinting tools, such as those for dyslexia) to implement such an extension without embedding it into a compositor.

Wayland has a process for standardising extensions - write the XML file defining it and send an email to the mailing list, then respond to questions - if developers cared about Wayland, they could do it.

Re:Fedora 25 to Run Wayland by Default by sunnyps on Sunday August 21, 2016 @06:06PM (#12332928)
Redshift (or flux) doesn't work that way. It adjusts the monitor's color temperature using XRandR.
Re:Fedora 25 to Run Wayland by Default by vertex-four on Sunday August 21, 2016 @06:17PM (#12332968)
Alright, though my latter point stands - standardising an extension for setting colour temperature would not be terribly difficult. You could look to libcoopgamma for ideas on managing multiple clients trying to change things at once, or write a simpler protocol that only allows one client to change things. At the very least, an unstable protocol definition and a patch for Weston would be a lot more than what we have now, and doesn't require Redshift to be cloned for each Wayland server.