From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Slackware is dropping Gnome
Date: Sat, 2 Apr 2005 20:59:06 -0600 [thread overview]
Message-ID: <20050403025906.GA4056@blackbox> (raw)
In-Reply-To: <000401c537ca$5a83dd80$220110ac@jim>
Hi.
The KDE screen reader won't happen soon because the basic libs for KDE are
still being rewritten. Once that happens, a screen reader like
Gnopernicus should be able to work with it with few changes. KDE is
using AT-SPI same as Gnome.
Mark wrote Orca as an alternative to Gnopernicus, but he no longer works
for Sun and I haven't seen any updates to it's CVS since July.
It seems development of GUI access is happening much slower than console
access. My personal view is this is happening because the developers of
GUI access don't depend on it to use there computers while the
developers of console access do.
My girl friend is also non technical, so she only uses Linux in Gnome.
She wouldn't even consider trying to use a command line. One of the
cool things about the GUI interface in Linux is you don't really need
access to support it. Mary Ann started using Gnome 1.4 which had no
access for me. I read docs and edited Gnome's config files in the
console.
If your girl friend is sighted, she will have no problems with using
Gnome. If she's used Windows, she will like the improvements.
Hope this helps.
Kenny
On Sat, Apr 02, 2005 at 01:24:23PM -0800, jim grimsby wrote:
> Well dave has been complaining about this for quite some time. At first
> his problem was not clear because he was doing a lot of talking about
> software speech and a radio show but the problem is clear. Kde is
> coming out with a screen reader for it soon according to peater. He
> said it was hopeful. Mark has created an alternative to gnopernicus
> witch I have not herd a lot about yet. It seems to me at this point
> after doing a lot of reading that the gui support has a long way to go.
> The nice thing is with speakup we can do every thing we would need to do
> in text mode. The reality is though that we really need this gui
> support. There are a lot of programs that are created using this gui
> interface. Also gui is easier for the new user to learn. Monkey see
> monkey do is always going to be easier then typing a lot of commands at
> a command line. I got in to linux hoping I could start building
> computers for blind people with a easy to use interface that would be
> the same across the board from program to program. Sorry to say I have
> not found this yet. Gnome still has to many problems to be a stable
> solution. Gnopernicus crashes more often then jaws does at this point.
> I my self am going to keep a close eyes on this situation as I get text
> based programs for my self learn it and then try to teach my very non
> technical girl friend linux. If she is able to grasp it using text mode
> there might be some hope for this project but if not I might need to
> wait another year or two.
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` Gregory Nowak
` Adam Myrow
` Joseph C. Lininger
` Re[2]: " Farhan
` Kenny Hitt
` Chris Hofstader
` Kenny Hitt
` Chris Hofstader
[not found] ` <20050402155416.GA13919@blackbox>
` Kenny Hitt
` jim grimsby
` hank smith
` Kenny Hitt [this message]
` jim grimsby
` Adam Myrow
` Kenny Hitt
` Gregory Nowak
` Janina Sajka
` Kenny Hitt
` Steve Holmes
` links 2.1 and elinks was " Kenny Hitt
` Trevor Astrope
` Steve Holmes
` Kenny Hitt
` Steve Holmes
` Igor Gueths
` Sean McMahon
` Kenny Hitt
` Lorenzo Taylor
` Justin Ekis
` Lorenzo Taylor
` jim grimsby
` Lorenzo Taylor
` Lorenzo Taylor
` jim grimsby
` Gregory Nowak
` Laura Eaves
` Ned
` Laura Eaves
` Kenny Hitt
` Laura Eaves
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=20050403025906.GA4056@blackbox \
--to=kenny@hittsjunk.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).