From mboxrd@z Thu Jan  1 00:00:00 1970
From: M Taylor <mctylr@privacy.nb.ca>
Subject: Re: KDE EchoLinux client development started
Date: Tue, 8 Apr 2003 14:19:09 +0100
Sender: linux-hams-owner@localhost
Message-ID: <20030408141909.A30053@pull.privacy.nb.ca>
References: <200304072004.55533.ve3mtm@rac.ca>
Mime-Version: 1.0
Return-path: <linux-hams-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <200304072004.55533.ve3mtm@rac.ca>; from ve3mtm@rac.ca on Mon, Apr 07, 2003 at 08:04:49PM +0000
List-Id: <linux-hams.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Michael Melanson <ve3mtm@rac.ca>
Cc: Linux-Hams <linux-hams@vger.kernel.org>

On Mon, Apr 07, 2003 at 08:04:49PM +0000, Michael Melanson wrote:
> Hi everyone
> 
> In light of the fact that there is no good GUI client for EchoLinux, the Linux 
> implementation of EchoLink, I am starting work on a KDE/Qt client called (you 
> guessed it) KEchoLink and any help would be appreciated. Anyone with 

Have you really started writing KEchoLink program, or have you just
created a sourceforge project? I don't see any source code at
the sourceforge.net/projects/kecholink page, either as a download or
via CVS.

Is the Echolink protocol documented and available?

-ve1mct