[Kde-accessibility] Re: accessibility.kde.org
Olaf Jan Schmidt
olaf@amen-online.de
Thu, 31 Oct 2002 12:41:51 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi JP, hi Chris!
[JP Schnapper-Casteras]
> Agreed, raising the profile would be a good idea. If anyone wants to
> step in and help me do this, it would be great, as I'm a bit
> overwhelmed with commitments at the moment.
I can help updating the site. Some weeks ago, you suggested discussing an=
=20
"agenda" for KDE Accessibility. As we are only very few people, this=20
should basically reflect the work currently done, plus a perspective for=20
things which will hopefully be done sooner or later.
My ideas where
1. Document existing programs on the web site (KMouth, KMousetool, KMag,=20
Speaker plug-ins, any other?)
I could do this.
2. Documentation of the Proklam work being currently done. This should=20
include answers to the questions:
What is Proklam?
How is cooperation with gnome-speech possible?
How do I use Proklam in my programs?
(explaination of dcop function, of the kspeech class, of the possible=20
changes to basic KDE parts like KTexteditor, and of the XML language used=
=20
by Proklam)
As Proklam needs to be coded first, an answer to the general ideas behind=
=20
Proklam might be enough for the start.
3. A concrete stragety paper for implementing an AT-SPI in KDE. Gunnar is=
=20
planning to come up with some ideas once KDE 3.2 is out, so we can=20
contact kde-core-devel for hints and ideas.
We will be lacking the time to implement all of this, but IMHO it would b=
e=20
great to decide upon a general stragety so that people interested in=20
accessibilty issues have the option to start coding small pieces.
I am also wondering about whether it might be possible to create a=20
kdeaccess package for KDE 3.2 or KDE 3.3 - once Proklam is ready and=20
programs like KMouth and the Speaker plug-ins are working with Proklam.=20
Pupeno wishes Proklam to go into kdelibs, but some of the plug-ins might=20
then go into kdeaccess. I might be also an idea to create kdeaccess-gnome=
=20
for interoperability bridges.
> There is probably some funding available for things like printing out
> flyers or packets for an upcoming KDE developer's event or working on a
> common, cross-desktop usability Human Interface Guide (HIG) that
> incorporates accessibility issues.
That sounds great.
Olaf.
- --=20
Meine Internetseiten:
http://www.GebetGenerator.de, http://www.amen-online.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj3BFv8ACgkQoLYC8AehV8d+4QCgz3pZ4zJPtzLr6rXMR2GOLhKL
RhQAnRTOsOZ8H+Hnqh8qdWhksK4Q2sXq
=3DpbR0
-----END PGP SIGNATURE-----