Re: [g-a-devel] How to support New UI Engine

[Li Yuan <Li Yuan Sun COM>]

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 gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>