9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] The utility of a chording pad
Date: Sun,  5 Aug 2007 13:49:40 +0200	[thread overview]
Message-ID: <5ee8edb3f8bb37a1de43a77f6deac71c@proxima.alt.za> (raw)
In-Reply-To: <d97c9ebdbb1867951527be229975cf0e@quanstro.net>

> that's because they're not standard.  you can use them if you map them
> with /dev/kbmap.
> 
> cpu% cat fkeys
> 0	59	'☺
> 0	60	'☹

For some definition of "standard", really.  The thing is that the
letter "a" is a clear concept no one is likely to argue with (and even
there, different keyboard layouts throw a spanner in the works, but at
least one assumes the keyboard has clear labels in place), but using
F1-F2-F3 as mouse buttons is a totally different idea and needs to
gain critical mass (think F1 as the Help key) before developers can
safely commit to it.

Chording itself is not at fault, although Gabriel is perfectly right
when suggesting that remembering more than a few combinations becomes
very difficult.  What is problematic is assigning the type of meaning
to each chord that meets with mass approval.  Given that needs vary
and some chords are bound to be easier than others, this is an
unlikely expectation.  Add the option to fall back to a keyboard
shortcut and the intent is readily defeated.

What may assist a lot would be visual hints, where the mouse pointer
or the colour of the highlight reflects the status of the chord.  But
I doubt that one would come up with a consensus on such meanings where
there are more than a few like in RIO or ACME.

++L



  reply	other threads:[~2007-08-05 11:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 11:35 erik quanstrom
2007-08-05 11:49 ` Lucio De Re [this message]
2007-08-05 11:59   ` Lucio De Re
2007-08-05 14:19     ` Steve Simon
2007-08-05 15:33       ` Lucio De Re
2007-08-05 15:33       ` Skip Tavakkolian
2007-11-06 21:26 ` maht-9fans
  -- strict thread matches above, loose matches on Subject: below --
2007-08-05  3:50 john
2007-08-05 10:03 ` Lucio De Re
2007-08-05 15:53   ` Jack Johnson
2007-08-05 10:05 ` Gabriel Diaz
2007-11-06 21:49 ` Eric Van Hensbergen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ee8edb3f8bb37a1de43a77f6deac71c@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).