Re: [wsjt-devel] 1.6.1 transmit start time
This is a small patch to restore the 25 second cutoff for transmit on JT65
and JT9.
Looks to me like the change that broke this was simply intended as a
temporary thing to let WSPR work with its desired behavior.
Should other modes have limits too?
@@ -1896,7 +1899,9 @@
}
float fTR=float((nsec%m_TRperiod))/m_TRperiod;
-//if(g_iptt==0 and ((m_bTxTime and fTR0.4) or m_tune )) {
+float fTRthreshold = 99;
+if (m_modeTx==JT65 || m_modeTx==JT9)
+ fTRthreshold = 0.4; // don't let transmit past 40% (~25 secs) into tx
period
if(g_iptt==0 and ((m_bTxTime and fTRfTRthreshold) or m_tune )) {
//### allow late starts ###
icw[0]=m_ncw;
g_iptt = 1;
73
Mike W9MDB
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X Development Status
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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSPR frequencies in WSJT-X 1.6.1
On 27/05/2015 14:31, Jay Hainline wrote: Hi Jay, Maybe I missed it in all the discussion, but is there a way yet to store both JT65/JT9 and WSPR frequencies in WSJT-X? Currently using WSJT-X v1.6.1-devel r5418. I have an enhancement that I am working on right now that allows much better handling of the working frequencies. As we have now merged Joe's work on integrating WSPR into the main development branch I will get that part sorted out. The changes will by default switch between the JT65 and JT9 frequencies for a band as you change between those modes. 73 Jay Jay Hainline KA9CFD Colchester, IL EN40om 73 Bill G4WJS. -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] 1.6.1 transmit start time
Tried using WSJT-X 1.6.1 devel for WSPR2 on 630M last night... clicking Enable TX shot off one TX cycle but the program never transmitted again afterward. Tx Pct was 20%. 73 Eric NO3M -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] f0 warning
Small patch to clear up warning on f0 not being initialized. Seems 0 is the
desired default.
@@ -4306,7 +4312,7 @@
if(isun==2) s=m_sunsetBands;
if(isun==3) s=m_nightBands;
- Frequency f0;
+ Frequency f0=0;
iband=-1;
for(i=0; is.length(); i++) { //See if designated band is
active
if(s.at(i)==bandName[iband0]) {
73
Mike W9MDB
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSPR frequencies in WSJT-X 1.6.1
Hi Jay and all, From messages on this list dated May 21: 1. I am not seeing the WSPR frequencies in the Frequencies tab or in the Dropdown menu on the GUI. Do I need to enter these manually somewhere? ... Currently the best way to reset the frequency list to the defaults, which now include the WSPR working frequencies, is to delete the Frequencies line from the .INI file. The .INI file is: %LOCALAPPDATA%\WSJT-X\WSJT-X.ini Alternatively, you can delete the whole .ini file and re-enter your setup parameters. -- 73, Joe, K1JT On 5/27/2015 9:31 AM, Jay Hainline wrote: Maybe I missed it in all the discussion, but is there a way yet to store both JT65/JT9 and WSPR frequencies in WSJT-X? Currently using WSJT-X v1.6.1-devel r5418. 73 Jay Jay Hainline KA9CFD Colchester, IL EN40om -- ___ 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
Re: [wsjt-devel] EMail test
Hi Mike, I do not know the reason, but I do not see / rcv my posted emails back in my Gmail inbox from any Sourceforge lists. Mailman lists seem OK, so I think this is something specific with the way Sourceforge has implemented their mailing lists. 73's Greg, KI7MT On 05/27/2015 10:48 AM, Michael Black wrote: I'm not seeing my own email from gmail. I see my email on the archive OK. I was having this same problem with yahoo and now see it again on gmail. So I don't know who is getting my emails on this list. Joe had said he wasn't seeing them. I put a delivery receipt on this one to see what is says. Is there any reason I shouldn't see my own emails from sourceforge lists? 73 Mike W9MDB -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Launchpad: https://launchpad.net/~ki7mt Ubuntu Hams..: https://launchpad.net/~ubuntu-hams-devel Debian Hams..: https://alioth.debian.org/projects/pkg-hamradio/ JTSDK: https://sourceforge.net/projects/jtsdk/ OpenPGP..: C177 6630 7115 78FE 9A2B 9F7F 18C0 F6B7 0DA2 F991 -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] EMail test
I'm not seeing my own email from gmail. I see my email on the archive OK. I was having this same problem with yahoo and now see it again on gmail. So I don't know who is getting my emails on this list. Joe had said he wasn't seeing them. I put a delivery receipt on this one to see what is says. Is there any reason I shouldn't see my own emails from sourceforge lists? 73 Mike W9MDB -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] v1.6.0-devel Cmakelist.txt Feature Request
Hi Bill, All, With the new 1.6.0-devel version capable of building documentation, when time allows, could you please add a result message message for finding AsciiDoc, similar to what is displayed when Python = 2.4 = 3.0, FFTW, etc etc? I'm not familiar enough with CMake find functions to propose a patch. Maybe it's time to learn ey' :-) 73's Greg, KI7MT -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSPR2 TX problem
Ran a test now with WSJT-X.ini removed prior to invoking the program still not transmitting after 4 RX cycles and TX Pct = 50% Configuration should be rather standard. Only set the callsign and grid, rest is default per having removed WSJT-X.ini: Call: WG2XJM (Part 5 exp call) Grid: EN91 Band: 630M Mode: WSPR-2 Tx Pct = 50% (even 100% was not triggering TX) Enable TX = true (GUI button highlighted Red) Tx = 1500 Hz Band Hopping = false Program info: Relative URL: ^/branches/wsjtx Revision: 5427 Still running and the Status indicates Receiving -278 now. Eric NO3M On 05/27/2015 05:15 PM, Joe Taylor wrote: Hi Eric, I have not answered your queries about failure to transmit in WSPR mode because so far I have not been able to reproduce the problem. As reported here a number of times, I (and a number of others) have been happily WSPRing with WSJT-X v1.6 for about two weeks. I've observed no reluctance of the program to transmit. Can you provide details on exactly what you are doing, and how you are configured? -- Joe, K1JT -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X Development Status
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 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
Re: [wsjt-devel] v1.6.0-devel Cmakelist.txt Feature Request
On 27/05/2015 22:18, KI7MT wrote: Hi Bill, All, Hi Greg, With the new 1.6.0-devel version capable of building documentation, when time allows, could you please add a result message message for finding AsciiDoc, similar to what is displayed when Python = 2.4 = 3.0, FFTW, etc etc? That's probably not simple. Asciidoc is found using the CMake find_program() command rather than using a package finder. This is normal for a tool, package finders are normally used to locate libraries and frameworks where multiple pieces of information are discovered. Currently the doc/CMakeLists.txt fails with a fatal error message if an asciidoc executable cannot be located. What are you looking for over and above that? I'm not familiar enough with CMake find functions to propose a patch. Maybe it's time to learn ey' :-) 73's Greg, KI7MT 73 Bill G4WJS. -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X User Guide for v1.5
I should have mentioned that a pre-built copy of the WSJT-X User Guide for version 1.5 has been posted at http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.5.html Note: this is NOT the version that will come up if you select Online User Guide from the v1.5 Help menu. To make this work properly we need to change the v1.5 source code to point to the above URL ... (or else rename the file to wsjtx-main.html, but then users of v1.4 would pull up the v1.5 manual from their Help menu). -- Joe On 5/27/2015 4:17 PM, Joe Taylor wrote: Hi all, With SVN revision 5427 I have committed files to build the WSJT-X User Guide for Version 1.5. I would greatly appreciate a careful reading by others! Please report mistakes, typos, unclear text, or any other need for improvements to this list. After final approval, this User Guide will be packaged with v1.5.0-rc2 -- and probably soon afterward with the GA release of WSJT-X Version 1.5. These files will also form a starting point for the v1.6 User Guide. New sections will need to be written for JT4 and WSPR modes and for VHF-and-up use of JT65. -- 73, Joe, K1JT -- ___ 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
Re: [wsjt-devel] WSJT-X User Guide for v1.5
Hi Greg,
thank for explanation.
In addition I have also some duplicates:
Directory di C:\JTSDK\wsjtx\install\Release\bin\doc
28/05/2015 00:30 1.215.014 wsjtx-main-1.6.0-devel.html
28/04/2015 20:12 1.204.470 wsjtx-main.html
As Joe and Bill will update repository, tomorrow I cleanup my local
destinations.
73
Sandro
IW3RAB
Il 28/05/2015 00:29, KI7MT ha scritto:
Hi Sandro,
The source locations for v1.6.0-devel and those stored
^branches/doc/wsjtx are different from what is being built with the
CMakelists.txt files which reside in ^branches/wsjtx/doc/user_guide
Originally, building the docs was a trial run in the CMake method of
build. Both JTSDK Win and Linux are still building from
^branches/doc/app-name to facilitate the migration, as we are not
setup to build all the documents from within applications themselves.
When Joe and Bill have an in application build method established, we
will not longer need to a separate the application build from the
documentation build. It will simply be a Target within the application
being built. At which point, they could do a final merge and declare the
^branches/doc/app-name dormant.
73's
Greg, KI7MT
On 5/27/2015 3:58 PM, Alessandro Gorobey wrote:
Hi Joe,
I have to advise that some file seem missed in svn.
In Windows JTSDK obtain:
Sandro@Sandro-HP~/doc$ build-dall
Building All WSJT Documentation
.. building data-uri version for ( map65 )
.. building data-uri version for ( simjt )
.. building data-uri version for ( wsjt )
.. building data-uri version for ( wsjtx )
sh: /home/Sandro/doc/wsjtx/source/images/jtalert.png: No such file or
directory
asciidoc: WARNING: cooperating-programs.adoc: line 26:
{sys:/usr/bin/python -u -c import mimetypes,base64,sys; print
'src=\x22data:'+mimetypes.guess_type(r'images/jtalert.png')[0]+';base64,';
base64.encode(sys.stdin,sys.stdout)
/home/Sandro/doc/wsjtx/source/images/jtalert.png}: non-zero exit status
asciidoc: WARNING: faq.adoc: line 1: missing style: [paradef-default]: qanda
.. building data-uri version for ( wspr )
.. building data-uri version for ( wsprx )
.. building data-uri version for ( wfmt )
.. building data-uri version for ( quick-ref )
.. building data-uri version for ( dev-guide )
Finished Building All Documentation
Sandro@Sandro-HP~/doc$
---
Some message also in Linux with JTSDK 2.0.2
C:\JTSDK\cyg32\home\Sandro\doc\wsjtx\source\faq.adoc first line:
[qanda]
/home/Sandro/doc/wsjtx/source/images/jtalert.png file is missing
Section 3 install wsjtx-1.4.0 -- 1.X.X
Section 11 Platform Dependencies
advise users that also some temp files is created
73
Sandro
IW3RAB
Il 27/05/2015 22:17, Joe Taylor ha scritto:
Hi all,
With SVN revision 5427 I have committed files to build the WSJT-X User
Guide for Version 1.5. I would greatly appreciate a careful reading by
others! Please report mistakes, typos, unclear text, or any other need
for improvements to this list.
After final approval, this User Guide will be packaged with v1.5.0-rc2
-- and probably soon afterward with the GA release of WSJT-X Version 1.5.
These files will also form a starting point for the v1.6 User Guide.
New sections will need to be written for JT4 and WSPR modes and for
VHF-and-up use of JT65.
-- 73, Joe, K1JT
--
___
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
--
___
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
Re: [wsjt-devel] WSPR2 TX problem
Enabling band hopping gets Tx rolling, but as someone pointed out in another message to the list, even with a low percentage Tx probability (in my case 20% tested), up to 4 consecutive Tx cycles before I killed it. On 05/27/2015 08:20 PM, Joe Taylor wrote: Hi Eric, It seems that my implementation of band-hopping has caused a side effect of improper behavior when band-hopping is NOT selected. As a temporary work-around, please try checking the Band Hopping box. On Tab 4, you enter 630 (your one desired band) alone in the Sunrise, Day, Sunset, and Night fields. -- 73, Joe, K1JT -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSPR2 TX problem
As stated before, so far there has been no effort to prevent any specific number of consecutive transmissions. The T/R randomization algorithm now in the code may be considered a placeholder. BTW: I was copying you well, before you quit. -- Joe, K1JT On 5/27/2015 9:06 PM, Eric NO3M wrote: Enabling band hopping gets Tx rolling, but as someone pointed out in another message to the list, even with a low percentage Tx probability (in my case 20% tested), up to 4 consecutive Tx cycles before I killed it. On 05/27/2015 08:20 PM, Joe Taylor wrote: Hi Eric, It seems that my implementation of band-hopping has caused a side effect of improper behavior when band-hopping is NOT selected. As a temporary work-around, please try checking the Band Hopping box. On Tab 4, you enter 630 (your one desired band) alone in the Sunrise, Day, Sunset, and Night fields. -- 73, Joe, K1JT -- ___ 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
Re: [wsjt-devel] WSJT-X User Guide for v1.5
Hi All, the WSJT-X user guide has been migrated to the WSJT-X build. For the moment it is only in the development branch, I will merge it back to the v1.5 branch once we are happy it is suitable for release with the upcoming v1.5 RC2 and GA. There is an issue with the QA labelled list section which I don't yet understand, it is causing an asciidoc warning and not formatting the QA list correctly. If you are reading this Greg, perhaps you know what is happening there? All user guide changes should now be committed to the ^/branches/wsjtx branch and for now they should be restricted to changes that are destined for the v1.5 release. The source files are in ^/branches/wsjtx/doc/user_guide with common files in ^/branches/wsjtx/doc/common and images in ^/branches/wsjtx/doc/user_guide/images . If a source file is added, deleted or. renamed you will need to amend the file list in the CMake script ^/branches/wsjtx/doc/CMakeLists.txt . Once the user guide has been merged into the v1.5 branch work can start on the user guide for the v1.6 release. 73 Bill G4WJS. On 5/27/2015 8:59 PM, Bill Somerville wrote: On 28/05/2015 00:18, Joe Taylor wrote: Hi Bill, Hi Joe, On 5/27/2015 7:03 PM, Bill Somerville wrote: Can I assume that the WSJT-X user guide documentation sources in ^/branches/doc are stable for a few hours so I can migrate them across to the WSJT-X tree(s)? Yes, by all means. I will commit nothing further for 12 hours. Looks like the file images/jtalert.png is missing, can you send it to me directly please. -- Joe 73 Bill G4WJS. -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X User Guide for v1.5
Hi Sandro,
The source locations for v1.6.0-devel and those stored
^branches/doc/wsjtx are different from what is being built with the
CMakelists.txt files which reside in ^branches/wsjtx/doc/user_guide
Originally, building the docs was a trial run in the CMake method of
build. Both JTSDK Win and Linux are still building from
^branches/doc/app-name to facilitate the migration, as we are not
setup to build all the documents from within applications themselves.
When Joe and Bill have an in application build method established, we
will not longer need to a separate the application build from the
documentation build. It will simply be a Target within the application
being built. At which point, they could do a final merge and declare the
^branches/doc/app-name dormant.
73's
Greg, KI7MT
On 5/27/2015 3:58 PM, Alessandro Gorobey wrote:
Hi Joe,
I have to advise that some file seem missed in svn.
In Windows JTSDK obtain:
Sandro@Sandro-HP~/doc$ build-dall
Building All WSJT Documentation
.. building data-uri version for ( map65 )
.. building data-uri version for ( simjt )
.. building data-uri version for ( wsjt )
.. building data-uri version for ( wsjtx )
sh: /home/Sandro/doc/wsjtx/source/images/jtalert.png: No such file or
directory
asciidoc: WARNING: cooperating-programs.adoc: line 26:
{sys:/usr/bin/python -u -c import mimetypes,base64,sys; print
'src=\x22data:'+mimetypes.guess_type(r'images/jtalert.png')[0]+';base64,';
base64.encode(sys.stdin,sys.stdout)
/home/Sandro/doc/wsjtx/source/images/jtalert.png}: non-zero exit status
asciidoc: WARNING: faq.adoc: line 1: missing style: [paradef-default]: qanda
.. building data-uri version for ( wspr )
.. building data-uri version for ( wsprx )
.. building data-uri version for ( wfmt )
.. building data-uri version for ( quick-ref )
.. building data-uri version for ( dev-guide )
Finished Building All Documentation
Sandro@Sandro-HP~/doc$
---
Some message also in Linux with JTSDK 2.0.2
C:\JTSDK\cyg32\home\Sandro\doc\wsjtx\source\faq.adoc first line:
[qanda]
/home/Sandro/doc/wsjtx/source/images/jtalert.png file is missing
Section 3 install wsjtx-1.4.0 -- 1.X.X
Section 11 Platform Dependencies
advise users that also some temp files is created
73
Sandro
IW3RAB
Il 27/05/2015 22:17, Joe Taylor ha scritto:
Hi all,
With SVN revision 5427 I have committed files to build the WSJT-X User
Guide for Version 1.5. I would greatly appreciate a careful reading by
others! Please report mistakes, typos, unclear text, or any other need
for improvements to this list.
After final approval, this User Guide will be packaged with v1.5.0-rc2
-- and probably soon afterward with the GA release of WSJT-X Version 1.5.
These files will also form a starting point for the v1.6 User Guide.
New sections will need to be written for JT4 and WSPR modes and for
VHF-and-up use of JT65.
-- 73, Joe, K1JT
--
___
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
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] v1.6.0-devel Cmakelist.txt Feature Request
On 27/05/2015 22:50, KI7MT wrote: Hi Bill, Hi Greg, Currently, we have the path to AsciiDoc Python2 in the tool-chain file, which I think that is where it is supposed to go. The paths to Python2 and AsciiDoc are not in the JTSDK-QT ENV or Build script %PATH% to prevent potential collisions with Python3 native or JTSDK installations. That's correct. Currently the doc/CMakeLists.txt fails with a fatal error message if an asciidoc executable cannot be located. What are you looking for over and above that? That was what I was hoping to prevent, the fatal error, rather, simply display the message that it wasn't found, and continue to build the app, or if it was found, things are OK and display the found message. If the doc portion of the build is deemed critical, then I suppose it's OK as is. The way I look at it is that the build script in its default form is supposed to build the final product in its entirety. For things that are deemed optional for developers there are CMake options that can be set to change the way they are built or not built. In this case the WSJT_GENERATE_DOCS option applies and builders have the option to turn it off. I will change the fatal error message to make it clearer that the docs build is optional and how to turn it off. 73 Bill G4WJS. -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] v1.6.0-devel Cmakelist.txt Feature Request
Hi Bill, On 5/27/2015 3:59 PM, Bill Somerville wrote: On 27/05/2015 22:50, KI7MT wrote: Hi Bill, Hi Greg, Currently, we have the path to AsciiDoc Python2 in the tool-chain file, which I think that is where it is supposed to go. The paths to Python2 and AsciiDoc are not in the JTSDK-QT ENV or Build script %PATH% to prevent potential collisions with Python3 native or JTSDK installations. That's correct. Currently the doc/CMakeLists.txt fails with a fatal error message if an asciidoc executable cannot be located. What are you looking for over and above that? That was what I was hoping to prevent, the fatal error, rather, simply display the message that it wasn't found, and continue to build the app, or if it was found, things are OK and display the found message. If the doc portion of the build is deemed critical, then I suppose it's OK as is. The way I look at it is that the build script in its default form is supposed to build the final product in its entirety. For things that are deemed optional for developers there are CMake options that can be set to change the way they are built or not built. In this case the WSJT_GENERATE_DOCS option applies and builders have the option to turn it off. I will change the fatal error message to make it clearer that the docs build is optional and how to turn it off. Ok, thank you. With you all moving the apps over to QT rather, that dramatically simplifies things for the Windows SDK. There are a few other itmes that I wanted to ask you about regarding the Tool Chain file but I can do that closer to the time when JTSDK v2.1 is being put together. 73 Bill G4WJS. 73's Greg, KI7MT -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
