51–60 of 125 posts
Looks very useful! I especially like the ‘grid mode’ — I would never have thought of that idea myself. It’s just a pity it isn’t available on Windows, though I’ve previously had good experiences with Mousable [ https://github.com/wirekang/mouseable ].
Saw this thread just now, I'm gonna try to implement this in AutoIt, let's see how long it takes me! [2022-10-16-09:58-Z]
I've built an app that has the same goals (not operate a mouse) but approach it completely different. Rather than try to simulate the moving the mouse itself, Shortcat [ https://shortcat.app/ ] indexes the user interface (buttons, text fields, links, menus, etc) and enables fast fuzzy search of the interface. Type a word, abbreviations, or hints and hit Enter to click or action the element. Works almost everywhere on…
Looks very useful! I especially like the ‘grid mode’ — I would never have thought of that idea myself. It’s just a pity it isn’t available on Windows, though I’ve previously had good experiences with Mousable [ https://github.com/wirekang/mouseable ].
I've built an app that has the same goals (not operate a mouse) but approach it completely different. Rather than try to simulate the moving the mouse itself, Shortcat [ https://shortcat.app/ ] indexes the user interface (buttons, text fields, links, menus, etc) and enables fast fuzzy search of the interface. Type a word, abbreviations, or hints and hit Enter to click or action the element. Works almost everywhere on…
Looks very cool, have you considered adding voice input or is it already possible?
Looking at the limitations, I hate how fragmented Linux is becoming for apps like this. Completely separate implementations for: - X - Wayland + Gnome Shell - Wayland + wlroots-based compositor - Wayland + sway or any other non-wlroots based compositor Is Wayland really that much better that this is worth it? Why can't Wayland be aware of the compositor like X?
This is growth pains. Once the the need is understood well enough, a common extension will be written, and Mutter, KWin and sway/wlroots will implement it. This is better for security than X11 free-for-all.
Like how they standardized nice simple things like taking a screenshot?
Looking at the limitations, I hate how fragmented Linux is becoming for apps like this. Completely separate implementations for: - X - Wayland + Gnome Shell - Wayland + wlroots-based compositor - Wayland + sway or any other non-wlroots based compositor Is Wayland really that much better that this is worth it? Why can't Wayland be aware of the compositor like X?
https://github.com/rvaiya/warpd/tree/master/src/platform/way...
If there is a distinction, and there might be, "completely separate" is exaggerating.
Edit: I see that only wlroot based implementations are supported so far, and of those there are some things broken in wayfire. Perhaps this is what you're referring to?
I've built an app that has the same goals (not operate a mouse) but approach it completely different. Rather than try to simulate the moving the mouse itself, Shortcat [ https://shortcat.app/ ] indexes the user interface (buttons, text fields, links, menus, etc) and enables fast fuzzy search of the interface. Type a word, abbreviations, or hints and hit Enter to click or action the element. Works almost everywhere on…
I love Shortcat's approach in general, indexing the UI. However, the reliance on the Accessibility API is actually a significant downside in the real world in my experience since so many apps don't properly implement it. I feel like Warpd is a good complement to this, you could use Hint or Grid mode as a fallback when the indexing approach fails.
I wish I could use shortcat or Warpd, but unfortunately I'm on windows. Curious if anyone has any good tool recommendations for windows? Currently, I'm using:
1. Vimium for Chrome (so good, wish I could just use it across the OS).
2. Hunt and Peck: https://github.com/zsims/hunt-and-peck has been my favorite for OS-level use, a simple version of shortcat for windows. But, it's not maintained and not as slick as some of these newer tools.
Earlier quoted context omitted.
Have you actually used Wayland? Besides the obvious current issues (compatibility and/or missing features), it is way better. Even something as simple as moving and resizing windows feels noticeably faster and more responsive on Wayland compared to X. I don't use it at the moment because of compatibility issues with some software that I use, but that's not Wayland's fault.
> Besides the obvious current issues (compatibility and/or missing features) I mean, that's the whole biggest criticism of wayland, 15 years in and it still doesn't work (well?) with the biggest GPU brand. The criticism has always been about whether it is worth it to fragment linux land and throw away a few decades worth of work on X.
Earlier quoted context omitted.
Some people need tools like this, as an assistive technology - think RSI, Parkinsons and other issues that affect dexterity or elbow movement. Not so weird.
Thank you for explaining - as a consequence of illness and disability, I can understand the need. But why someone would intentionally make things more difficult for themselves as a preference, I don't get. It would be like walking around in crutches when you have two perfectly healthy legs.