News for hackers. Stuff that matters.
Re:The Linux graphics stack from X to Wayland (2011) by rtpg on Monday September 19, 2016 @10:33AM (#12531721)
kinda curious: how would you build something like Text Expander in this world? As a keyboard driver?
Re:The Linux graphics stack from X to Wayland (2011) by bandrami on Monday September 19, 2016 @11:13AM (#12532029)
I'm also curious about keyboard layouts. I type stuff in both English and Bengali, and it looks like wayland.ini uses similar semantics to xorg.conf (layout=us,in variant=,ben or something like that). I'm curious how they'll do per-window layouts like windowmaker does. I find those very useful, and I'd assume they depend on some level of message promiscuity that they find distasteful -- I could imagine libevent being "smart" enough to multiplex that like my window manager does, but that in itself gets worrisome for largely the same reasons that people are talking about with X, particularly if it's meant to be extensible (it is, right?)
Re:The Linux graphics stack from X to Wayland (2011) by michaelmrose on Monday September 19, 2016 @02:24PM (#12533521)
Why would it be extensible. Instead pick the desktop environment which gets this feature more or less right and hope that some other feature you want isn't only available on a different de.
Re:The Linux graphics stack from X to Wayland (2011) by maggit on Monday September 19, 2016 @10:39AM (#12531753)
Wayland is built up of multiple orthogonal protocols that each app negotiates access to with the server. Any given app will probably use multiple of these, for output, input, etc.

Not knowing exactly what Text Expander is, I'm guessing it would probably need access to a specific protocol for controlling accessibility features. The Wayland server would need to be configured to allow this app access to that protocol somehow, for example by way of a server-initiated popup window that asks you to allow or deny this access.

Does that explain it?

Re:The Linux graphics stack from X to Wayland (2011) by michaelmrose on Monday September 19, 2016 @02:22PM (#12533507)
What you mean is that because each compositor would have to add each feature that wayland breaks on each environment some will be implemented badly, others not at all.
Re:The Linux graphics stack from X to Wayland (2011) by digi_owl on Monday September 19, 2016 @10:22PM (#12536546)
Why do that sound very damn close to the various X extensions that has come and gone over the years?