4 ms·

kinda curious: how would you build something like Text Expander in this world? As a keyboard driver?

• maggit 10y ago
  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?
  • michaelmrose 10y ago
    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.
  • digi_owl 10y ago
    Why do that sound very damn close to the various X extensions that has come and gone over the years?
• bandrami 10y ago
  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?)
  • michaelmrose 10y ago
    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.