[Kde-accessibility] kttsd and KSayIt etc...

[Olaf Jan Schmidt]

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

[Robert Vogl, So 01.02. 2004 21:45:21]
> As a newbie here, I don't know the actual state of the discussions and
> how far the overall KDE TTS concept has already been fixed.

Nothing has been fixed yet at all - since there are currently only three 
people (you, my brother, and me) involved.

> The runtime control of kttsd may be performed by a stand-alone tool
> named 'kttscontrol' (in the style of artscontrol). GUI and
> functionality of that tool is essentially the dialog that pops up if
> "restore" of the todays system tray of kttsd was clicked.

Interesting idea.
I will come back with some comments in a few days.

> Because a server alone makes no sense we need a bunch of clients.
> KSayIt easily could be reimplemented as a client for the above
> described kttsd. It's located in the system tray to speak the content
> of the clipboard by a single mouse click and can also offer the simple
> editor view like today.

I am wondering whether we should really have KMouth amnd KSayIt as 
seperate clients then - maybe it would then be better to merge the two, 
or to merge KSayIt and kttsdcontrol.

Gunnar, what do you think?

- -- 
Olaf Jan Schmidt, KDE Accessibility Project
KDEAP co-maintainer, maintainer of http://accessibility.kde.org

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

iEYEARECAAYFAkAnSA4ACgkQoLYC8AehV8c0TQCeI7utEm5PKkI2lbowE/mu8pKo
Xw4AoIrgNvR1u3ts+3N7oSEMgyamsv6U
=5/cD
-----END PGP SIGNATURE-----