<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Andreas Tønnesen wrote:<br>
<br>
<blockquote
cite="mid21904.194.196.35.3.1100776231.squirrel@webmail.gnist.org"
type="cite">
<pre wrap="">The plan is to redesign the IPC interface in a not to distant future. I
agree on you design points:
- A general GUI would benefit from using a cross platfor toolkit.
- The new IPC interface should allow for setting of olsrd parameters in
runtime.
</pre>
</blockquote>
<br>
So, you are going to rewrite the IPC ? <br>
Then I'd like to provide some of our (detailed) ideas regarding the IPC
interface:<br>
<ul>
<li>Creating a IPC plugin which handles all the remote connections.
Now, we have the IPC inside of olsrd with an own port and
configuration, we have the dot_draw plugin with an own port and
configuration, etc.</li>
<li>According to Thomas the current GUI is (more or less) guessing
the "state" of olsrd instead of knowing it. That should be corrected.</li>
</ul>
<br>
<blockquote
cite="mid21904.194.196.35.3.1100776231.squirrel@webmail.gnist.org"
type="cite">
<pre wrap="">- The IPC interface will be a superset of the dot_draw plugin(the data
might not be delivered in that excact format) so that a GUI can visiulize
the topology.
</pre>
</blockquote>
<br>
What do you mean with "the data might not be delivered in that exact
format" ?<br>
<br>
<br>
<blockquote
cite="mid21904.194.196.35.3.1100776231.squirrel@webmail.gnist.org"
type="cite">
<pre wrap="">We are looking for people interested in doing a GUI when the new IPC
interface is ready, so keep that in mind if you are into these things :-)</pre>
</blockquote>
<br>
Just to get an idea - is "a not to distant future" still in 2004 ? <br>
I gladly help <span class="moz-smiley-s1"><span> :-) </span></span><br>
<br>
Marek<br>
</body>
</html>