headers
Eitan Isaacson | 3 Jul 2008 21:45
Gravatar

pyatspi version checking

Hi All.

Recently I committed to AT-SPI trunk a change that will allow pyatspi
version checking:

>>> import pyatspi
>>> print pyatspi.__version__
(1, 23, 3)

The version displayed is the AT-SPI version that pyatspi is distributed
with. The tuple stored in __version__ is the major, minor and micro
version numbers, in that order. So the above tuple means version 1.23.3.

Cheers,
	Eitan.
Permalink | Reply | 0 comments |
headers
Hao Yu - 於浩 | 4 Jul 2008 04:54

How to support New UI Engine

Hi, All

I was using a11y for GTK applications, it works so great! But now, it decide to use a new UI engine to replace GTK, it definitely do not have a11y. So my question is:

What need do to make New UI applications accessible? My idea is implement ATK, gail, and atk-bridge for new UI engine, am I correct, is there any easier way to do that?

 

Regards,

Alex

_______________________________________________
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Permalink | Reply | 2 comments |
headers
Li Yuan | 4 Jul 2008 06:29
Picon

Re: How to support New UI Engine

Hi Hao,

ATK is based on glib, so if there is no glib present you need a new one. 
You may also need a new library which implements ATK interfaces for the 
new toolkit (like GAIL). And a daemon like at-spi-registryd to collect 
necessary information and relay signals and implement device controller. 
Bridge for application (like atk-bridge) and ATs (like cspi and pyatspi) 
are also needed to do the IPC work. This is a lot of work. And I am not 
sure if there is some work needed for ATs.

If there is a CORBA implementation in the new environment, you probably 
can reuse some of the existing code like pyatspi. If Bonobo is supported 
then you can reuse most of the existing code except GAIL.

Note the project which implements at-spi on DBus is going on. So if the 
new environment supports DBus, it is also a choice.

Regards,
Li

Hao Yu - ì¶ºÆ wrote:
>
> Hi, All
>
> I was using a11y for GTK applications, it works so great! But now, it 
> decide to use a new UI engine to replace GTK, it definitely do not 
> have a11y. So my question is:
>
> What need do to make New UI applications accessible? My idea is 
> implement ATK, gail, and atk-bridge for new UI engine, am I correct, 
> is there any easier way to do that?
>
>  
>
> Regards,
>
> Alex
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>
Permalink | Reply | 0 comments |
headers
Peter Korn | 7 Jul 2008 19:28
Picon

Re: How to support New UI Engine

Alex,

In addition to Li Yuan's feedback about how to support ATK, you will also need to consider keyboard navigation and theme support for folks with vision impairments. 


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

Hi, All

I was using a11y for GTK applications, it works so great! But now, it decide to use a new UI engine to replace GTK, it definitely do not have a11y. So my question is:

What need do to make New UI applications accessible? My idea is implement ATK, gail, and atk-bridge for new UI engine, am I correct, is there any easier way to do that?

 

Regards,

Alex

_______________________________________________ Gnome-accessibility-devel mailing list Gnome-accessibility-devel <at> gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel 

_______________________________________________
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Permalink | Reply | 0 comments |
headers
Eitan Isaacson | 21 Jul 2008 02:07
Gravatar

Accerciser - Please test

Howdy.

This release of Accerciser has some substantial changes. I would love it
if folks give the latest release/trunk a round and tell me what you
think. Notice the new highlighter (inspired from Jambu, which was
inspired by Istanbul), and the context menu in the main treeview.

Most importantly, I put proper version checking in place for pyatspi. So
if you don't have the latest pyatspi the configure stage will fail.

I would like to hash out any kinks with this new stuff early.

Thanks,
	Eitan.
Permalink | Reply | 2 comments |
headers
Jason White | 21 Jul 2008 07:14

Re: Accerciser - Please test

On Sun, Jul 20, 2008 at 05:07:40PM -0700, Eitan Isaacson wrote:
> This release of Accerciser has some substantial changes. I would love it
> if folks give the latest release/trunk a round and tell me what you
> think. 

What is the present situation with regard to the accessibility of the tool
itself via Orca?

I remember reading, probably on this list, that it used to be inaccessible
with Orca, but perhaps this has since been addressed.
Permalink | Reply | 1 comment |
headers
Eitan Isaacson | 21 Jul 2008 22:23
Gravatar

Re: Accerciser - Please test

Hey Jason.

We have one major bug when using Orca, you could read about it, comment,
and fix it here:
http://bugzilla.gnome.org/show_bug.cgi?id=511352

Aside from that issue, Accerciser is designed to be fairly usable with
Orca.

Cheers,
Eitan.

On Mon, 2008-07-21 at 15:14 +1000, Jason White wrote:
> On Sun, Jul 20, 2008 at 05:07:40PM -0700, Eitan Isaacson wrote:
> > This release of Accerciser has some substantial changes. I would love it
> > if folks give the latest release/trunk a round and tell me what you
> > think. 
> 
> What is the present situation with regard to the accessibility of the tool
> itself via Orca?
> 
> I remember reading, probably on this list, that it used to be inaccessible
> with Orca, but perhaps this has since been addressed.
> 
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

_______________________________________________
Gnome-accessibility-devel mailing list
Gnome-accessibility-devel <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
Permalink | Reply | 0 comments |
headers
Mike Gorse | 31 Jul 2008 20:22

intercepting keys

Hi all,

Can someone explain how the registry daemon is supposed to listen for 
keyboard events?  There is a function in deviceeventcontroller.c called 
spi_controller_register_global_keygrabs which looks like it's supposed to 
cause the daemon to grab keys, but it seems to do nothing on my system. 
Instead, it looks like it is each application's responsibility to pass 
keys along so that, say, Orca will see them (this is done by gail for gtk 
applications); otherwise Orca won't know if a user presses one of its hot 
keys.  We don't currently have code in the UIA-to-ATK bridge to handle 
this, so I'm trying to figure out if we need code to intercept keys and 
pass them on to the registry.

Thanks,
-Mike G-
Permalink | Reply | 1 comment |

Gmane