public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: what is orca
Date: Tue, 5 Apr 2005 09:08:01 -0500	[thread overview]
Message-ID: <20050405140801.GC25490@blackbox> (raw)
In-Reply-To: <000201c539b5$ded8ef70$220110ac@jim>

Hi.

On Tue, Apr 05, 2005 at 01:02:48AM -0700, jim grimsby wrote:
> 
> 
> Yes, developmental.
> How well does it work so far?  Does it work better then gnopernicus?
> Where can one goto get it? Thanks. 

I can't get it to run on my current Debian system, but I tried it last
year when I ran Gentoo.  I suspect my problem in Debian is something
Debian changed in bonobo, but haven't spent much time trying to debug
and fix.

Because of the nature of Gnome accessibility, it did a good job.
It doesn't have any review functions,and at that
time, it did a better job of reading a gnome terminal.  Gnopernicus has
sinced improved it's access to Gnome terminals.

The only way I know to get it is from CVS.  I noticed that not all of it
gets downloaded some times, so make sure you get the C code as well as
the Python code if you try it.

export CVSROOT=':pserver:anonymous@anoncvs.gnome.org:/cvs/gnome'
cvs login
cvs co orca
cvs logout

I know this could probably be done with fewer commands, but I'm lazy and
just pasted my getorca script from last year.

If nothing else, orca convinced me the biggest problem with Gnome
accessibility is probably Gnopernicus and not actual Gnome
accessibility.

Hope this helps.
          Kenny
	  


  reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Danny Crone
 ` Janina Sajka
   ` jim grimsby
     ` Kenny Hitt [this message]
       ` Luke Yelavich
         ` Kenny Hitt
           ` Luke Yelavich
             ` Kenny Hitt
               ` Luke Yelavich
     ` Janina Sajka

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=20050405140801.GC25490@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).