public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Charles Hallenbeck <2ndsight@taconic.net>
To: Richard Uhtenwoldt <ru@river.org>
Cc: blinux-list@redhat.com
Subject: Re: the glass tty model of human-computer interaction
Date: Mon, 14 Dec 1998 09:04:55 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.3.96.981214084931.355B-100000@darkstar.taconic.net> (raw)
In-Reply-To: <199812140555.VAA29035@ohio.river.org>

I have had a lot of experience with line editors dating from the late
1960s and as I think about it, it has been a very long time since I have
used one. I presently use a standard word processor for writing and
editing documents (I hate to admit it but I am a WordStar freak), and a
full screen "visual editor" (Brief by Borland and Underware) for program
preparation and editing.
I think the reason line editors and the dumb terminal went together so
well was the fact that one had to use the same key presses for editor
commands as for data entry. That meant there needed to be a convention for
switching back and forth between "edit mode" and "command mode". Even
though as a blind user I perhaps cannot appreciate the expanse of the
whole screen at once, there is an enormous convenience in not having to
think constantly about this distinction between the two "modes". Thus
while VI is a visual editor, it retains the problem of "edit mode" and
"command mode" and therefore resembles an older style line editor more
closely than a modern word processor.
Word processors and single-mode editors are clearly more convenient than
dual-mode editors, whether line or full screen oriented.
Thanks for your very interesting question.
BTW -- our screen review software, provox, has two modes of operation
which we call "standard mode" and "enhanced mode." In the former, one
needs to switch back and forth between using the keyboard for
communicating with the application, or using it for reviewing the screen.
The enhanced mode sets aside the numeric keypad for the exclusive use of
the speech software, so that in effect it is always in review mode, while
the rest of the keyboard is always in the active data entry mode. There
are in effect two cursors, one controlled by the running application and
one controlled by the user for screen review purposes. I had not thought
before about the similarity of this modality to the question of editor
design, but the similarity is striking.
 

Chuck -- Second Sight Software
Now using Linux and PINE




  parent reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Richard Uhtenwoldt
 ` Ann K. Parsons
   ` wlestes
     ` Matthew Campbell
   ` Jude Dashiell
 ` Charles Hallenbeck [this message]
 ` Dave Mielke
   ` Lisa Carmelle
   ` Why I learned emacs was " wlestes
     ` Dave Mielke
       ` wlestes
         ` Moe Aitel
           ` Luke Davis
             ` Moe Aitel
               ` Luke Davis
         ` Lar Kaufman
       ` Why I learned emacs Richard Uhtenwoldt
         ` Dave Mielke
         ` Jude Dashiell
 ` the glass tty model of human-computer interaction wlestes
 ` Jude Dashiell
 ` Jude Dashiell
 ` James H. Cloos Jr.
 ` Mike Keithley
   ` Steve Holmes

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=Pine.LNX.3.96.981214084931.355B-100000@darkstar.taconic.net \
    --to=2ndsight@taconic.net \
    --cc=blinux-list@redhat.com \
    --cc=ru@river.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).