--===============0370993464==
Content-Type: multipart/signed;
  boundary="nextPart14800904.34i2RALPl2";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart14800904.34i2RALPl2
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Rob Taylor wrote:
>> Let's remember that DCOP was implemented in a very short period of
>> time, and was dead simple - MUCH less complex than dbus is - and
>> people used it heavily and successfully for lots of real
>> functionality.
>
>And KDE never wrote a sucessful accessibility framework with DCOP.

The way you phrase it, it seems like DCOP is responsible for it. It's not.=
=20
There was no accessibility framework like AT-SPI at all, nor any work to=20
create it AFAIK.

However, parts of an accessibility framework, including the text-to-speech=
=20
interface, were written and even used DCOP.

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

--nextPart14800904.34i2RALPl2
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBHYNxPM/XwBW70U1gRAlYjAJ9t8iaSIEsQbx7WFejcvprBUO2qOwCcCOI3
yhaio4mBoPWp3eUKL0wZBEk=
=Qfpt
-----END PGP SIGNATURE-----

--nextPart14800904.34i2RALPl2--

--===============0370993464==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dbus mailing list
dbus@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dbus

--===============0370993464==--