vk6flab / contest-logger Goto Github PK

Similar macros to other popular logging software, i.e., consistency for F1-F2-F3, etc., function keys.

Charles NK8O

It would also be good if it could send the log to LOTW and keep track of what contacts have and have not been sent.

Bob, K4RFK

[..[]writing a summary sheet for Score 3830 [..]

Bob, K4RFK

Hi Onno,

Perhaps you like to add to you list, the ability to upload live data to one of the contest scoring live display sites, if Internet connectivity is available.

Given the wish from some to make AR Contesting more into sport, not only for those taking part but also for "spectators", using these websites allows "outsiders" to see how teams / individuals are doing.

We had such a system running at WRTC2018 on an internal IP network and it drew lots of compliments. since then the publicly accessible scoreboards have expanded their capabilities and can certainly cover most of the major contests now.

73 Ed DD5LP.

http://www.w1hkj.com/FldigiHelp/xmlrpc_control_page.html describes an existing XMLRPC "control method [...] currently used by several external programs including flrig, logger32 and Xlog"

I confess I haven't researched too deep, but piggy-backing on that MAY mean you can pretend to be flog / logger32 for the purpose of receiving logs directly from those other programs, and/or sneak your way into an existing ecosystem or three?

If it looks like it's going to be a total PITA, forget it, and/or consider looking into other standards that may be out there... Or make a new standard because https://xkcd.com/927/ 😆

As a regular logging program a simple uncluttered interface would be nice. N3FJP's programs have a good interface....in my opinion. Log4OM is so cluttered that sometimes its hard to move around in it if you need to change something or want to skip something.

Bob, K4RFK

Extensibility is generally a useful feature for many applications. WebAssembly (WASM) has been used originally to port non-JavaScript applications to the browser, and now it's starting to gain traction on the backend as well. It may be a way to support a polyglot plugin system, allowing contributors to code functionality in their preferred programming language and have it run sandboxed within the application.

This is not so much a feature request, just a way to get your thoughts on this, if you were already aware of it.

Chrome DevTools Lighthouse reports the following error:

Content is not sized correctly for the viewport The viewport size of 368px does not match the window size of 360px.[1]

[1] https://developer.chrome.com/docs/lighthouse/pwa/content-width/?utm_source=lighthouse&utm_medium=devtools

Chrome DevTools Lighthouse reports the following error:

Manifest doesn't have a maskable icon[1]

[1] https://developer.chrome.com/docs/lighthouse/pwa/maskable-icon-audit/?utm_source=lighthouse&utm_medium=devtools

Chrome DevTools Lighthouse reports the following error:

Background and foreground colors do not have a sufficient contrast ratio.[1]

[1] https://dequeuniversity.com/rules/axe/4.4/color-contrast?utm_source=lighthouse&utm_medium=devtools

The error shows the blue "Log" button with white text.

Should use the Amateur Contesting Standard presumably?
I mean I heard the maintainer is a bit hard to work with 😜 , but, y'now, any standard is better than no standard, right? 😁

The current style sheet doesn't use the screen properly. It was chosen as a starting point for semantic HTML, but it's not compact in it's layout behaviour.

The data entry form should fit on the screen entirely and likely will need to consider onscreen keyboards as well.

When working weak stations or in noisy band conditions, having additional context to verify the callsign you thought you heard can be useful. Some loggers do this with a qrz.com lookup. It would be nice to enter a callsign and see the owner's name, location, and license class. The person using the logger can then say "Was that WT0RJ, Trevor in Colorado?" and I can then be sure they got my callsign right, even if it was hard to tell if they got all the letters right. Showing the license class is helpful in the U.S. (and probably other countries): if you're on an HF band and the callsign shows as a Technician license you'll want to double-check the callsign, since that station probably isn't allowed to transmit on this frequency.

As a bonus, it would be great if this callsign data were available for offline operation, periodically updated from a cloud server when the app is online.

The current implementation updates the date and time in real-time, this prevents the user from entering their own time.

Simple networking of computers for multi-op sites.

Charles, NK8O

... cos it strikes me that if you can do all the logging for contests, and can have configurable fields for different contests, then a set of fields for "not a contest" would be really trivial too, then I could use the same software for my day-to-day logs too.
... and if you can calculate different scores based on different contest rules, and perhaps highlight different states/classes/bands that could improve your multipliers... then counting for WAS / DXCC / IOTO/POTA/SOTA and highlighting missing countries/islands/etc would be fairly easy to do, probably under the same rules engine? 🤨

Ideally it should be based on "electron" (https://electronjs.org/) although many consider it bloated.

A client-server web application would be a remedy to that but requiring internet connectivity, maintaining a server (or have a local web server as in the jupyter project (https://jupyter.org/).

73 de IV3IFZ and thank you for your podcast

Paper logging for me is great because I can write down multiple times the call sing I hear and finally pic the right version. After that usually RST and a Number are exchanged. This Informations are going out and coming in on paper I Tag my Notes with “i /in” and “o/out”. An input could look like this.
DO8 DO8A DO8E DO8EW 59i 025i 59o o001
Representing I heard DO8EW recived 59 and Number 025 I reported a 59 with Number 001.

It appears that on Android Chrome tapping the "Log" button doesn't log if the cursor is still in the "Call" field.

[..] track the time spent working the contest [..]

Bob, K4RFK