From: Jason White <jasonw@ariel.ucs.unimelb.EDU.AU>
To: blinux-list@redhat.com
Subject: Re: Concerning BLinux project (fwd)
Date: Mon, 7 Dec 1998 20:23:27 +1100 (AEDT) [thread overview]
Message-ID: <Pine.SUN.3.95.981207201212.20486B-100000@ariel.ucs.unimelb.EDU.AU> (raw)
In-Reply-To: <Pine.GSO.4.05.9812061054560.7011-100000@shell.clark.net>
One worthwhile project would be to design a user interface that provides
generic components which capture the semantic distinctions required for
spoken interaction and can also be presented graphically. This could be
based on an analysis of the types of input/output options required by
various types of interactions with application software. The resulting
system would need to be easy and natural for programmers to include in
their applications and also provide controls over the presentation in
different media, so that the visual, auditory and tactile renderings could
be independently customised.
Important and relevant analysis is provided in T. V. Raman's excellent
book, Auditory User Interfaces, Toward the Speaking Computer (1997),
details of which can be found at his web site.
The essential idea would be to extend the distinction between content and
presentation, which has been developed in structured markup languages, to
the entire user interface by creating a general means of specifying
interaction semantics and then specific presentational controls.
I am sure that experts in the u i field have developed proposals of this
kind.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Hans Zoebelein
` Concerning BLinux project T.Pospisek's MailLists
` Concerning BLinux project (fwd) Jude Dashiell
` OCR software (was Re: Concerning BLinux project (fwd)) Jason White
` Jude Dashiell
` Jack Berdeaux
` Ron Marriage
` Jack Berdeaux
` Jude Dashiell
` Jason White [this message]
` Concerning BLinux project (fwd) Jason White
` aaa
` Dave Mielke
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.SUN.3.95.981207201212.20486B-100000@ariel.ucs.unimelb.EDU.AU \
--to=jasonw@ariel.ucs.unimelb.edu.au \
--cc=blinux-list@redhat.com \
/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).