From: "Chris Peterson" <capeterson@visi.com>
To: <speakup@braille.uwo.ca>
Subject: development questions
Date: Sat, 26 Jan 2002 15:42:16 -0600 [thread overview]
Message-ID: <000e01c1a6b2$53c2a820$6801030a@greatmachine> (raw)
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Hello,
I don't even have speakup installed yet, but I've been looking through the sourcecode and documentation to try to understand how this all works.
I've programmed in C, but mostly in dos/windows so I'm not familiar with kernel programming in Linux, but perhaps someone can bring me up to speed and perhaps I can assist with speakup development when I have a better understanding of what is going on.
After looking through the source, I'm unclear as to where the main entry point to speakup actually is. There must be a process running that controls everything (i.e. speaks when new text is written to video...etc.) Can someone explain exactly what functions are called where so I can better understand this?
Also, after looking at the keymap for speakup, and reading the man pages for loadkeys, dumpkeys...etc, I have a question that I haven't found the answer to as of yet. Some of the key definitions for speakup refer to hex addresses which I believe are the addresses of functions to be called when the keys are pressed (such as moving to the previous or next word). How are those addresses determined? If one wanted to add more functions that could be bound to keys, how would one determine the addresses of those functions to write them into the keymap?
Thanks and I hope I haven't caused to many headaches,
Chris
[-- Attachment #2: Type: text/html, Size: 2208 bytes --]
next reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Peterson [this message]
` Kirk Reiser
` Chris Peterson
` rmann
` Thomas Ward
` Chris Peterson
` Kirk Reiser
` Chris Peterson
` Angelo Sonnesso
` Geoff Shang
` Gregory Nowak
` Geoff Shang
` Buddy Brannan
` Thomas Ward
` Kirk Wood
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='000e01c1a6b2$53c2a820$6801030a@greatmachine' \
--to=capeterson@visi.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).