From: Glenn <glennervin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup todo?
Date: Sun, 16 Sep 2012 15:34:32 -0500 [thread overview]
Message-ID: <FCA097C9572B4E1C965423DD685C8925@your2c061f0461> (raw)
In-Reply-To: <505617AB.1020700@tysdomain.com>
The big one for SpeakUp would be for it to have the option to switch to JFW
key mappings.
This will allow many people to switch to Linux easily.
Microsoft did this with MS Word, allowing people to use Word Perfect key
mappings.
I think this is the only way Linux will ever become any more popular to
screenreader users.
Glenn
----- Original Message -----
From: "Littlefield, Tyler" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, September 16, 2012 1:17 PM
Subject: speakup todo?
Hello all:
I'm trying to transfer, and applying for scholarships and all that I'd
like to be able to make some contributions to projects that I can note.
I'm interested in learning more about kernel programming, and I figured
I'd start by working on something I use almost daily. I'm curious then
if there's some sort of todo or improvements speakup could have to it.
I'd also be curious if someone has thought about moving it to
userspace--as far as I know, the only thing that we really need the
kernel for would be hardware speech (and since serial ports are dying
out that could be a dead point), and accessing the console directly. How
easy would it be then, to have speakup run in userspace, but access a
smaller cut-down version of itself in the kernel to provide the access
to the console we need?
We could use sequence files and access the console through /proc. It
could return a file of 2-byte chars, which I believe is how it works
now--one byte is the color, and the other byte is the ascii value. The
sequence file would just iterate over the console's lines. I'm also
curious how we'd handle something like key presses like caps+u to move
up a line etc.
If I'm way off here, I'd still like to help out if possible; is there a
todo list around, or stuff people would like to see done? If there are
people willing to answer questions from time to time in terms of the
kernel programming, since that's something I've not done before, I'm
game to start coding.
Another question is then, how do people catch panics? Since I'm not
quite cool enough to write code that just works, I'm sure I'll be
dealing with panics, but I can't see them on the console and usually
it's when speakup goes boom anyway.
--
Take care,
Ty
http://tds-solutions.net
The aspen project: a barebones light-weight mud engine:
http://code.google.com/p/aspenmud
He that will not reason is a bigot; he that cannot reason is a fool; he that
dares not reason is a slave.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Samuel Thibault
` Glenn [this message]
` Littlefield, Tyler
` Glenn
` Alonzo Cuellar
` Glenn
` Rob Hudson
` Littlefield, Tyler
` Alonzo Cuellar
` Glenn
` Littlefield, Tyler
` Rob Hudson
` Glenn
` Glenn
` Alonzo Cuellar
` Littlefield, Tyler
` Glenn
` Littlefield, Tyler
` Glenn
` Albert Sten-Clanton
` Jason Miller
` Glenn
` Littlefield, Tyler
` mk360
` Glenn
` Speakup history lesson, was " Kirk Reiser
` Albert Sten-Clanton
` Brian Buhrow
` Glenn
` Keith Barrett
` Kyle
` Kyle
` Cleverson Casarin Uliana
` Kyle
` Albert Sten-Clanton
` Albert Sten-Clanton
` Glenn
` mike
` Brian Buhrow
` Littlefield, Tyler
` Brian Buhrow
` Cleverson Casarin Uliana
` Cleverson Casarin Uliana
` Littlefield, Tyler
` Cleverson Casarin Uliana
` Littlefield, Tyler
` Kyle
` Cleverson Casarin Uliana
` Kirk Reiser
` Cleverson Casarin Uliana
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=FCA097C9572B4E1C965423DD685C8925@your2c061f0461 \
--to=glennervin@cableone.net \
--cc=glennervin@gmail.com \
--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).