81–90 of 125 posts
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?
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…
Thank you for Shortcat, I used it a long time ago and loved it. Excited to giv it another go!
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 this new wave of tools coming out for mouseless computer use. Chronic mouse use has destroyed my wrist so I have to avoid using it as much as possible. 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 t…
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…
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.
Full disclosure, I am a Wayland skeptic. I don't think your focus on X input security is as justified as you probably think.
Earlier quoted context omitted.
I love this new wave of tools coming out for mouseless computer use. Chronic mouse use has destroyed my wrist so I have to avoid using it as much as possible. 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 t…
I have used a trackball for many years since my wrist started bothering me, and I love it. I am right-handed, and I use Logitech's 575 and MX Ergo. I prefer the Ergo, even though it is more expensive. I keep it beside me on the couch where I sit. That way my elbow makes a 90 degree angle. Very comfortable. My keyboard is on my lap and my monitor at eye level.
Earlier quoted context omitted.
No it's not. It's pressure sensitive and about as fast or faster than a trackpad with movement. I've never had a problem with speed, even across multiple, large, monitors.
Is this not what you mean: https://www.youtube.com/watch?v=7H8o_-7bKIU ? I really doubt it's as fast/accurate as a trackpad even if you master it. This tool looks to be as fast as a mouse if you master it in many situations. But you would need a direct comparison by skilled users for each to be sure. I just don't see how a mini stick will ever beat pressing two buttons.
In the 1980's, there was a thread of animosity directed at GUIs and mice as productivity-killers and providing accessibility to novices that robbed power-users of expressivity and automation as features shifted towards UIs over text mode applications. I think we can agree that with necessary and sufficient software engineering and UX, CLI-UI-API parity is achievable offering an easier learning curve, varying levels of user astuteness, mental models, and expressivity to accomplish a task by having different MVC "views" or "presentations" to interact with software or systems of any sort.
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.
It's not just throwing away a decade's worth of work on X, it's making everyone redo that work per display manager (thankfully wlroots exists as a kind of Wayland shared library).