saka-key

I'd say that pointing is inherently slow because it involves checking where the cursor is, where the target is, moving it in that direction, then stopping at the right time. With a typical keyboard-based browser interface clicking the update button would have been a 2 key combination. Two discreet steps without any timing or measurement nuances. I guess which is better for me doesn't have to be so for someone else. Mouse interfaces do have a certain simplicity to them. Check demo animation on Saka Key's readme: https://github.com/lusakasa/saka-key

I use Saka Key https://github.com/lusakasa/saka-key Usable in Chrome and Firefox. Configuration can be exported to JSON and reused on other machines.

Note that Saka Key currently is unmaintained: https://github.com/lusakasa/saka-key/issues/171

Far as I can tell, no. I'm open to adding an emacs profile to Saka Key. It's as easy as modifying this JSON file: https://github.com/lusakasa/saka-key/blob/master/src/options...

I think site-specific keyboard shortcuts are great. Do you have plans to release the source code? My chrome extension Saka Key [1] provides generic keyboard shortcuts, but my vision is to eventually integrate with other extensions like yours and Streamkeys [2]. 1. https://github.com/lusakasa/saka-key 2. https://www.streamkeys.com

Thanks! I was very surprised a half-decent in-window tab search extension didn't already exist. They all opened in the popup or a new window. So I made one myself. My goal is to make a complete Omnibar/tabs replacement so I can browse in full-screen mode by default. This extension complements my other keybinding extension (https://github.com/lusakasa/saka-key).

I've been building a keybinding Chrome extension like Vimium for about half a year now. It started when I struggled to add a feature to Vimium and figured I could do it better myself. From my biased perspective, my extension is better. User uptake has been negligible, but I think the lessons I've learned have made it worth the time invested. https://github.com/lusakasa/saka-key

For my extension Saka Key (https://github.com/lusakasa/saka-key), I decided to use the browser.* APIs on both Chrome and Firefox using Mozilla's web extensions polyfill. https://github.com/mozilla/webextension-polyfill The biggest challenge for me was addressing browser incompatibilities and Firefox bugs. This is a big one: https://bugzilla.mozilla.org/show_bug.cgi?id=1193394 Another is that Firefox doesn't fire blur events when DOM elements are removed or hidden. The Firefox approval process is slow. Mine took 3 months the first time, < 10 days the second time, and this third time it's taking over a month. Chrome's reviewal process is really nice. It usually takes <30 minutes.

Awesome job with the extension! I think the idea has great potential. Judging from my five minute test drive, you could probably increase adoption if you made it 'discoverable'. It's hard to determine what to do once it's installed. Turns out, you have to click the browser action to start listening for user input. After that, you have to refer to the website to find out what commands are available. It would be great if there were on-screen suggestions of commands to voice. Using it was really frustrating and unreliable until I read the instructions on the web store page to disable 'ambient noise reduction' on macs. Showing an 'instructions' page on installation would help a lot. An instructional video would be great too. Other nitpicks: * I couldn't get dictation to work. * More tab manipulation commands would be nice * I'm not a huge f