Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Curt, WE7U" <archer@eskimo.com>
To: Martin Ewing <martin@aa6e.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: newbie question - hamlib and gMFSKX
Date: Wed, 5 May 2004 09:14:23 -0700 (PDT)	[thread overview]
Message-ID: <Pine.SUN.4.58.0405050906030.23780@eskimo.com> (raw)
In-Reply-To: <40990E79.5000701@aa6e.net>

On Wed, 5 May 2004, Martin Ewing wrote:

> Sorry to give any offense, slight or

;-)  I was just kidding.  Just making sure you knew of other quality
stuff that's out there.


> I confess to near total ignorance of APRS, but I'm glad to hear of good
> work being done there.

You should try Xastir hooked up to an internet port just to see
what's out there.  I'm involved in firenet also, where we have an
alternate network that we use to plot both APRS trackers and
weather/fire/river gauges, quakes, etc.  firenet.us port 2023.
Your map will really light up if you connect there.


> In a way you prove my point, however. I wouldn't count Cygwin support as
> "Windows compatibility". [Although I have claimed that Python support
> is. Go figure.] IMO, we need to use wxWidgets (wxwindows.org) or similar
> cross-platform GUI framework to get apps that work nicely across
> Windows, Mac, and Linux platforms. (Java is an alternative, too.) We can
> handle the GUI part, but does anyone have a cross-platform soundcard
> strategy?

We have a Java application at work that our group wrote.  Runs on
Solaris, WinNT, Linux, and now WinXP.  Wonderful language for our
automated testing.

I agree with you that Cygwin isn't Windows compatibility.  It's a
hack.  A useful hack, but a slow one.  Most Windows people won't go
through the hassle, but for Unix people who are stuck on Windows at
work, or have other restrictions here and there, it's a useful tool.

I'm not sure that Xastir could try for a native Windows port without
a heck of a lot of work.  We use so many of the Unix system calls
that aren't supported well (or at all) on Windows.  We're
multi-threaded too.  Currently we use the Motif widget set, and it
would be a big hassle to even change to a new widget set.  I'm the
main GUI guy (and threads guy, and mutex locks guy, and topo map
guy).

Soundcard... Depends on what you're after.  We support some limited
uses of AGWPE.  We can also use the soundcard interface to do
packet.  Windows people can also use AGWPE.

If you're talking someone universal uses other than packet, can't
help you there.  Sorry.

--
Curt, WE7U			    archer at eskimo dot com
Arlington, WA, USA		http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

  reply	other threads:[~2004-05-05 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-01 14:06 newbie question - hamlib and gMFSK N5NW Marty
2004-05-01 14:37 ` Martin Ewing
2004-05-01 15:34   ` Andrea Borgia
2004-05-01 17:58     ` Martin Ewing
2004-05-03 16:14   ` Curt, WE7U
2004-05-05 15:55     ` Martin Ewing
2004-05-05 16:14       ` Curt, WE7U [this message]
2004-05-05 19:03         ` cross-platform sound (was newbie...) Martin Ewing
2004-05-03 22:56   ` newbie question - hamlib and gMFSK Stephane Fillod
2004-05-01 15:26 ` Andrea Borgia

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=Pine.SUN.4.58.0405050906030.23780@eskimo.com \
    --to=archer@eskimo.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=martin@aa6e.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox