Hi Bill, I hope you refer only the server side of message_aggregator see below
Il 27/05/2015 20:40, Bill Somerville ha scritto: > On 27/05/2015 19:24, Alessandro Gorobey wrote: >> Hi Bill, > Hi Sandro, >> >> I perfectly understand the status. >> >> But I hope that some very good software will no be lost. >> >> Eg jt9sim.exe is compiled but not installed. >> Eg All the FMT suite present in WSPR that using PY only for marginal >> operations and use some library of WSJTX > The tool jt9sim is intended as a developer tool rather than an end user > tool. > > 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 >> >> why not maintain these as installed programs as your exceptional >> message_aggregator (and I hope also the new frequency list) outside the >> program ? > Hardly exceptional Sandro, it is just a reference implementation > demonstrating the UDP message broadcasts from WSJT-X. It has no real > purpose other than as an example to developers of cooperating > applications. My intention was to not ship message_aggregator when it > comes to the first GA of v1.5 as by that time there should be > applications using the new protocol like JTAlertX. 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"? I personally think it is a shame remove a so nice feature. >> >> The main program is WSJTX, but who want use the additional programs can > Well that is try for anyone who builds from sources as the additional > developer tools are all built by the CMake build script. We already > choose to package jt9code, jt4code and, jt65code as they are useful > tools for end users that are referenced in the user guide. >> ...... >> >> 73's >> Sandro >> IW3RAB > 73 > Bill > G4WJS. 73 Sandro IW3RAb >> >> >> >> Il 27/05/2015 18:26, Bill Somerville ha scritto: >>> Hi All, >>> >>> further to Joe's comments below, we have now reintegrated his WSPR mode >>> work in the wsjtx_exp branch into the main WSJT-X development branch. >>> Currently wsjtx_exp is dormant and the latest and greatest WSJT-X is to >>> be found on the main development branch ^/branches/wsjtx . >>> >>> The main development branch (a.k.a. the trunk) still builds as v1.6.0-devel. >>> >>> Until further notice only the WSJT-X branches ^/branches/wsjtx-1.5 and >>> ^/branches/wsjtx are active and should have any changes submitted. >>> >>> 73 >>> Bill >>> G4WJS. >>> >>> On 22/05/2015 17:45, Joe Taylor wrote: >>>> Hi all, >>>> >>>> I believe WSJT-X v1.6.1 now works well in all of its supported modes: >>>> JT9, JT65(A-C), JT4(A-G), and WSPR-2. Surely there is more work to be >>>> done: to name just a few items on my To Do list, WSPR-15 should be >>>> implemented, message averaging should be added to JT65, and a higher >>>> accuracy EME Doppler calculation should replace the present one, which >>>> may have errors as large as 20 Hz at 10 GHz. Probably also some cleanup >>>> and/or refactoring of source code, some "beauty-treatments" on the GUI >>>> here and there, etc. >>>> >>>> I think these things can reasonably be done in our normal development >>>> branch, so I'd like to suggest it's time to merge my "features branch", >>>> aka .../branches/wsjtx_exp, aka v1.6.1, back into the main development >>>> branch, .../branches/wsjtx. >>>> >>>> Is everyone OK with this plan? Among other advantages, it will mean >>>> that our current SVN branches .../wsjt_exp, .../wspr, and .../wsprx will >>>> become inactive. This will result in a considerable simplification in >>>> the way we manage our source code and will minimize the required number >>>> of cross-branch merges. >>>> >>>> -- Joe, K1JT > > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
