Orca scripting, how much can be done

Hello,
How much can be done to improve the accessibility of an
application by
using scripting? I hinted at this in a previous message
regarding
evolution and whether a key press can be made to move you to
a
particular control. I have other things I would want to do,
eclipse
would be a good example. In eclipse I would like to have
some way of
knowing whether a JUnit test succeeds or fails when
cursoring through
the tree showing test results. I don't know whether I could
use the
coloured indicator, or would I need to see if anything
appears in the
stack trace area.

Also if this would be possible where might one learn about
the various
technologies to be able to write these scripts. I am
familiar with the
python language, so don't need to learn that, but I would
need to know
about how to make Orca use the script, if I would need to
use at-spi and
how to use it, how to gather information I would need to use
the various
controls in my script, etc.

Any help would be welcome.

Michael Whapples

_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca
 for more information on Orca

> How much can be done to improve the accessibility of an
application by
> using scripting? 

You can do lots of things with scripting as long as the
application and 
toolkit are somewhat good AT-SPI citizens.  Even if they
aren't good 
citizens, but still participate in the AT-SPI, you can do a
fair amount. 
  I might conjecture that a lot of what we actually do in
Orca is to 
script to accommodate those that really aren't good
citizens.  

In order to script well, you really need a decent foundation
in AT-SPI. 
  Accerciser is a useful tool to help you with this, and
there's a good 
Linux Journal article on it here: http://www.
linuxjournal.com/article/9991.

 From there, you can look at the existing Orca scripts (they
live under 
src/orca/scripts/*.py in the Orca source tree) as well as
the default 
script which lives in src/orca/default.py.

Then, there's always here and the #orca channel on
irc.gnome.org, where 
questions are welcome and we even answer them when we have
time.  

Hope this helps get you started!

Will

_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca
 for more information on Orca

Thanks for this information, I think the learning of at-spi
will be the
main thing for me. Hopefully that link will be helpful, have
to try and
find the time to have a good read of it.

Michael whapples
On Thu, 2008-03-06 at 16:32 -0500, Willie Walker wrote:
> > How much can be done to improve the accessibility
of an application by
> > using scripting? 
> 
> You can do lots of things with scripting as long as the
application and 
> toolkit are somewhat good AT-SPI citizens.  Even if
they aren't good 
> citizens, but still participate in the AT-SPI, you can
do a fair amount. 
>   I might conjecture that a lot of what we actually do
in Orca is to 
> script to accommodate those that really aren't good
citizens.  
> 
> In order to script well, you really need a decent
foundation in AT-SPI. 
>   Accerciser is a useful tool to help you with this,
and there's a good 
> Linux Journal article on it here: http://www.
linuxjournal.com/article/9991.
> 
>  From there, you can look at the existing Orca scripts
(they live under 
> src/orca/scripts/*.py in the Orca source tree) as well
as the default 
> script which lives in src/orca/default.py.
> 
> Then, there's always here and the #orca channel on
irc.gnome.org, where 
> questions are welcome and we even answer them when we
have time.  
> 
> Hope this helps get you started!
> 
> Will
> 

_______________________________________________
Orca-list mailing list
Orca-listgnome.org
http
://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca
 for more information on Orca