From: Tyler Spivey <tspivey@pcdesk.net>
To: speakup@braille.uwo.ca
Subject: Speakup in userspace
Date: Wed, 20 Jun 2007 01:33:54 -0700 [thread overview]
Message-ID: <20070620083354.GA4139@fajrero> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have some oppinions on this, and I'd like some input on how possible
this is. I'm not a very good C coder, but that's less important. I'm
hoping, if a user space screen reader is implemented, that it can be
extended; e.g. perl, python, etc. The problems with this seems to be:
1. How can a userspace program get extended key sequences such as caps
lock+i? Under Linux, I don't think that an API exists for this.
2. What about console output? There is /dev/vcs[a]x, but polling that
a few times a second would be inefficient if the system was under load.
The rest is relatively easy - Linux already has serial port devices if
needed, and also speech dispatcher communications. I see no reason why a
smaller subset of speakup (just an API to get keyboard/console
input/output) couldn't be included into the kernel - it probably
wouldn't change much, compared to the user-space adapter that would be
using that API. This is similar to what the Jupiter project is doing;
although that's all in-kernel.
any thoughts?
- - Tyler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFGeOZxTsjaYASMWKQRAt/WAKCsG0jwPECPii4+yQX6i4gO02UdXQCgmmuY
e5jsV1bQGCZd+8LLWjwTHTs=
=xOzu
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Spivey [this message]
` Luke Yelavich
` Samuel Thibault
` Luke Yelavich
` Samuel Thibault
` Doug Sutherland
` Samuel Thibault
` Doug Sutherland
` Samuel Thibault
` Christopher Moore
` Samuel Thibault
` Albert E. Sten-Clanton
` Doug Sutherland
` W. Nick Dotson
` Albert E. Sten-Clanton
` Deborah Norling
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=20070620083354.GA4139@fajrero \
--to=tspivey@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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).