[Koha-devel] Staff client keyboard shortcuts

Garry Collum gcollum at gmail.com
Tue Jul 14 22:45:17 CEST 2009


It seems like you are also talking about two different types of
shortcut keys, global keys and context keys.  For example the current
accesskeys are global.  No matter where you are in koha, they work.

The new functionality for F12 looks like it only works in circulation.
 There's no reason F12 could not do a related function in other parts
of Koha.  For instance, print an invoice or a workslip in
acquisitions, print out a routing slip in serials, or print out a
check-in slip if items are being checked-in and the patron requests
it.

Maybe for the global keys we could continue using the accesskeys, but
use function keys (js) for the context sensitive functionality.

On Tue, Jul 14, 2009 at 3:35 PM, Owen Leonard<oleonard at myacpl.org> wrote:
> I'd like to start a discussion on how keyboard shortcuts are
> implemented in the staff client so that going forward developers can
> be working according to the same playbook. Right now there are two
> different kinds of keyboard shortcuts:
>
> - shortcuts via the accesskey attribute
> - shortcuts via a jQuery plugin, hotkeys
> (http://code.google.com/p/js-hotkeys/). (Please note that this was
> recently updated in HEAD and the syntax has changed).
>
> The advantage of the accesskey method is of course that it's not
> javascript-dependent. The disadvantage is that different browsers
> handle accesskeys differently, a combination of keys is usually
> required (Alt+ or Ctrl+Alt+), and not all keys or key combinations
> will be available (for instance, because of conflicts with built-in
> browser shortcuts).
>
> The advantage of the javascript method is that it is possible to
> configure single-key shortcuts, although I think different browsers
> will still retain their shortcuts. Try this demo page:
> http://jshotkeys.googlepages.com/test-static-01.html.
>
> Currently the core set of accesskeys are "u" for Check Out, "r" for
> Check In, and "q" for Search. The javascript-based match for these is
> "Alt-u," "Alt-r," and "Alt-q." Darrell Ulm just submitted a patch that
> would add "F12" to the list of js-based shortcuts, used for printing a
> circ slip.
>
> Ideally our goal would be to provide shortcuts via accesskeys wherever
> possible, and supplement the accesskey method with javascript-based
> shortcuts. However, this limits us to keys which are valid for the
> accesskey method.
>
> Going forward, how should we choose the default keyboard shortcuts?
>
> Should we attempt to fall back on accesskeys? If no, should we expand
> the use of js-based keyboard shortcuts?
>
> Eager for opinions,
>
>  Owen
>
>
> --
> Web Developer
> Athens County Public Libraries
> http://www.myacpl.org
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha.org
> http://lists.koha.org/mailman/listinfo/koha-devel
>



More information about the Koha-devel mailing list