Hi, Halim and Mark. If some help is needed to work on the qt-at-spi bridge, please let me know. I can ask some Vinux volunteers if they would be willing to help, and I have some interest in helping myself.
I think Mark can probably enlighten us as to what's actually going on under the hood in the IA2 interface to QT. My understanding is that it's a Linux-only interface, so it's not really IA2. It wont support very much of the MSAA interface, for instance, which in theory is a subset of IA2. Uninformed programmers like myself have theorised that it might make more sense to merge qt-at-spi directly into the IA2 interface in QT, as it's really just the Linux accessibility interface, but that's a completely uninformed opinion. Bill On Thu, Jul 8, 2010 at 3:45 PM, Halim Sahin <[email protected]> wrote: > Hi, > It seems that marc needs some help to finish this work. > three commits in 8 months. > Are you sure that he will continue that work in the future? > > In my point of view using ia2 under linux is a big mistake. > We have already a working a11y infrastructure (atk). > So it makes no sense to create a second api. > In general it's painfull that qt apps are inaccessible for a long time. > And using ia2 will not speedup things because they need to bridge to > at-spi. > So the better approach would be to write a new screenreader which > understands ia2 directly or switch to atk natively in qt itself. > > > _______________________________________________ > gnome-accessibility-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > _______________________________________________ gnome-accessibility-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
