Hello All, I started updating WSJT manpage and documentation builds, primarily for *Nix. The Windows User Guide Builds are OK via Makefile.jtsdk2. There is a fair amount of work yet to be done, both in terms of the docs themselves, and the autotool files (makefiles / configure scripts etc).
Aditionally, for those using the CALL3.TXT file, I've added an SQLite3 DB ( wsjt.db ) and fixed up a CSV file based on the CALL3.TXT file which resides in the ^/trunk. There were a number of malformed rows that needed to be fixed (extra commas and such), but I think I have it straightened out now. Using any number of the available Open Source SQLite3 DB managers, you can easily update the database from the CALL3.TXT file, or generate new CALL3.TXT from the DB if you wish. See example below. Eventually, when I get the add / update python functions finished, with very little change to the main wsjt.py script, WSJT should be able to interface directly with the DB for CALL3 additions and / or updates. The same is true for the QSO log. Currently, the Menu Item "Logbook" is set to display a simple message box stating it is under development. As things are added / tested properly, the functions can be enabled for wider audience testing. The following is a quick method of exporting the wsjt.db call3 table into CALL3.TXT file. Note, there are many ways to do this, this is just quick method to get things moving. *GENERATE CALL3.TXT* Using Windows JTSDK-Py as the example. You should not need to install any software for this: * Open JTSDK-Py * cd src\trunk * svn update * cd logbook\database * sqlite3 wsjt.db * .output CALL3.TXT * .separator "," * SELECT call, grid mode, previous_call, comment, last_update FROM call3; * .output stdout *.quit That should create a file called CALL3.TXT in the ^\database directory, which should be correct for WSJT use; if it is not, please let me know. Using the list function rather than .output csv prevents wrapping NULL fields with "-" double quotes. If your using an SQLite3 DB manager, all you do is Export the call3 table as a CSV file, ensuring you select comma delineated. Using the DB managers makes things "Much" easier for updates / imports / exports. If you have any trouble or find issues withe using the updated CALL3.TXT file, let me know and I'll take a closer look. 73's Greg, KI7MT ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
