[Kde-accessibility] Qt and accessibility on Unix

[Olaf Jan Schmidt]

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

[Christian Fredrik Kalager Schaller]
> In fact libraries that KDE already use like pkgconfig actually contains
> code cut and pasted from glib, and if GStreamer ends ups being shared
> between GNOME and KDE (which we are working with Tim Janssen to make
> happen), then there are also another major component that use this
> basic utility library.

Is it consensus among KDE core developers that there will be glib=20
dependencies in future KDE versions? The main reason I was expressing=20
ideas to avoid glib dependencies was just that I am not at all familiar=20
with KDE core issues and do not wish KDE Accessibility to force KDE into=20
a direction the rest of KDE opposes.
 If KDE already has decided to have a glib dependency in future, this=20
might make coding the bridges easier.

Pupeno, what do you think? Should we ask on kde-core-devel about what to=20
do about this?

While I think that doing a bit extra work to avoid too many dependencies=20
is better than adding unnecessary dependencies, it would not make much=20
sense trying to avoid glib dependencies if KDE will depend on glib=20
anyway.

> Hope I didn't offend anyone with this mail, I am just so tired of
> Microsoft winning because we divide and conquer ourselves.

Nobody in the KDE Accessibility Project spoke of dividing. Our bridges=20
will make full use of existing accessibility solutions, and we are very=20
grateful for all the work that has already been done outside of KDE.

I can, however, understand that TrollTech does not wish to add glib=20
depencies to Qt, as Qt is cross-plattform.

I personally would not mind glib dependencies for Unix versions of Qt or=20
for KDE. I just think that our small project does not have the authority=20
to decide in whether KDE should have a glib dependency for all of KDE, we=
=20
can only agree to a glib dependency of for the accessibility bridges.


Olaf.

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

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

iEYEARECAAYFAj3rtxMACgkQoLYC8AehV8fJKwCg7ewmIaIYo/bLT7gzxLm+5xz/
5gUAn3rDfwTMpj24QSw4MEQEBT3KB87I
=3DdwzD
-----END PGP SIGNATURE-----