[Kde-accessibility] KDE and AT-SPI [was: Re: Is it the time for "KSpeach"?]

[Olaf Jan Schmidt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[Bill Haneman, Mittwoch, 15. September 2004 18:04]
> In any case, I think it makes more sense to use the ATK/at-spi
> interfaces which Qt.next will be providing for this purpose, including
> AtkAction.
>

I am not sure this will be technically possible, because the Qt-ATK bridge 
is server-side only. We don't have a solution for client side AT-SPI 
support in Qt/KDE yet, mainly because the use of ORBit2 in KDE is not an 
option due to dependency issues.

Our strategy for KDE Accessibility is to support AT-SPI as soon as 
possible on the application side, and then to work with you on the 
changes that are needed for KDE/Qt-based AT clients.

D-BUS will be used by both KDE and GNOME, so it would make sense to use it 
as a base protocol for AT-SPI. We could reuse most of the AT-SPI 
protocol, of course. We might also change a number of things in the 
AT-SPI protocol that are needed to make Gnopernicus stable and quicker, 
but I am no expert in this area. Thomas Friehoff mentioned a couple of 
points in his talk in Ludwigsburg.

Gnopernicus was written in such a way that it could use a different 
protocol for AT communication, as Thomas pointed out in Ludwigsburg. I 
expect the situation to be similar for Dasher, since it is also running 
on Windows. How closely is GOK tied to CORBA? Does it use cspi?

Olaf

- -- 
Olaf Jan Schmidt, KDE Accessibility Project
KDEAP co-maintainer, maintainer of http://accessibility.kde.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAkFIceQACgkQoLYC8AehV8fLugCgsvb6U0rFTVqaRfT3B/WJpFCd
L3IAoIWHyaZ5mvNyB/rNADZmcYIS+EGC
=xRhs
-----END PGP SIGNATURE-----