+ AA6YQ comments below
Seriously, I do think Ham Radio software does need to adopt some modern
architecture principles. In this context the WSJT-X team
should be focused on weak-signal communication protocol processing. Issues such
as logging should be left to others to focus on, and
there should be a well defined complete API for applications to interface to
them.
+ Modern architectural principles would encourage a modular structure with
weak-signal communications loosely coupled to logging.
Having one development team implement both functions does not violate modern
architectural principles.
Absent the Ham Radio logging community coming up with such an API, some
application should emerge to bridge the gap, with a well
defined API. JTAlert comes very, very, close to this.
+ WSJT-X enables an application to receive a well-defined UDP message from
WSJT-X that conveys a QSO Record defined by the ADIF
specification. Other than debating the choice of UDP vs TCP what more do you
want, exactly?
73,
Dave, AA6YQ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
