Hi Simon,
comments in line below.
On 06/12/2018 17:40, Simon wrote:
Thanks for pointing out the MessageAggregator demo code. We looked at
Decodesmodel.cpp and our one simple line of needed data is as below:
1. May be easier to use QT, instead of Microsoft and needing to port a
lot of 'QT things which I never used before' to Microsoft environment.
the message_aggregator reference application has similar dependencies as
the udp_daemon. They are both Qt applications that talk the WSJT-X
protocol, they both use the MessageServer class from the wsjt_udp
library. The major difference is that, because message_aggregator is a
desktop GUI application, it is far more complex and it depends on much
more of the Qt framework (the GUI and Wdgets components). The udp_daemon
is a command line tool and only depends on the base and networking Qt
components.
As I see it you have C experience in embedded environments, little or no
C++ experience, maybe some networking experience with Internet
protocols, and no Qt C++ framework experience (which in turn requires
C++ knowledge). You must choose your implementation strategy such that
your learning curve is only extended in areas that you want to improve
your capabilities. So if you are interested in C++, GUI applications,
cross platform independence you might go down the C++ and Qt route. If
you want to remain in the MS proprietary domain then choose an MS
toolchain and implement with appropriate facilities, that could be C
with winsock, C++ with some third party networking library (or winsock
if you are happy with the C API), or .Net in any language that supports
it. Another alternative could be to choose a non MS toolchain that has
suitable networking libraries like Delphi (object-pascal or the similar
Lazarus, also object-pascal, with the Indy components library), or Java.
If you are not unhappy with learning some C++ and some of the Qt
framework, by installing the JT-SDK you will get a leg up as you do not
need to become proficient with the tools for this requirement as you
have a starting point of the WSJT-X UDP message protocol reference
applications. Other paths will require more work to get to the same
point but OTOH a simple C+winsock application may be less work overall
and the new bits like network sockets programming and data handling can
be completed with a familiar programming language and environment.
Only you can decide what is the best route for you.
2. Which version of QT? Where to get it?
The JT-SDK deal with this but I did answer this question in a previous
message to you.
3. The MessageAggregator is an independent program, right? There is no
concern for huge dependencies and needing to get all library, etc. if
I were to compile the WHOLE WSJT-X.
Just like the udp_daemon reference application, the easiest way to build
it is to build the WSJT-X application suite. It can be built separately
but you will still need Qt and an appropriate C++ compiler. We do not
provide a recipe to build these reference applications with other tools
as it would be duplication of almost all of the set up to build WSJT-X
itself.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
