All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Douglas Cole" <n7bfs@qwest.net>
To: Michael Melanson <ve3mtm@rac.ca>,
	LINUX HAMS MAILING LIST <linux-hams@vger.kernel.org>
Subject: Re: KDE EchoLinux client development started
Date: Thu, 10 Apr 2003 21:11:43 -0700	[thread overview]
Message-ID: <200304102111.43686.n7bfs@qwest.net> (raw)
In-Reply-To: <200304102146.01378.ve3mtm@rac.ca>

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



  reply	other threads:[~2003-04-11  4:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 20:04 KDE EchoLinux client development started Michael Melanson
2003-04-08 13:19 ` M Taylor
2003-04-10 21:45   ` Michael Melanson
2003-04-11  4:11     ` Douglas Cole [this message]
2003-04-11 20:44       ` Jose A. Amador
2003-04-12 19:16         ` KDE EchoLinux client development started - SERVER? Bill Vodall - WA7NWP

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200304102111.43686.n7bfs@qwest.net \
    --to=n7bfs@qwest.net \
    --cc=linux-hams@vger.kernel.org \
    --cc=ve3mtm@rac.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.