3 ms·
GUIs have keyboard shortcuts for decades, blame the developer that wasn't up to their stuff, not providing keyboard navigation. Heck, there are even Win32 and
by pjmlp 2y ago
GUIs have keyboard shortcuts for decades, blame the developer that wasn't up to their stuff, not providing keyboard navigation.
Heck, there are even Win32 and X Windows APIs designed with the exact purpose for keyboard navigation and shortcuts.
Maybe instead of doing TUIs one should better spend their time learning the tools of their craft.
Skyscanner failure to adopt such tooling, which browser also have due to accessibility requirements, has nothing to do with technical issues, all about skill and willingness where to spend budget.
- nikau 2y agoThe difference is keystroke buffering - the agent in sabre can type ahead while the system is processing a transaction, the web/gui user has to wait for each screen to load.
- pjmlp 2y agoFirst of all, keyboards have limited size buffers, secondly the same is available on GUIs, and I go back to mastering the craft and OS APIs. https://learn.microsoft.com/en-us/windows/win32/inputdev/keyboard-input https://learn.microsoft.com/en-us/windows/win32/inputdev/key... https://tronche.com/gui/x/xlib/events/keyboard-pointer/keyboard-pointer.html https://tronche.com/gui/x/xlib/events/keyboard-pointer/keybo...
- nikau 2y agoIts not the hardware keyboard buffer, its the tty readline or equivalent buffer which ends up being a like a stack of commands for the app which pops off the next buffered line after the previous line has processed. Although I'm sure its technically possible to do it, in reality no gui apps work that way and extra keystrokes end up lost while web forms refresh or a 2 tier app is waiting for the DB to respond.