ktalkwake Files

1. Definition
2. Running without ktalkd4
3. Running with ktalkd4
4. Command line options
5. Installation
6. End

-----------------------------------------------------------------------

	1. Definition
ktalkwake is a simple kde4 program released under the terms of the GNU/GPL. It
helps the user when an incoming talk call arrives.

	2. Running without ktalkd4
On some systems konsole (the kde's default terminal emulator) doesn't write any
entry into the utmp service. Users are not notified of any incoming talk calls
on their terminal. The notification usual arrives through knotify4 that spawns
a short term lived tray pop-up.

knotify4 has the ability to run an external program to exhibit the
notification.  Launch "System Settings" and browse through "Application and
System Notifications" > "Message Notifications". Choose the tab "Applications"
and then select "Local System Message Service" as "Event source".  Check "Run
Command" and add the path to ktalkwake followed by "--message %s"

The next time an incoming talk call is received a pop-up is spawned offering to
the user the choise to pick it up or refuse it. If the user picks up the call
the pop-up vanishes and konsole is run with the necessary commands to answer.
Konsole will run ytalk if it was present at compile time or it will fallback to the "classic" talk client.

Unlike the knotify4 pop-up this is not a tray one and it won't disappear after
few seconds. The user will still find the small ktalkwake window on the
foreground after he/she will be returned to his desktop. Accepting the call
after a while has the good side effect of dialing back the remote caller.

	3. Running with ktalkd4
The other (and more friendly) way to use ktalkwake is to let the talkd to
invoke it. I wrote a modify version of talkd (the one from netkit 0.17) that
can notify the kde user directly, not involving knotify4. After compiling and
installing ktalkwake all you need to do is to remove the "traditional" talkd
from the system (if any) and then compiling and installing ktalkd4 (note: it's
not a fork of ktalkd).

	4. Command line options
It is useless for the user to invoke ktalkwake directly. Anyway there are two
command line long options:
  --message <message>       the output from kwrited (actually used by knotify4)
  --respond <user@host>     respond to user on host (actually used by ktalkd4)

	5. Installation
Unlike most source packages, ktalkwake lacks a full autotool layout. I think
it's unnecessary in an environment ready to compile kde packages. Having a
running Kde desktop, cmake, make, Qt and Kde headers is an obvious
precondition.  Anyway the configure script will check for the presence of
cmake, install, konsole and ytalk. Each of there programs may be specified with
the complete path on the command line after the flags -c, -i, -k and -y.
The -p option specifies the installation prefix (default /usr).

	6. End
If anyone has the goodwill to translate this README into a less clumsy english, he/she is warmly welcome.

Lucio Tomarchio
Thu Jan 27 19:58:46 CET 2011