From: "Erik Heil" <eheil@rcn.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Gnopernicus with Festival
Date: Mon, 11 Nov 2002 18:36:14 -0500 [thread overview]
Message-ID: <00b601c289db$2633b040$0201a8c0@6S4X011> (raw)
In-Reply-To: <Pine.LNX.4.44.0211111813010.5022-100000@champion.mhonline.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yes, that could pose a problem, I think. What needs to be done is a way to
either disable or catch the system calls made to the Speakup screen review
package. But their are a myriad of ways one could acaccomplish this. One
would expect that when Speakup is in the "off" context, it would also
relinquish control of the numeric keypad to the rest of the OS. The serial
port is another issue, but its not important here, so I won't bring it up.
- ----- Original Message -----
From: "Chuck Hallenbeck" <chuckh@mhonline.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, November 11, 2002 6:20 PM
Subject: Re: Gnopernicus with Festival
> Hi Erik,
>
> Too soon to say. The keypad problem limits its usefulness right
> now, so I have only been cruising up and down menus and examining
> the choices etcetera.
>
> One nice thing about the X window system though is that you have
> a large number of choices of "Window Managers" you might run,
> some of which are look alikes for MS Windows and others are quite
> different. Gnome and Gnopernicus do not limit you to any
> particular Window Manager. The Gnopernicus developers recommend
> starting with either "sawfish" or "metacity" but I do not have a
> feel yet for how they function.
>
> This stuff is way too new to be useful right now, at least my
> implementation is. But it is like the proverbial talking dog: the
> amazing thing is not how well it talks, but that it talks at all.
>
> Chuck
>
> On Mon, 11 Nov 2002, Erik Heil wrote:
>
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi there. Have you gotten a chance to experiment with any of the Gnome
UI?
> > If so, what is it like? Similar to Winblows or MacOS X? i've heard
> > concepts such as multiple workspaces, and that one can have multiple
> > desktops within them, but I don't have any notion of them or what to
compare
> > them too.
>
> --
> The Moon is Waxing Gibbous (51% of Full)
> Visit Chuck Hallenbeck at http://www.mhonline.net/~chuckh
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 (Build 294) Beta
iQA/AwUBPdA+6TmECcLUqviGEQJhKACfdQD5K3kfko9vJIq9cW1UbBKWT68AoPSq
Ah9GqkzwQDYf+DP7kjPhDRxD
=HdjE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Erik Heil
` Chuck Hallenbeck
` Erik Heil [this message]
` Adam Myrow
` Chuck Hallenbeck
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='00b601c289db$2633b040$0201a8c0@6S4X011' \
--to=eheil@rcn.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).