Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP ei socket for at-spi2-core #759

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

WIP ei socket for at-spi2-core #759

wants to merge 1 commit into from

Conversation

ids1024
Copy link
Member

@ids1024 ids1024 commented Aug 22, 2024

This works with the receive example of reis using LIBEI_SOCKET=/tmp/atspi-ei-kb.socket. I've also worked on changes to at-spi2-core, so I'll now be able to try testing it...

If a version of this is ultimately used, it will need a secure way to pass the socket to accessibility tools. Putting it in /tmp is a placeholder.

@ids1024
Copy link
Member Author

ids1024 commented Aug 23, 2024

It's just a hacky prototype at the moment, but this now partly works with https://github.com/ids1024/at-spi2-core/tree/atspi-ei.

Orca keybindings now work, but the keys are also sent to applications. We need something like X11's XIGrabKeycode to register a key combination. But all we need to do is have the compositor track those grabs and not send them to applications. We don't need to feed all input synchronously through the screen reader or anything.

I think that's pretty much the only other thing we need for parity with AtspiDeviceX11?

We'll also need a secure mechanism to start the screen reader, and only give it access to this.

This works with the `receive` example of `reis` using
`LIBEI_SOCKET=/tmp/atspi-ei-kb.socket`. I've also worked on changes to
at-spi2-core, so I'll now be able to try testing it...

If a version of this is ultimately used, it will need a secure way to
pass the socket to accessibility tools. Putting it in `/tmp` is a
placeholder.

WIP

initial modifiers

start_emulating

fix keycode offset

WIP use cosmic-atspi-unstable-v1 protocol

Now client has a way to communicate grabs, but they still need to be
handled here.

WIP grabs

WIP keycode offset

atspi grabs

SealedFile

add_keyboard

Update reis with improved api

WIP update_keymap

WIP update keymap

WIP grab keyboardt

Multiple clients

reis update; serial
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant