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

[Pupeno]

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

Hi, I'm the original developer of KTTSD, no longer mantaining the project but 
I think my knowledge of it might come usefull now.

On Sunday 01 February 2004 17:45, Robert Vogl wrote:
> 1.) kttsd
>
> In this context kttsd should be designed as a pure server-daemon that
> offers a well defined interface to its clients e.g. via DCOP or
> IPC-Sockets. The interface should receive the text to speak and implements
> elementary functions like 'start', 'stop', 'pause'. All lowlevel
> functionality like queue-handling, prioritization, sentence segmentation or
> whatever should be addressed to the daemon to keep the clients as simple as
> possible. As a daemon kttsd is completely invisible for the user (like KDEs
> sound server artsd), i.e. it doesn't require any GUI functionality. The
> configuration of kttsd should be performed via a KDE Controllcenter Module
> (KCM) and a set of plugins for the several existing TTS systems. The KCM
> may offer a checkbox of type: "Start kttsd on KDE startup".
All that, excep asyncronus stoppping is already implemented and working, 
exactly as you describe it (I'm proud that I reached the same design as the 
mind of another developer :)

> 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.
This is not implemented but is a good idea, if there's something to control at 
all.

> 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.
> The setup dialog is no longer required as well as the speaker stuff since
> both is delegated to kttsd and its KCM.
I agree, good luck with your developing! :)
- -- 
Pupeno: pupeno at pupeno.com
http://www.pupeno.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAIBODtCepaMf3unIRAg4KAJ9IeBKf9Gq5HJFjXFSZ83jBqoBEDACfdIdU
LWYr76WWR8VWHR0066Cty2s=
=JHY+
-----END PGP SIGNATURE-----