| |
ZL3AI > APRDIG 03.02.03 14:30l 273 Lines 10248 Bytes #999 (0) @ WW
BID : 803-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 8/10
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<RZ6HXA<SP7MGD<IK6PYS<W4JAX<VK4TUB<
ZL2BAU<ZL3VML
Sent: 030131/0935Z @:ZL3VML.#80.NZL.OC #:58520 [Chch-NZ] FBB7.00i $:803-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Fw: RE: Incident Command Post Symbol
From: "Spider" <spider@rivcom.net>
Date: Mon, 27 Jan 2003 17:19:38 -0700
X-Message-Number: 49
----- Original Message -----
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
To: "Spider" <spider@rivcom.net>
Cc: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Monday, January 27, 2003 5:13 PM
Subject: Re: [aprssig] RE: Incident Command Post Symbol
>On Mon, 27 Jan 2003, Spider wrote:
>
>>From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
>>
>>>Looks like you can't create mixed-case/lower-case object names? I
>>>now have multiples of each object on my screen, some with
>>>lower/mixed-case (the way I created them), and some with all
>>>upper-case (the ones you created).
>
>>I just took control over...did not change anything manually. So it's
>>software?
>
>Yep. When you took over "CampTest", you changed it to "CAMPTEST".
>Same for "BaseTest" and "StagingT", you converted them to
>upper-case. The spec states that for objects and items the names
>are case-sensitive, so on my screen, I now have six objects instead
>of three.
>
>I'll bet Roger could fix this one in a jiffy. Let him know.
>
>While you're at it, find out if he supports Items yet. I'll place
>one on the map near the objects. I'll call it "Spider".
I see a stick man jogging.....Xastir took the Objects back I see. So it
looks like the two program are not cooperating....Cat fight!!
Jim
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 27 Jan 2003 19:25:48 -0500 (EST)
X-Message-Number: 50
On Mon, 27 Jan 2003, AE5PL Lists wrote:
>That's fine, Bob. But reverse engineering a program (which is what you
>are saying every author today should do) is not the way to have authors
>create standard interfaces.
No, no one ever had to reverse engineer anything. The documentation of
APRSdos was thorough and I was willing to answer any questions about any
nuance not covered in the voluminous docs:
Everything about SYMBOLS was in README\SYMBOLS.TXT.
Everything about the Protocol was in README\PROTOCOL.TXT
Everything about Weather was in README\WX.TXT
Everything about DFing was in README\DF.TXT
Everything about GPS Interfacing was in README\GPS.TXT
Everything about MOBILE OPS was in README\MOBILEs.TXT
Everything about Operations was in README\OPS.TXT
Everything about Marathons was in README\MARATHONS.TXT
Everything about Digipeaters was in README\DIGIS.TXT
Everything about SPACE was in README\SPACE.TXT.
Everything about Telemetry was in README\TELEMTRY.TXT
Everything about DX Cluser spotting was in README\DX.TXT
Everything about APRS and BBS's was in README\BBSNOTES.TXT
Everything about MAPS was in README\MAPS.TXT
Everything about Deadreckoning was in README\DR.TXT
Everything about Milemarks was in README\MILEMARK.TXT
Everything about Overlays was in README\OVERLAYS.TXT
Everything about COunties was in README\COUNTIES.txt
Everything about ALTNETS was in README\ALTNETS.TXT.
Everything about APRS Resources was in README\RESOURCE.TXT
Everything about Field Day was in README\FD.TXT
Everything about Traffic monitoring was in README\TRAFFIC.TXT
Everything about Boats was in README\BOATS.TXT
Everything about Aircraft or CAP was in README\AIRCRAFT.TXT
Everything about NTS Traffic handling was in README\NTS.TXT
Everything about Meteor Scatter with APRS was in README\METEORS.TXT
ANd so on for a total of 87 separate REAMDE files detailing every aspect
of APRS as designed into APRSdos.
>The fact remains, that for whatever reason, many things in APRSDos were
>not implemented and some things were implemented that are not in
>APRSDos. You can place (which you have) the blame squarely on the other
>authors, but I still maintain that by insisting an author reverse
>engineer APRSDos is a failure to communicate effectively the
>capabilities you wanted to see implemented.
I disagree 100% with your assertion.
1) Nothing in my posts is intended in anyway to lay blame or to in anyway
criticise the extremely good and well intended efforts of all the other
authors. They have done wonders for APRS. I admire them greatly and all
their work. I am only stating, however, that there were some things
omitted in many such efforts while they concentrated on the more immediate
issues they were working on. My job at this point, is to make sure that
they don't get forgotten in the long run...
2) No one had to reverse engineer anything. From day one in 1992 when I
began APRS, I thoroughly documented every single feature of APRS if for no
other purpose that to keep track of it all. And that documentation was
included in every copy of APRSdos... A total of 87 README files, each
with a FILENAME telling its meaning and purpose.
Bob
----------------------------------------------------------------------
Subject: RE: Incident Command Post Symbol
From: Curt Mills <hacker@tc.fluke.com>
Date: Mon, 27 Jan 2003 16:28:29 -0800 (PST)
X-Message-Number: 51
On Mon, 27 Jan 2003, Curt Mills, WE7U wrote:
>Looks like you can't create mixed-case/lower-case object names? I
>now have multiples of each object on my screen, some with
>lower/mixed-case (the way I created them), and some with all
>upper-case (the ones you created).
>
>Good thing we're testing this now, instead of when all heck breaks
>loose and we need this capability in a hurry!
What will happen is this: I'll continue to transmit the
mixed-case/lower-case objects, and you'll continue to transmit the
upper-case objects. Your software will think it has control of all
of the objects, but it really only has control of the upper-case
objects, which are new ones that you just created (separate from my
original three). My software will think it has control of the
mixed-case/lower-case objects, and it does, since you haven't
really messed with them.
My map view will be: Duplicate objects with same names, different
cases running around.
Your map view will be: Few objects, ping-ponging between two
locations as each of us transmits.
Kind'a funny! Let's get it fixed though.
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: Re: Fw: RE: Incident Command Post Symbol
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Mon, 27 Jan 2003 16:30:57 -0800 (PST)
X-Message-Number: 52
On Mon, 27 Jan 2003, Spider wrote:
>I see a stick man jogging.....
Good. That means you're seeing Items as well as Objects.
>Xastir took the Objects back I see. So it
>looks like the two program are not cooperating....Cat fight!!
Yep! That's what it looks like from your screen anyway. I see
these objects:
Spider
HELIBASE
ICP-TEST
StagingT
STAGINGT
CampTest
CAMPTEST
BaseTest
BASETEST
--
Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto: A tax on people who are bad at math!"
"Windows: Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: Re: Fw: RE: Incident Command Post Symbol
From: "Spider" <spider@rivcom.net>
Date: Mon, 27 Jan 2003 17:38:30 -0700
X-Message-Number: 53
----- Original Message -----
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
To: "Spider" <spider@rivcom.net>
Cc: "Roger Barker" <roger@peaksys.co.uk>; "Curt Mills"
<hacker@tc.fluke.com>; "TAPR APRS Special Interest Group"
<aprssig@lists.tapr.org>
Sent: Monday, January 27, 2003 5:30 PM
Subject: Re: Fw: [aprssig] RE: Incident Command Post Symbol
>On Mon, 27 Jan 2003, Spider wrote:
>
>>I see a stick man jogging.....
>
>Good. That means you're seeing Items as well as Objects.
>
>
>>Xastir took the Objects back I see. So it
>>looks like the two program are not cooperating....Cat fight!!
>
>Yep! That's what it looks like from your screen anyway. I see
>these objects:
>
> Spider
> HELIBASE
> ICP-TEST
> StagingT
> STAGINGT
> CampTest
> CAMPTEST
> BaseTest
> BASETEST
>
I would think I should have sent a delete packet out when I took control
and moved the objects. I'll let You and Roger figure that one out! See, I
am a nice guy! I only see what was there.hhmmm
time to move off the sig, I suppose too!
Jim
----------------------------------------------------------------------
Subject: Re: ARRL Public Service Manual regarding RACES
From: "Jack Smith" <jrs38801@bellsouth.net>
Date: Mon, 27 Jan 2003 18:36:51 -0600
X-Message-Number: 54
The AN/PRC-1099 Man portable. I knew it was still out there, but hadn't
seen one in years... Which in a way kind of validates my point. The
current usage of HF in the military is extremely limited. The only reason
why SF use HF is because as small as the single channel TacSat is (which
they use for military comms) it's still handy on occasion. But even they
only use it as a back-up system.
Which brings me to another point... Did you know that the 7th Army (Europe)
is using something very similar to APRS to track all the vehicles in the
Transportation Companies? I saw that while I was over there last month, and
thought it was funny. Since Bob works for DoD, I just have to wonder why
they didn't talk him into licensing a custom version of APRS instead of
buying the incredibly expensive version? It's even terrestrially based just
like APRS.
Never mind! I keep forgetting about the retired Generals employment
program! LOL In the past I even demonstrated APRS to CECOM (Comms and
Electronics Command) folks, and they loved it! Especially the TinyTrak
modules that I showed them. The price was right, and the size, too. But
they were only end users and engineers. Not the people with the purse
strings... I guess it didn't cost enough!
Jack
KE4LWT
----------------------------------------------------------------------
Read previous mail | Read next mail
| |