[Kde-accessibility] Our future

[Olaf Jan Schmidt]

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

[Volker Hilsheimer]
> A plugin solution seems to be a reasonable idea, but requires Qt to be
> present as a shared library (since the plugin will also link against Qt=
)
> - this is not a problem for KDE, but software vendors often tend to shi=
p
> Qt statically linked to avoid conflicts with existing Qt libraries.

Maybe we could use not a plug-in, but a shared library, that is only=20
called when present. What do you think, Pupeno?

> Plugin based solutions also tend to bring in all sort of trouble, e.g.
> difference in Qt versions the plugins and the applications depend on
> etc.

With a shared library, we would have this problem only if we change the=20
interface, which should happen quite seldom if we design it properly, and=
=20
we could make alll changes backwards-compatible.

> What I don't know though is how that plugin should handle the RPC, e.g.
> the requests for atk objects/interfaces from the accessibility client,

It shouldn't handle them.

The plug-in / shared library will just forward the informaton to ATK,=20
which is then forwarding it via Corba to the AT-SPI rtegistry, which is=20
then forwarding it to the clients.

- --=20
Olaf Jan Schmidt, KDE Accessibility team

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

iEYEARECAAYFAj3qTboACgkQoLYC8AehV8dQtACfcMPOVhQHu54ScMwPbydMXy2O
e9oAn2boz/rcQUnSN4K6c+pgWz3+ZFNo
=3D3Dud
-----END PGP SIGNATURE-----