[Kde-accessibility] Re: Qt Accessibility

Olaf Jan Schmidt ojschmidt at kde.org
Wed Jul 16 13:30:00 CEST 2003

Hash: SHA1

[Maks Orlovich]
> An another option is what I've prototyped Klavi with. I've added a new
> type of plugin, xaccess, and a qtrc key to load a few plugins by name,
> and just make QAccessible broadcast ::updateAccessible to the loaded
> plugin.

I agree that it might be a good idea to allow for different
plugins/libraries here, with the possibility to configure which one
should be loaded, especially since we are not yet sure which bridging
solution the best and might wish to try out things. But I don't it is
necessary to load several ones, as I believe it is cleaner to define an
API for an assistive technology library that can be bridged to AT-SPI,
Klaviatura, or whatever. This way, we would not tie the assistive
technologies to any particular solution.

But I also agree with Volker that having a low level API between and the
bridge is important for keeping extended binary compatibility [1] between
different version Qt, which is important if we wish to have static linked
applications accessible as well.


[1] This means standard binary compatibility, but is more than that: e.g.
it is necessary that both sides of the API interpret even the internal
d-pointers in the same way.
- --
Olaf Jan Schmidt, KDE Accessibility Project
KDEAP co-maintainer, maintainer of http://accessibility.kde.org

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


More information about the kde-accessibility mailing list