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

Hi!

On the kde-accessibility mailing list, we agreed on importing an icon=20
theme and three applications into KDE CVS for KDE 3.4. Most of these=20
would go into kdeaccessibility, but some might be better placed in=20
kdelibs or kdeaddons, and we would be happy to have advice on this.

Sorry for the long mail and for crossposting, but in this case it was=20
necessary since this is highly relevant to both lists.

If there are no objections in the coming days, I will ask the authors to=20
do the move until end of next week.


1. Monochrome icons: This is important for partially sighted people that=20
need high contrast colour settings. Using Gunnar's recently commited icon=20
effect, they can be coloured in the current foreground and background=20
colours if we define the appropriate meta-themes. (Which includes=20
changing the meta-theme kcm to also store icon effects.)
I suggest importing it into kdelibs/pics/, to be in the same module as all=
=20
other settings for partially sighted people, but kdeaccessibilitry is=20
also an option.

http://kde-look.org/content/show.php?content=3D18317


2. kdenonbeta/kbstateapplet: This is a small applet that shows the state=20
of the all modifier keys. Apart from being important for people who use=20
accessibility features like stick keys, this is handy if your keyboard=20
does not show the state of caps lock. (module kdeaccessibility)


3. kdenonbeta/kttsd: A speech synthesis framework for KDE. It is already=20
optionally supported by KMouth; having it in kdeaccessibility simplifies=20
the code. It has become quite stable now, and a release will be announced=20
on Sunday. (module kdeaccessibility)

kdenonbeta/kttsd/app-plugins/ contains plugins for konqueror, katepart and=
=20
kate (support for kpdf is also planned). These have a build dependency on=20
kdebase and a runtime dependency on kttsd (or maybe KSayIt in future,=20
depending on usability discussions). I suggest to move them to kdebase,=20
since they are very small and the code can easily be changed to only show=20
the menu item if kttsd is installed. Another option would be kdeaddons,=20
of course.

kdenonbeta/kttsd/libkttsd/ has some very small files for sending DCOP=20
messages to kttsd. Since there is no build dependency on kttsd, it could=20
either go into kdelibs to make kttsd support for KDE applications easier,=20
or into kdeaccessibility.


4. KSayIt: This is a frontend for reading out longer texts. It interface=20
is different from KMouth, which is focussing on smaller messages, so we=20
would not have real duplication here. It contains a front end for kttsd=20
functionality to navigate through a text, which is important to make this=20
usable to end-users. KSayIt supports kttsd; having it in KDE CVS will=20
again simplify code. (module kdeaccessibility)

http://www.kde-apps.org/content/show.php?content=3D10028


Olaf

=2D-=20
KDE Accessibility Project

--nextPart73516720.q11Ar3pkVn
Content-Type: application/pgp-signature

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

iD8DBQBBuYfVoLYC8AehV8cRApwIAKCSD8/mgTKlPw/wC/0BupQo/BGbmQCgmtW/
gMAGrPc35qxAHxB1vGKMi2Y=
=PWLD
-----END PGP SIGNATURE-----

--nextPart73516720.q11Ar3pkVn--