<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Andrew-<br>
I'm glad you finally popped up on the list. I was in such a rush
to get to the airport after DCC that I misplaced your contact
information (and my brand new TH-D72A). Based on what little I saw
at DCC, you're well on the right track for a cross-platform client.
I hope you make the decision to "go public" with your code. There
are a number of quite talented developers on this list that might
just prove that "all of us are smarter than one of us." I don't
want to rush you or try to force you down a path you don't like, but
what license are you considering releasing your client under?<br>
<br>
John Gorkos<br>
AB0OO<br>
(the AVRS author, for better or worse...)<br>
<br>
On 11/09/2011 10:40 PM, Andrew P. wrote:
<blockquote cite="mid:BLU156-W5085C1109C6FB6249072E5B8DC0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
Hi, Georg.<br>
<br>
Thanks for the "encouraging words". :-) Good thing I've been a
professional software engineer for 30 years (!), so I've
developed a pretty tough hide regarding user complaints.<br>
<br>
Re: targets: I'm writing my app in Java, so it's very
deliberately "write once, test everywhere." :-) I've already
successfully run the same pre-alpha distro on Windows XP and
Linux (Fedora Core dialects); when I get it a little further
along, I'm going to see if I can find a Mac owner to try it,
too. But I still have a bit of work to do (currently 14 tasks
to-do on my work list before I'm ready to send the alpha release
to Bob for evaluation, and one of those tasks is the first draft
of the user manual). Once Bob (and anyone else he recommends)
has had a chance to shoot holes in it, I'll be ready to release
it to the general ham public.<br>
<br>
I met the AVRS author at the ARRL/TAPR DCC this year, and he
told me about his library. I've been working on my application
independently since June. At this point, considering that this
program started as a training exercise in APRS system
engineering, I'm probably going to keep what I wrote myself for
a while longer, until the app's internal API's settle down a bit
more. Doesn't mean I'm not going to look at his AVRS stuff, and
see if there is a good convergence point for his library and
mine.<br>
<br>
So, back to the hack. I'd like to have it out there before it's
completely obsolete. :-)<br>
<br>
Andrew KA2DDO<br>
Berwyn, Pennsylvania U.S.A.<br>
<br>
<br>
<div>Date: Wed, 9 Nov 2011 12:58:18 +0100<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:georg@op-co.de">georg@op-co.de</a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
Subject: Re: [aprssig] questions about the Bulletin Screen
"billboard" concept<br>
<br>
<pre>* Lynn W. Deffenbaugh (Mr) <a class="moz-txt-link-rfc2396E" href="mailto:ldeffenb@homeside.to"><ldeffenb@homeside.to></a> [2011-11-09 03:49]:
> >Looking forward to some good advice.
> Be ready to do it, and re-do it. What platform are you targeting
> your application to if I may ask?
In case it is Java based, maybe you can make use of (and contribute to)
the APRS parser/encoder which is part of AVRS:
<a moz-do-not-send="true" href="http://sourceforge.net/projects/avrs/" target="_blank">http://sourceforge.net/projects/avrs/</a>
It would be great for the community as well as for the APRS standard to
have a strong multi-platform library which can be plugged into own
projects. Maybe together we can make that vision come true!
> And if you're planning to release it to the general amateur radio
> public, you should probably read G4ILO's excellent description of what
> you can expect from your user base:
>
> <a moz-do-not-send="true" href="http://blog.g4ilo.com/2010/10/advice-to-amateur-programmers.html" target="_blank">http://blog.g4ilo.com/2010/10/advice-to-amateur-programmers.html</a>
However, you should not take the advice too serious. Most of the
feedback I'm getting for APRSdroid is very positive. The only
significant exception are people too impatient to wait for an APRS-IS
passcode.
73 from Germany,
Georg DO1GL
--
APRSdroid - Open Source APRS Position reporting and Mapping on Android
<a moz-do-not-send="true" href="http://aprsdroid.org/m" target="_blank">http://aprsdroid.org/m</a> ++ <a moz-do-not-send="true" href="https://market.android.com/details?id=org.aprsdroid.app" target="_blank">https://market.android.com/details?id=org.aprsdroid.app</a>
</pre>
<br>
_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a></div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>