toggle quoted messageShow quoted text
I don't disagree John.
But the EmComm leaders have decided that forms save critical bandwidth over the air, and forms must be used.
Regrettably, forms are proprietary in Winlink, so EmComm leaders have locked us into Winlink Express, and Windows in one fell swoop.
On Thu, Oct 4, 2018 at 5:33 PM, John D Hays - K7VE <john@...>
I looked on the winlink site and the HTML and CSS for existing forms does not appear to be independently downloadable, nor do I see a quick link to the data only transport.
Open things up and maybe some development will follow.
On Thu, Oct 4, 2018, 17:08 Randy Neals <randy@...
For EmComm oriented clients, there are a few key functions necessary in client software:
-Forms ie: HTML/CSS Forms creation & content-only transport
-Tactical Address Support
Outpost, Pat, Paclink (but not Paclink-Unix) and Winmail Express support tactical addressing.
Only Winlink Express supports Forms.
I'd dearly love to see a client that supports Forms and Tactical addresses that would run on a Raspberry Pi, such as the new DRAWS station.
It has been my experience that nearly every time I fire up my ham radio ThinkPad, that it wants to download an update or do something other than the Winlink message I want to send.