kickstarting with a jxr test of assigning a gesture to an object as an action
switching to another object
switching to another action
generalizing for xrsh and thus how to interface
Good fallback mechanism for e.g Lynx
gesture
target
callback
right hand pinch
red cube id
hide targetted cube
left hand pinch
red cube id
scale targetted cube
left hand pinch
blue cube id
scale targetted cube
left hand pinch
cube class
scale all targetted cubes
1. kickstarting with a jxr test of assigning a gesture to an object as an action
1. switching to another object
1. switching to another action
1. generalizing for xrsh and thus how to interface
Good fallback mechanism for e.g Lynx
| gesture | target | callback |
| -------- | -------- | -------- |
| right hand pinch | red cube id | hide targetted cube |
| left hand pinch | red cube id | scale targetted cube |
| left hand pinch | blue cube id | scale targetted cube |
| left hand pinch | cube class | scale all targetted cubes |
wondering how programming the firmware of my mechanical keyboard (thus being aware of such affordances as mode, semi-mode, tap, etc and even designing the keyboard itself) with the intersection of ergonomic might help design the right gestures
wondering how programming the firmware of my mechanical keyboard (thus being aware of such affordances as mode, semi-mode, tap, etc and even designing the keyboard itself) with the intersection of ergonomic might help design the right gestures
Good fallback mechanism for e.g Lynx
KDE Custom shortcuts as example
wondering how programming the firmware of my mechanical keyboard (thus being aware of such affordances as mode, semi-mode, tap, etc and even designing the keyboard itself) with the intersection of ergonomic might help design the right gestures
Initially started as https://forgejo.isvery.ninja/xrsh/xrsh-apps/issues/1
See also existing models e.g