Dave: On the first point, we more or less agree. A development team can focus on many things, true. The point Im trying to make here is that logging and weak-signal processing are two very different functions, and don't belong in the same application. If an exception is to be made here, yes, it should be loosely coupled.
More disagreement is found in the second point. Yes, a UDP message defined by the ADIF specification is an API. I do question if it's appropriate. What I want is for the Ham Radio software generally: Let's catch up to modern software practices, and perhaps even return to the position of innovating. At some point, we seem to have lost that. Perhaps Im wandering off the topic of the list. Im happy to continue the discussion in email or some other public forum if appropriate. Thanks. Robert. AD6I. On Mon, Jun 29, 2020, at 9:08 PM, Dave AA6YQ wrote: > + 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 > _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
