Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Braddock Gaskill <braddock@braddock.com>
To: "Curt, WE7U" <archer@eskimo.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: APRS library?
Date: Wed, 10 Mar 2004 18:18:55 -0600	[thread overview]
Message-ID: <20040311001855.GA20040@braddock.com> (raw)
In-Reply-To: <Pine.SUN.4.58.0403100901380.25481@eskimo.com>

On Wed, Mar 10, 2004 at 09:04:18AM -0800, Curt, WE7U wrote:
> Curt.  One of the Xastir guys.

After doing a bit more digging and asking around, it seems like your
Xastir (107k lines of code), and Ian Wades perl parser (~55 pages of
code), are the ONLY open source APRS parser implementations, and that
creating a fresh one will be a massive job.  It's a shame to see so
much good non-commercial software is close-sourced in the HAM
community.

Do you have any recommendations on perhaps a good place to hook into
Xastir to get the APRS data in a parsed standardized format?  I was
thinking I could pretty easilly externalize the DataRow structure via
a documented TCP port interface so that people could realistically
write new APRS clients.  I could write a little client library to
remotely retrieve parts of the DataRow structure via TCP, and allows
the application programmer to register "data update" callbacks when an
entry is changed.

Any suggestions would be welcome.  I'm hoping to do this in the next
two days before a local HAM weather balloon launch.

	-braddock


  reply	other threads:[~2004-03-11  0:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  2:39 APRS library? Braddock Gaskill
2004-03-10 17:04 ` Curt, WE7U
2004-03-11  0:18   ` Braddock Gaskill [this message]
2004-03-11  0:34     ` Curt, WE7U
2004-03-11  9:11 ` Robert Jenkins
2004-03-11  9:52 ` Margaret Leber

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=20040311001855.GA20040@braddock.com \
    --to=braddock@braddock.com \
    --cc=archer@eskimo.com \
    --cc=linux-hams@vger.kernel.org \
    /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