<HTML>
<HEAD>
<TITLE>DeviceConfig</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffff">
<p>
<A HREF="hier.html"> view hierachy</A>
<p>

<H2> Introduction</H2>


This directory contains the different signal mechanisms.
The Yaf library mostly uses a simple Sender/Listener communication.
The listener must derive from a class and overwrites the "notify"
method to get the signal from the sender. 
It can register itsself at the sender.
<p>
But there are a few areas where yaf depends on the toolkit signal
mechanism. These areas are described in this directory.
A new toolkit must implement the core classes with the
same functionaliy and then it should work.
<p>

The signal mechanism in the core directory must deal with two problems:
<pre>
1 coordination between threads over pipes
2 deliver of the stdin/stdout/stderr messages of a forked process

1. Is solved with the class
2. work in progress


It seems that GTK/GTK-- makes it harder than QT to solve 
problem 1. 
After 2. is solved I will start a GTK/GTK-- port


You dont have to deal with this classes if you dont
want to implement eg. a new GTK Signal mechanism.

</pre>

</BODY></HTML>

