| |
ZL3AI > APRDIG 03.02.03 14:30l 210 Lines 9584 Bytes #999 (0) @ WW
BID : 798-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 3/10
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<VK7AX<ZL2BAU<ZL3VML
Sent: 030131/0920Z @:ZL3VML.#80.NZL.OC #:58515 [Chch-NZ] FBB7.00i $:798-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Mon, 27 Jan 2003 07:00:45 -0600
X-Message-Number: 11
>-----Original Message-----
>From: Bob Bruninga [mailto:bruninga@usna.edu]
>Posted At: Sunday, January 26, 2003 11:55 PM
>Subject: [aprssig] RE: APRS Symbols (versus Windows ICONS)..
>
>Thus the SPEC does not necessarily fully represent what I
>designed APRS to do, but represents the lowest common
>denominator. To see what APRS is supposed to do (but without
>pretty maps) the only baseline is APRSdos. Although I do not
>expect anyone to find APRSdos attractive at all in today's PC
>environment, it still implements 100% of what was the design
>objective of APRS. An NO OTHER PROGRAM has fully implemented
>all of the fundamentals.
That's fine, Bob. But reverse engineering a program (which is what your
are saying every author today should do) is not the way to have authors
create standard interfaces.
>>And, I submit, the fault of you by not doing a good job in conveying
>>these ideas, hence their omission from the Spec.
>
>I find that accusation offensive, arrogant, self richeous and
>totally unfounded by someone with no hindsight who was not
>around during those painful years. I did everything in my
>
>Your insinuation that it is my fault is the most outlandish
>statement I have ever heard!
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. If someone decides not to
implement one of your ideas that you consider critical to APRS's
operation, then you have not communicated that criticality to them. You
may have told them, but communication requires the acceptance and
understanding of the recipient, as well.
>>A major problem with your implementation of symbols in APRSDos is the
>>lack of uniform symbols
>
>There was never any intention to be uniform! The EYEBALL and
>Tornado and Hurrricane symbols to name a few were intended to
>be BIG. Others were intended to be small. Others expand to
Bob, I wasn't referencing size. I was referencing all programs using
the same symbol for the same thing.
>cover the area affected as you zoom. SO your insinuation of
>a "problem" is your lack of understanding of the intent of
>such symbols in APRS. ANd a lazy acceptance of a simplistic
I was not insinuating anything. I was stating a fact. There is no
common symbol set for APRS GUI's and part of the reason is the there is
no way to pull these from APRSDos which, as you stated before, is the
foundation of the APRS displays.
>Yes, "Taking things into account" is the job of any good
>programmer. I do not need to hold anyone's hand (nor would
>they listen) to tell them how to convey the SYMBOL type
>variable. At their resistance, I left it up to them to
>figure out how they wanted to do it, but the fact remains, none did.
No one is asking you to hold their hand. But this sub-thread was
started by you slamming Windows and the other client authors for not
implementing symbols the way APRSDos does. And everyone did convey the
symbols the best way they saw fit because they had no other firm
specification to go by.
>APRS WAS DESIGNED TO CONVEY THIS BY COLOR. BUT I NEVER
>INSISTED THAT ANY OTHER AUTHOR DISPLAY THOSE VARIABLES IN
>COLOR. BUT I DID INSIST THAT SYMBOLS HAVE THE VARIABLE OF
>"TYPE" AND THAT THEY SHOULD CONVEY THAT INFORMATION TO THE
>USER IN A VISIBLE WAY.
Where did you "insist" this? There are client applications that have
been written and/or maintained by authors who were not involved, as you
put it, "those painful years". Slamming those authors or the authors
that were involved when there is no specification is not the solution.
>Whereas in APRSdos, this is conveyed by the color of the
>symbol. But I would NEVER insist that any other programmer
>do it in color, but I am very disappointed that none of the
>other authors display this SYMBOL TYPE variable on the map
>for EASY assessment by people looking at these maps (without
>haivng to go dig for it)...
Again, there is no specification that this should be done. Short of
reverse engineering APRSDos, don't expect authors to be mind readers.
And don't slam other authors for not adopting these unwritten concepts
(being listed on this sig is not documentation) because they believe
other things may be more important.
>I absolutely agree to all of the above, except for the one
>where you conclude that the omission of this "type"
>information from the display is "not" an incomplete
>application. I say they are incomplete and can do a better
>job at conveying this information to the end user at a glance.
Then you should have had that in the specification. I have used
APRSDos. I have found it less than user-friendly and I have found the
display, at times, confusing. I also have found the documentation
lacking in clarity. I have used WinAPRS, APRS+SA, APRSPoint, javAPRS,
and UI-View. Each has their deficiencies as well as their benefits. No
program is perfect but claiming that other authors are deficient because
they didn't implement something in APRSDos is pretty pretentious, IMO.
>I'm sorry, but the tone of your condescending emails upsets me.
I'm sorry if you are upset, Bob, but I was not condescending. I was
merely stating a fact. You can blame TAPR; you can blame the other
authors; but you are not blameless in this either. Nothing prevented
you from putting a generic recommendation in the spec about
differentiating station types in the map display (this did not have to
be tied to the way APRSDos did it). Nothing prevented you from agreeing
with the other people in the WG on what the standard symbol set should
look like (this has nothing to do with how they are drawn, it has
everything to do with how they appear on a map).
And, regarding being condescending, you might reread your post to me and
see if the tone of your email was condescending. I found it so and I
found the CAPITALIZATION emphasized your defensiveness.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Re: ARRL Public Service Manual regarding RACES
From: "Ronald Reams" <wa4mjf@worldnet.att.net>
Date: Mon, 27 Jan 2003 09:35:21 -0500
X-Message-Number: 12
I dare say that most APRS stations and digis are not regestered with their
county CD (EM) manager. This would mean they would go off of the air in the
event of such a declaration. Also, they could not operate when RACES is
called out for a more local opertion.
I know that is the situation in Raleigh NC area.
BTW, RF GATE WA4MJF and APRSDAT WA4MJF-1 are registered with the Wake
County EM.
73 de Ronnie
OES Area 7 NC ARES/RACES
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "Pat Karp" <pkarp@conwaycorp.net>
Date: Mon, 27 Jan 2003 08:36:07 -0600
X-Message-Number: 13
Bob Wrote:
>And a LOT of these are NOT in the spec, becuase the TAPR guidelines for
>the SPEC held that nothing could go into the SPEC if it was only in
>APRSdos (the original APRS)... and not yet implemented by the other
>authors at the time.
My anger on this subject is not aimed at you Bob but at the situation.
Too me this is the biggest mistake: The SPEC should entail every aspect of
APRS so that programmers have a guideline to built there apps from. Not to
Look at what's available at the time and limit the Spec's to common
components. The Spec's should be a COMPLETE source of information so that
programmers can create program to fully encompass what the original concept
of APRS was to be. I can not tell you how many times programmers have said
that they did not put feature in there program because it was not in the
Spec's.
There are several new programmers today that have no way of knowing what
your original concept was. The only thing they has is the Spec's. To me
this should be seriously look at and a new set of Spec's written. APRS has
been around long enough to determine if one concept of your was not needed
or needed to be improved. What you have said Bob (To my understanding) is
that Only APRSdos is a complete APRS app. And if you wish to write a
complete APRS app you need to copy APRSdos because there is no other
complete source of intended feature.
Most programmers started selling there versions long before they met the
Spec's. Most still have not implemented all of the aspects of the Spec's
to date. Either they have no intention of adding features (There Choice) Or
they have not gotten to it yet. How ever I believe all of them look at the
Spec's as a complete guideline as to what an APRS app is to be.
I keep reading the quote above and think of what a shame it is that APRS has
been limited in this way. If someone new to APRS where to ask which program
was a complete APRS app? Only DosAPRS would stand up to your criteria and
no other version would ever be able to compete. However most of the APRS
apps come really close to meeting the Spec's and more than likly can be use
as the answer to the question above. For the sad reason that the Spec's are
not complete!
Pat
----------------------------------------------------------------------
Read previous mail | Read next mail
| |