On 27/05/2015 22:02, Michael Black wrote: Hi Mike,
> I know JTAlert is working on it. What are the other two? https://sourceforge.net/p/wsjt/mailman/message/33817990/ Anders was progressing well with this AFAIK. A Mac application using Swift as the application language. Also Saku OH1KH is working on something implemented in Free Pascal which is a multi platform variant of Object Pascal like Delphi. > > 73 > Mike W9MDB 73 Bill G4WJS. > > -----Original Message----- > From: Bill Somerville [mailto:[email protected]] > Sent: Wednesday, May 27, 2015 3:57 PM > To: [email protected] > Subject: Re: [wsjt-devel] WSJT-X Development Status > > On 27/05/2015 21:43, Alessandro Gorobey wrote: >> Hi Bill, > Hi Sandro, >> I hope you refer only the server side of message_aggregator see below > Oh yes. The client code in WSJT-X is definitely staying in. At least three > applications that I know of are already using it ready for when > v1.5 goes to GA. Also the server side code will be maintained as the client > side gets amended or enhanced with new messages. > > ... >>> ... >>> The FMT suite is published software so I expect it will remain so. I >>> believe they are simple Fortran programs that can be easily migrated >>> to the WSJT-X build script and installed as part of the WSJT-X package. >> Also manual is ready: >> file:///C:/JTSDK/cyg32/home/%username%/doc/wfmt/wfmt-main.html >> search fmt replace fmtest > OK, that sounds like another candidate for migration to the WSJT-X build. >> The UDP message broadcast/multicast from WSJT-x seems do not impact in >> any way the program performance. >> A piece of code write in C# work well with UDP and open a lot of chance. >> It is possible to maintain the code in main program, or through a >> switch as used by "Enable PSK reporter" --> "Enable UDP Server"? > See above, the UDP messages from and back to WSJT-X are staying in. > > As for the performance, nothing is free but the overhead compared to writing > to the file system will be very small. I think the main overhead in the > current file based protocol is contention for access to the status files > that blocks both the reader and the writer, this effect is very apparent > with JTAlertX which gets into a fight with WSJT-X over access to the > wsjtx_status.txt file. The UDP client code cannot block and the back channel > for replies is handled asynchronously so there are no blocks to the GUI > thread there either. > > ... > > 73 > Bill > G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
