Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard only functionality #14

Open
petercutting opened this issue Feb 22, 2013 · 5 comments
Open

Keyboard only functionality #14

petercutting opened this issue Feb 22, 2013 · 5 comments

Comments

@petercutting
Copy link

Hi
Does/Will Netzke support keyboard-only (ie mouse not required). This will help when redoing old mainframe apps. Keyboard-only apps are FAR more effective (then mousing) in the hands of an experienced (eg data entry) user.

My company has a ExtJs keyboard only app which works quite well. Things to implement in Netzke are

  1. never losing focus
  2. Tab and shift-tab working properly.
  3. keyboard shortcuts to jump between fieldsets
  4. every action has a keyboard shortcut
  5. clear indication of where focus is
  6. menu item numbers for quick menu access
  7. etc
@mxgrn
Copy link

mxgrn commented Feb 22, 2013

That's a good one!

Are all these things implemented in your app? I would love to have it as an example! Maybe a couple of screenshots can be shared? Thanks!

@petercutting
Copy link
Author

sorry just posted to groups as well, as decided this might be wrong place. where would you like to continue conversation.
All the above is implemented in our app. I cannot send it to you. Maybe a few specific snippets.
The app looks like blue Ext Js. drop down menus at the top and a screen number field (say F3). A screen typically has filter fields at the top, maybe a grid, then details. So fairly simple format. Can also use tabs and popups etc. I have been adding a screen and as a JS and Ext noob it is slow going.

@mxgrn
Copy link

mxgrn commented Feb 22, 2013

How would you suggest handling situations when, say, there's multiple grids on the page. How should we navigate around?

@mxgrn
Copy link

mxgrn commented Feb 22, 2013

In any case I'd be willing to start implementing these features, even be it scoped to a single grid.

@petercutting
Copy link
Author

The navigation is tricky. Not sure if we have best solution. Pgup/down moves focus to first field of next/previous fieldset. A Grid behaves as a fieldset. So mutiple grids not a problem. But now Pgup/down not available within grid which is a shame.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants