[aprssig] Some obscure APRS client questions
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toMon Nov 14 13:57:55 UTC 2011
- Previous message: [aprssig] Some obscure APRS client questions
- Next message: [aprssig] Some obscure APRS client questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
IMHO, the "spec" should be about shared interoperability based on the protocol and the transport. Static data like displays and/or file formats may be "recommendations" or "oh-by-the-way", but not SPECs. Objects can be shared over APRS and are therefore specs. Overlays are for local display and, IMHO, are not specs. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 11/14/2011 8:44 AM, Bob Bruninga wrote: >> The .POS files came from Bob's original APRSDOS which was before UI-View. >> Like Patrick said "based on software which is dead". >> I load them for backward compatibility, but have no >> plans for maintaining nor extending them from within APRSISCE/32. > ] > Actually every APRS program eventually used them. APRSdos, MacAPRS, > WinAPRS, APRS+, UIview, etc... It was part of the standard. Is this > something else that did not get into the spec? If so, Ill correct it. > > Thanks > Bob > > > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig >
- Previous message: [aprssig] Some obscure APRS client questions
- Next message: [aprssig] Some obscure APRS client questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
