KDE EchoLinux client development started

KDE EchoLinux client development started

[Michael Melanson]

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 
experience with development under KDE and with a modest amount of free time 
(I don't ask much), please email me (ve3mtm@rac.ca). I could also use help 
with a webpage, although in a pinch I could do that myself.

The project was just approved by SourceForge for hosting at 
http://sf.net/projects/kecholink so I want to get started on work. It 
shouldn't take too long to get a working client going, since the underlying 
EchoLinux program takes care of the protocol.

Thanks in advance,

Michael VE3MTM
ve3mtm@rac.ca

73 33

Re: KDE EchoLinux client development started

[M Taylor]

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

Re: KDE EchoLinux client development started

[Michael Melanson]

I have started, pending the acception of the Sourceforge project, but I 
haven't uploaded anything yet (It's not much yet)

As for the Qt/GTK debate, I can do either. I chose Qt because that's what I've 
used more, but that's by no means a binding reason. I have used GTK, but 
that's a long time ago and not much at that. If the general concensus is to 
use GTK, then I'll register a new SF project with a non-KDE name

This project will not implement the EchoLink protocol. That's done by 
EchoLinux, which will run as a child process of this program.

I welcome any other input


- Michael VE3MTM
ve3mtm@rac.ca

73 33

Re: KDE EchoLinux client development started

[Douglas Cole]

On Thursday 10 April 2003 14:45, Michael Melanson wrote:
> I have started, pending the acception of the Sourceforge project, but I
> haven't uploaded anything yet (It's not much yet)
>
> As for the Qt/GTK debate, I can do either. I chose Qt because that's what
> I've used more, but that's by no means a binding reason. I have used GTK,
> but that's a long time ago and not much at that. If the general concensus
> is to use GTK, then I'll register a new SF project with a non-KDE name
>
> This project will not implement the EchoLink protocol. That's done by
> EchoLinux, which will run as a child process of this program.
>
> I welcome any other input
>
>
> - Michael VE3MTM
> ve3mtm@rac.ca

Whip me beat me hang me out to dry, but if I had a choice, having an ncurses 
interface so that one could run it from a console/limited hardware would be 
kinda fun :^)

Second choice would be QT.
Third would be Kylix.
Fourth would be GTK...
Just my two pennies.

Thanks for sharing what my dumb brain just doesn't seem to want to do (write 
software).

73

-- 
Douglas Cole   N7BFS
Spokane IRLP node owner
AMSAT#26182 , K2 # 544
http://www.users.qwest.net/~cdoug3
Registered Linux user # 188922

Re: KDE EchoLinux client development started

[Jose A. Amador]

Not only for this thread, but for ANYTHING ELSE I agree with the choices 
of N7BFS. If it MUST be graphical (say, SSTV, waterfalls or some other
funny
indicator) let it be so. If it is not, and text is sufficient, it makes
sense to me to have escalating choices that range from text to the
fanciest
GUI, so either a 486 and text only (ncurses) or a P4 with a superwhizbang
video card perform well with it with the proper configuration choices.
Please don't forget the poor guy if it makes sense.

73 de Jose, CO2JA

On Thu, 10 Apr 2003 21:11:43 -0700, "Douglas Cole" <n7bfs@qwest.net>
said:
> On Thursday 10 April 2003 14:45, Michael Melanson wrote:
> > I have started, pending the acception of the Sourceforge project, but I
> > haven't uploaded anything yet (It's not much yet)
> >
> > As for the Qt/GTK debate, I can do either. I chose Qt because that's what
> > I've used more, but that's by no means a binding reason. I have used GTK,
> > but that's a long time ago and not much at that. If the general concensus
> > is to use GTK, then I'll register a new SF project with a non-KDE name
> >
> > This project will not implement the EchoLink protocol. That's done by
> > EchoLinux, which will run as a child process of this program.
> >
> > I welcome any other input
> >
> >
> > - Michael VE3MTM
> > ve3mtm@rac.ca
> 
> Whip me beat me hang me out to dry, but if I had a choice, having an
> ncurses 
> interface so that one could run it from a console/limited hardware would
> be 
> kinda fun :^)
> 
> Second choice would be QT.
> Third would be Kylix.
> Fourth would be GTK...
> Just my two pennies.
> 
> Thanks for sharing what my dumb brain just doesn't seem to want to do
> (write 
> software).
> 
> 73
> 
> -- 
> Douglas Cole   N7BFS
> Spokane IRLP node owner
> AMSAT#26182 , K2 # 544
> http://www.users.qwest.net/~cdoug3
> Registered Linux user # 188922
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
-- 
  Jose A. Amador
  co2ja01@fastmail.fm

-- 
http://www.fastmail.fm - Consolidate POP email and Hotmail in one place

Re: KDE EchoLinux client development started - SERVER?

[Bill Vodall - WA7NWP]

> > > This project will not implement the EchoLink protocol. That's done by
> > > EchoLinux, which will run as a child process of this program.


EchoLink is great.

Having a nice client on Linux will be a really good thing.

What about the other side?   It would be useful, at times,
to have a local Echolink style server.  It's not always
necessary nor desireable to join  the big group.

Is anybody working on or thinking about an open server?

73,
Bill - WA7NWP