Hi Bill and all,

I'm copying this answer to the wsjt-devel list, so that everyone can 
know what's going on -- and can chime in, if they have pertinent ideas.

> Chase W4TI is getting stuck into updating the WSJT-X docs for the latest
> enhancements. Because of this and his need to generate new graphics for
> the manual I think we need to do something with the visible JT9W parts.
> I would like to make them optional with a CMake option but I'm not sure
> I can do that easily with the parts in the UI modules that are written
> with Qt Designer. I could insert code to call "hide" on the UI
> components if the option is not "ON" at build time, which may be enough.

Yes, hiding the visible JT9W parts would be OK.  Or perhaps better, 
"graying them out".  I don't see any particular downside to having some 
visible indications of features that are still to come.  It lets people 
know something about our plans.

> What is you intention with JT9W, are we going to make WSJT-X suitable
> for all bands or is it just being used as a test bed for the mode? If it
> is the former, the configuration changes I've made should be Ok for all
> recognised amateur bands up to 1mm including transverter support.

My original plan was to move the other WSJT modes (FSK441, JTMS, 
ISCAT-[AB], JT6M, JT65[BC], JT4[A-G]) into WSJT-X.  This would be a big 
job, and probably rather disruptive.

One possibility would be to recognize some clear distinctions between 
"Fast Modes" (JTMS, FSK441, ISCAT, and JT6M) and "Slow Modes" (JT65, 
JT4, and JT9).  Modes within each group share many characteristics, 
including length of T/R period and assumed signal type (e.g., 
meteor/ionospheric scatter, or roughly constant SNR).  Of course, each 
mode uses its own particular scheme for coding and modulation.

One might then move only slow modes into WSJT-X, or at least move them 
first.  I think this probably makes sense.

JT9W is probably the smallest perturbation of all, so it makes sense to 
do that one first.  I've been reluctant to start any of this development 
until after we release an existing WSJT-X -- first as a beta, for more 
thorough field testing, and then as a full release with an up-to-date 
manual.  Then we can tag that release and I can start on the "mode 
additions", perhaps in a new SVN branch.

        -- Joe, K1JT

HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
wsjt-devel mailing list

Reply via email to