[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-accessibility
Subject:    [Kde-accessibility] Dependencies
From:       Olaf Jan Schmidt <olaf () amen-online ! de>
Date:       2002-11-27 0:26:03
[Download RAW message or body]

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

Hi!

As there was some talk of having GNOME dependencies in kde-core at 
compile-time, I was wondering whether we are talking about different 
approaches here. My understanding was that a simple generic KDE 
accessibility framework (call it KATK if you want) might be bridged to 
ATK or AT-SPI in a library which is independent of any other KDE code.

While it would be a good idea to base Qt itself on ATK and thereby make 
all Qt and KDE applications accessible without much other work, this is 
beyond our scope, so we will need some Qt-ATK bridge anyway - either in 
kde-core, or better in an optional package.

There is already some functionality in Qt and DCOP which we could extend 
to create a very simple KATK. We would not need to implement a complete 
accessibility framework all at once, as making KDE application export 
their GUI elements to AT-SPI would already be a huge step. The question 
how KDE applications could get other information about other applications 
could be addressed later. Our first goal should be just to make sure that 
KDE applications are seen by AT-SPI, so assistive technologies work also 
with KDE applications.

The properties of any named QObject can already be accessed via DCOP. The 
only problem with KDE objects like menus is that often some of their 
sub-objects are not named, so they are invisible for DCOP (which could be 
changed).

Another strategy would be to extend QAccessibleObject in cooperation with 
TrollTech, so that the properties of all QObjects can be reached, not 
just the original Qt objects.

Anyway, what we would need to add for an KATK solution would be 
information about which QObjects are currently shown in which window, 
where the cursor currently is, and a notification of any changes.

What else would we need to implement some basic KATK?

Olaf.

- -- 
Olaf Jan Schmidt, KDE Accessibility team
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj3kERwACgkQoLYC8AehV8fu1gCfaNwgnDKbCaPcryjQYKGyAfib
Tr4AnjYR0UkN/bUH164KWZXe8OfxYedv
=tyhU
-----END PGP SIGNATURE-----

_______________________________________________
kde-accessibility mailing list
kde-accessibility@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-accessibility
[prev in list] [next in list] [prev in thread] [next in thread]