Re: How Wayland manages the automation/access of input devices and deal with block on them
On Fri, 25 Nov 2022 07:04:14 + "Victor Borghi Gimenez (FIPT)" wrote: > Hello there, > > I was developing some scripts to automate test cases using Xlib > package in Python to test resources (click in icons, verify the > opened window, text that appeared) on a new linux distro here, before > it was standardized in X11 and now they decided to standardize it in > Wayland and it let me stucked to keep the development of the scripts > because the lack of working. I also give a dig to find packages in > Python and mouse/keyboard simulation tools compatible with Wayland > which work in terminal and I found python-uinput which works for > simulation of keyboard but not to simulate mouse, and ydotool which > gave me error. Now I would like to know how Wayland manages the > automation of mouse and keyboard opposed to X11/XOrg in order to > develop any script in Python or other language to automate input > devices, I don't have any knowledge of the differences from XOrg and > Wayland and I fell in this study because the need to automate Wayland. Sorry, Wayland does not standardise that yet. Is your aim to test applications or Wayland compositors? If you want to test applications, you might be able to build something against a specific Wayland compositor or a compositor library. The only truly generic interface is uinput (Linux kernel evdev), and using that requires root privileges and comes with a bunch of caveats. Another generic approach is libei, but it requires explicit integration in compositors, and I'm not aware of any compositor doing that yet: https://gitlab.freedesktop.org/libinput/libei Finally, each compositor might have something of its own, or not. Thanks, pq pgpBMOMJYRBJf.pgp Description: OpenPGP digital signature
[ANNOUNCE] Weston bug-fix release -- 11.0.1 and 10.0.3
Hi everyone, Last week Simon Ser expressed on IRC, that he's no longer interested into doing Weston releases, so I'd like to volunteer for that. We have a few fixes pilling up and I'd like to get these in until the end of the year, if it is possible. First, I'd like to personally thank Simon for his contributions and support all these years. Simon is (still) actively involved with Wayland and other related projects so he's going to be around, I hope we can further interact and collaborate. Secondly, I suggested last week doing a bug-fix release for Weston 11 (11.0.1), and with it, one for Weston 10 (10.0.3). I'd like to continue supporting at least one version behind our current development branch. I'm looking at doing that this point release, the third week of December (12-16), with a tentative for Dec 14, unless obviously some other issues don't further pile up. Finally, if you would like to see anything else getting in until then, and qualifies as a bug-fix, either open a MR against that respective branch or use the label 'Backport to weston 11' for closed MRs which landed into main branch, and which I might have missed. signature.asc Description: PGP signature
Re: [ANNOUNCE] Weston bug-fix release -- 11.0.1 and 10.0.3
Glad I could help Weston these last few years, and thank you for stepping up Marius!
