| |
ZL3AI > APRDIG 03.02.03 14:30l 203 Lines 9156 Bytes #999 (0) @ WW
BID : 804-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jan 27, 9/10
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<RZ6HXA<IK1ZNW<IK6PYS<W4JAX<VK4TUB<
ZL2BAU<ZL3VML
Sent: 030131/0938Z @:ZL3VML.#80.NZL.OC #:58521 [Chch-NZ] FBB7.00i $:804-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 27 Jan 2003 19:57:20 -0500 (EST)
X-Message-Number: 55
On Mon, 27 Jan 2003, AE5PL Lists wrote:
>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.
How can you make such an assertion? I didnt notice you at any of
those meetings or emails... Yes, I did everything I could to convey
what was missing from the SPEC as it was evloving and also I have
stated it over and over again here on the APRSSIG.... but I also
fully recognized that everyone is swamped and have tons of
issues besides these to worry about in their coding. So I just keep
mentioning these issues so they dont get forgotten...
>>>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 with zoom
>
>Bob, I wasn't referencing size. I was referencing all programs using
>the same symbol for the same thing.
Yes, that is why there was the SYMBOLS.TXT file to tell everyone not only
what a symbol was but also what it looked like. I assumed that anyone
interested in writing an APRS look-alike program back then when APRSdos
was still at least 50% of the users, would at least run APRSdos once and
press F1-HELP-SYMBOLS to get a full screen view of all the Symbols
documented in SYMBOLS.TXT. Here is a link:
http://www.ew.usna.edu/~bruninga/aprs/symbols.html
Given the limitations of DOS, I would NEVER have suggested they use my
Symbols, just somthing that looked like them...
>... 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, but the APRS-WG took the stance that the SPEC could not specify
"how information was presented" which I was completely against. Not that
I wanted to tell others -how- to display things, but I wanted to insist
that certain "things" must be displayed to the end user so that ALL end
users no matter what the platform would get the "same" information.
I lost that argument, and that is why we are where we are today. We have
no consistency in what information is presented to a user looking at a map
display... So I think we are in violent agreement.
And to help, I have prepared my ERATTA page to describe what I think
should be conveyed with a symbol (icon). I applaud all the great things
that the authors do present and I love many of their innovations and the
additional data using modern graphical user interfaces. I am not
complaining about those at all. But I do think we need to make sure some
fundamentals are covered...
>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?
On this sig, over and over, every time it comes up... Where else can I
insist it?????
> 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.
I am not slamming anyone. Geeze. Im saying that just following the SPEC
does not give the full intent of APRS, and I am doing all I can to help
others understand some of the key issues that were missing...
>>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 ... disappointed that none of the
>>others.... display this SYMBOL TYPE variable on the map
>>for 'easy' assessment by people looking at these maps (without
>>having 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.
>...
>Then you should have had that in the specification.
Believe me I tried!!!!
>I have used APRSDos. I have found it less than user-friendly and I have
>found the display, at times, confusing.
Which is exaclty why I NEVER say do it my way, I simply say, "if a
program does not in some way convey this information to the end user,
then something is missing and should be fixed..."...
>I also have found the [APRSdos] documentation lacking in clarity.
Which is EXACTLY why we decieded to boil it all down in the APRS SPEC!
>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 NEVER SAID THAT AND THE SOONER YOU GET RID OF THAT MISSREPRESNTATION THE
SOONER we can make some progress! I NEVER say do it my way, I only say,
to the effect of "this is how I did such and such in APRSdos" I certainly
hope that others will use all of the much better tools available to them
to figure out BETTER ways to do it than what were available to me in 1992
in BASIC!
I can't believe your totally counerproductive assertions. On the one hand
you say that these problems are my fault becuase I didnt 'show what' was
required in the SPEC, and then when I use an example in APRSdos to SHOW
how I did it to help convey the idea, you condem such attempts as telling
people to do it my way.
>...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).
Ha! What can you possibly mean "nothing prevented"... Where were you?
The working group heard in no uncertain terms my diatribes against these
issues, and my dissatisfaction at the compromises that were required to
get consensus. So your use of the words "nothing prevented..." are just
crazy. What "prevented" me was the need to get consensus or there would
not have been any SPEC.
de WB4APR@amsat.org, Bob
----------------------------------------------------------------------
Subject: RE: APRS Symbols (versus Windows ICONS)..
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Mon, 27 Jan 2003 19:00:02 -0600
X-Message-Number: 56
>-----Original Message-----
>From: Bob Bruninga [mailto:bruninga@usna.edu]
>Posted At: Monday, January 27, 2003 5:47 PM
>Subject: [aprssig] RE: APRS Symbols (versus Windows ICONS)..
>
>I got sucked-into that less than adequate response.... by
>being defensive to the 'blame game' that AE5PL is playing
>with his inflamatory statememts:
I was going to let this drop, but you have made extremely rash and
baseless accusations about me and my character, much of which does not
bear repeating.
Bottom line: I did not "suck" you into anything. Your post to which I
originally responded stated:
>Thus, a whole layer of visual information was lost in most Windows
>versions of APRS that took the simplistic "Icon" approach to displaying
>APRS stations on their maps.
>So, lack of seeing what an "icon" is, is not the fault of "APRS", it
>is the fault of many implementations of "APRS".
It was your post that stated that "other" software was at fault and
therefore, you started what you now call the "blame" game. I neither
"blamed" you for the problems nor did I claim that you were solely at
fault for the problems discussed. I did point out that you might not be
without fault in this matter at which time you became highly defensive
and, IMO, unnecessarily abrasive and rude in your posts. I made no
personal attack on you or your software. I have not made any
inflammatory statements regarding you, your actions, or your software.
I ask that you cease and desist in your baseless and incessant attacks
on me and my character.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Read previous mail | Read next mail
| |