Linux

13880 readers

249 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

My Accessibility Stack and the future on Wayland (nocoffei.com)

submitted 4 days ago* (last edited 4 days ago) by exu@feditown.com to c/linux@programming.dev

13 comments fedilink hide all child comments

cross-posted from: https://feditown.com/post/3071906

Edit: To clarify, this is not my personal blog. It's just intended to raise awareness and spread it around here as well. I just don't believe in editorializing titles

you are viewing a single comment's thread
view the rest of the comments

[–] rumba@lemmy.zip 18 points 4 days ago (3 children)

Yeah, even from a non-accessibility standpoint, they're severely lacking. Text replacement shortcuts, mouse automation, it feels like a nightmare when you long for the control Windows users still have over their systems.

I've been using the Speed of Sound appimage for voice input, but it's just basic whisper to text on a global hotkey. I can get mouse control via python but only relative positioning. I tried to hack in some dead reckoning going to a bounding corner and coming back out but it's super cagey with accelleration which i'm not willing to turn off.

You're not an edge case; there are lots of us out there who would use a proper input api.

[–] esc@piefed.social 7 points 4 days ago (1 children)

It's not so bad like the article author describes, there is work being done to address the input issue e.g. libei and wayland protocols. (also N.Graham answer that says that it should be done on wayland level if they require universal solution is right if a bit unkind)

[–] nyan@lemmy.cafe 7 points 4 days ago (1 children)

And how many years will it take before this reaches a usable state, when people need (not just want) it now?

[–] esc@piefed.social 3 points 4 days ago

First, it is usable just not the way Talon requires (and its developer doesn't want to support wayland). Second people can use LTS distributions that will ship X11 for many years, and by that time it will either be good enough or won't.

[–] exu@feditown.com 5 points 4 days ago* (last edited 4 days ago) (1 children)

Just to clarify, I didn't write this blog post. It's just intended to raise awareness and spread it around here as well. I just don't believe in editorializing titles :)

[–] Skullgrid@lemmy.world 6 points 4 days ago

You can avoid the ambiguity by posting it as "Author: title of post". This way we can see you attribute the post to someone else.

[–] jaybone@lemmy.zip 2 points 4 days ago (2 children)

xdotool and kin didn’t work on Wayland for me.

[–] rumba@lemmy.zip 2 points 4 days ago* (last edited 4 days ago) (1 children)

same, these are surfaced in python, but it's barely usable

device = uinput.Device([
uinput.BTN_LEFT,
uinput.BTN_RIGHT,
uinput.REL_X,
uinput.REL_Y,
])

device.emit(uinput.REL_X, 0)
device.emit(uinput.REL_Y, 0)
device.emit(uinput.BTN_LEFT, 1)
device.emit(uinput.REL_X, -100)
device.emit(uinput.REL_Y, -100)

[–] jaybone@lemmy.zip 2 points 4 days ago

Yeah I wrote something using a lower level interface. Like at the usb layer or some shit, I forget. I gave that up and went back to X.

[–] esc@piefed.social 1 points 4 days ago

There is wdotool, it's not complete re-implementation yet, but it works.