Re: TLF-1.4.0 release
Hi Nate, Am Sun, 17 Nov 2019 04:50:16 -0600 schrieb Nate Bargmann : > Congratulations to Tom and everyone that has worked on this release. > Thanks. > I've been quiet for the past year or so as I chose a different > challenge about a year ago due, in part, to the lament of some > friends. For the handful of events I operate these days I've chosen > to use N1MM+ under Wine. It does work though it is a bit (quite a > bit) quirky. > One feature I really like is to be able to switch from > ESM to a CT like mode on the fly. When I do S I much prefer the CT > mode and for running ESM works best for me. As far as I see now that could be done in TLF easily. If we switch the mode after finishing a QSO and before starting a new one, that should work flawlessly. All that is needed is a way to switch 'ctcompatible' on and off by key or command. Feel free to experiment on it and prepare a pull request if you like. > Another reason to work > with it was for our club Field Day operation where other ops seem > more comfortable with menus and such. Yes, there seems to be different 'operating modes' in our heads also - some prefer keyboards and other prefer mouse and menus. I fear that one can not be changed - every one has to choose the programs which fits their 'internal working' best :-). 73, de Tom DL1JBE -- "Do what is needful!" Ursula LeGuin: Earthsea -- pgp9x5d_A5BO1.pgp Description: Digitale Signatur von OpenPGP
Re: TLF-1.4.0 release
Hi all, Am Thu, 14 Nov 2019 20:22:24 +0100 schrieb Csahok Zoltan : > Thanks, Tom! > > Now it's time for feature requests and bug reports. :-) As the first feature request came in today by Joop let me start a little list with things to do. Please feel free to add your ideas to the list. We then sort out in which order and timeframe we can work on it: - Have a template for cabrillo file header (Joop PG4I) - Add a keyword to startup TLF in S mode (should be an easy one) - switch between ESM and CT mode during contest (Nate N0NB) - change internal QSO representation to structs (makes coding much simpler and will enable migration of log file to a different format later) - Switch the logfile to a database. The actual TR-Log format has some limitations. Log as a database will enable easy statistics, make removal of QSOs easier and allows us to store more information about the contest. (Long term goal) - Do a major rework of scoring of multis and points (That is already overdue for some time now). As contests developed in last years there are more and more complex scoring schemes. To code a special contest module for each contest will not be possible with our limited man power. So we need a flexible and programmable scoring which will allow us to handle most of the contests by a rule file. I fear it will break compatibility with existing TLF rules completely and would sure be a major version bump to TLF-2.0 or similar. Thats for a start. Any additions? 73, de Tom DL1JBE > > 73, > Zoli > > On Wed, Nov 13, 2019 at 03:06:33PM +0100, Thomas Beierlein wrote: > > > > After a lot of work by all people contributing to TLF I would like > > to announce the release of the new TLF-1.4.0 version. > > > > You can find it at > > > > http://download.savannah.gnu.org/releases/tlf/tlf-1.4.0.tar.gz or > > https://github.com/Tlf/tlf/releases/download/tlf-1.4.0/tlf-1.4.0.tar.gz > > -- "Do what is needful!" Ursula LeGuin: Earthsea --
Re: TLF-1.4.0 release
Hi Pontus, in the name of all who spent their time working on TLF let me thank for your kind words. We are glad that our work make contesting fun for all of you. 73, de Tom DL1JBE Am Fri, 15 Nov 2019 08:39:38 +0100 schrieb Pontus Falk : > Hi, > > Den 2019-11-13 kl. 15:06, skrev Thomas Beierlein: > > > After a lot of work by all people contributing to TLF I would like > > to announce the release of the new TLF-1.4.0 version. > > > > You can find it at > > > > http://download.savannah.gnu.org/releases/tlf/tlf-1.4.0.tar.gz or > > https://github.com/Tlf/tlf/releases/download/tlf-1.4.0/tlf-1.4.0.tar.gz > Thanks a zillion to all of you involved in the development. > > I've been using tlf for a couple of years, most recently in CQ WW SSB > 2019 and I'm so happy with 1.3.0 - and I see a lot of improvements > already by just starting 1.4.0. > > Thanks again! > > 73's de SM0RUX Pontus (SM0R in contests) > -- "Do what is needful!" Ursula LeGuin: Earthsea --
Re: trouble scoring the LZ-DX contest
Hi Joop, Am Sun, 17 Nov 2019 10:30:22 +0100 schrieb Joop Stakenborg : > First of all, thanks for the new release! I have started using tlf a > few weeks ago, very happy! > Nice to hear. > > I am having trouble scoring the lz-dx contest. Points are okay, but > multipliers not. The multiplier is either the ITU zone or the LZ > district. So I would like to have something like ITU_&_SECTIONS, > which would work the same as DX_&_SECTIONS. > Sigh, it is a trouble with those 'creative' contest designers (Rant off). You are right, at the moment there is no solution for your problem. Scoring your contest results will be correct, as it is done by the contest organizer. But we would want at least a good guess how we are doing. The keyword suggested by you (ITU_&_SECTIONS, or better ZONE_&_SECTIONS) would work (and could be added in the next version of TLF). But I fear there will be another combination of multipliers poping up soon which we do not have in our repertoire. So a better solution is needed - same goes for point scoring. I did some investigation how other contest programs solve these problem. One of the ideas there are to classify multipliers into some main categories: - Country/DXCC - Zone CQ or ITU - Prefix - section or similar With that we could allow more to count more than one category as multi and would need additional rules how to combine the values (add if more than one or score only one) and how to count on different bands (BY-BAND or ONCE). Than your ITU_&_SECTION could be something like: COUNTRY_MULT = DXCC,BY_BAND ZONE_MULT = ITU,BY_BAND ADD I am not sure if that would catch all or at least most of the multi scoring problems for existing contests. Feedback on that is very much welcome. 73, de Tom DL1JBE > > Here is part of my rules file, which does not work properly > (lz_dx_mults attached): > > > # > # CONTEST PARAMETERS > # > # > MULT_LIST=lz_dx_mults > COUNTRYLIST=LZ > SECTION_MULT > ITUMULT > # > # > # POINTS LIST > # > # > COUNTRY_LIST_POINTS=10 > MY_CONTINENT_POINTS=1 > DX_POINTS=3 > > > -- "Do what is needful!" Ursula LeGuin: Earthsea --
Re: feature request: cabrillo template
Hi all, On Sun, Nov 17, 2019 at 06:00:41PM +0100, Thomas Beierlein wrote: > Hi Joop, > > I assume you are talking about the contest and operator related > informations gathered when you want to write a new cabrillo file. > > Can you please elaborate some more about what you have in mind here. > The head part of the cabrillo file is not independent of the contest. > So one template for all seems not to fit. But I see that at least the > operator related part could be common between contests. > > Any comments or suggestions? I don't want to answer for Joop, but I thought about this feature earlier. I imagined like this: logcfg.dat: CABRILLO_DATA=/home/airween/.tlf/HA2OS_general.cab CABRILLO_CONTEST=CQ-WW-CW ... /home/airween/.tlf/HA2OS_general.cab CABROLLO_CALLSIGN: HA2OS CABRILLO_LOCATION: DX CABRILLO_CATEGORY-OPERATOR: SINGLE-OP CABRILLO_CATEGORY-ASSISTED: NON-ASSISTED CABRILLO_CATEGORY-BAND: ALL CABRILLO_CATEGORY-POWER: LOW CABRILLO_CATEGORY-MODE: CW CABRILLO_CATEGORY-TRANSMITTER: ONE CABRILLO_CATEGORY-OVERLAY: CABRILLO_CONTEST= I wrote deribelately the CABRILLO_CONTEST field at two places (logcfg.dat and general data file): the second occurrance of field overwrites the first, so therefore we can replace the values at every contest, but can use a basic data. When user types a ":w" in callsign field (start to export the log to CABRILLO), then the fields which has values (by set them the fields above) will filled in dialogues. If you like this way, I can start to implement it soon. 73, Ervin HA2OS
Re: feature request: cabrillo template
Hi Joop, I assume you are talking about the contest and operator related informations gathered when you want to write a new cabrillo file. Can you please elaborate some more about what you have in mind here. The head part of the cabrillo file is not independent of the contest. So one template for all seems not to fit. But I see that at least the operator related part could be common between contests. Any comments or suggestions? 73, de Tom DL1JBE Am Sun, 17 Nov 2019 10:32:16 +0100 schrieb Joop Stakenborg : > It would be nice to have a cabrillo template. If present, all the > questions when exporting to cabrillo can be skipped. > > > 73 de Jo PG4I > -- "Do what is needful!" Ursula LeGuin: Earthsea --
Re: TLF-1.4.0 release
Congratulations to Tom and everyone that has worked on this release. I've been quiet for the past year or so as I chose a different challenge about a year ago due, in part, to the lament of some friends. For the handful of events I operate these days I've chosen to use N1MM+ under Wine. It does work though it is a bit (quite a bit) quirky. One feature I really like is to be able to switch from ESM to a CT like mode on the fly. When I do S I much prefer the CT mode and for running ESM works best for me. Another reason to work with it was for our club Field Day operation where other ops seem more comfortable with menus and such. Regardless of what I do, have fun! 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
feature request: cabrillo template
It would be nice to have a cabrillo template. If present, all the questions when exporting to cabrillo can be skipped. 73 de Jo PG4I
trouble scoring the LZ-DX contest
First of all, thanks for the new release! I have started using tlf a few weeks ago, very happy! I am having trouble scoring the lz-dx contest. Points are okay, but multipliers not. The multiplier is either the ITU zone or the LZ district. So I would like to have something like ITU_&_SECTIONS, which would work the same as DX_&_SECTIONS. Here is part of my rules file, which does not work properly (lz_dx_mults attached): # # CONTEST PARAMETERS # # MULT_LIST=lz_dx_mults COUNTRYLIST=LZ SECTION_MULT ITUMULT # # # POINTS LIST # # COUNTRY_LIST_POINTS=10 MY_CONTINENT_POINTS=1 DX_POINTS=3 bu bl vn vt vd vr ga do ka kd lv mn pa pk pl pd rz rs ss sl sm sf so sz ta ha sn ya
