Skip to content

Conversation

@szporwolik
Copy link
Contributor

@szporwolik szporwolik commented Nov 1, 2025

Goal

The main goal is to update the Bandplan list functionality, addressing multiple user requests and aligning this view with other DX Cluster tools.
It should be convenient to use, easy to read, and—thanks to the API backend—significantly faster than the current implementation.

Prototype

screenshot

Note: what you see at my screens is my own tweaked DX Cluster cache, I proposed the changes in int2001/DXClusterAPI#31 to improve SOTA spot creation.

Tasks

  • Merge CQ zone logic
  • Implement toasts
  • Re-do CAT handling at this page using common libraries
  • Bugs and features
    • Sending log to QSO window shall also populate references (if we have any)
    • User settings - band and modes shall affect page behavior
    • Contest Only behavior is wrong, this shall behave like LoTW filter
    • Small highlight of new spots (as in the old code)
    • Frequency marker (as in the old code)
    • Table broken when using translations (German, Polish etc.)
    • Css breaking DXCC quick lookup table
  • Re-work how/what filters are send to API calls
    • Filter by continent logic shall be improved
    • Reduce server load by possibly limiting the query size to minimum (ex. when tied to radio only one band shall be pulled)
  • Review feedback
    • Button to turn on and off - CAT band tracking; expected behavior:
    • ON (default): Follow CAT // Only CAT-Band shown
    • OFF: Follow CAT // All Bands shown
    • Check font in the filters popup
    • Disable CAT pooling when CAT control is OFF
    • Contest flag - contest name in the tooltip and improved detection
    • Date of previous QSO - broken at some instances see [DX Cluster] Bandplan List Update #2479 (comment)
    • Clear text search icon
    • Add DX quick filter
    • Add ITU zone popup
    • Add Continent popup
    • Sorting of the table - freq is always numeric
    • Consider using leaflet.geodesic.js
    • Send spot to : "Post QSO" or "Live QSO" - decision
  • Ready for review
    • Remove cache prevention tricks
    • Finalize UI prototype
    • Translation support
    • Code refactoring (this will be massive task)
    • Remove debug logs
    • Complete all previous tasks
    • Final testing

@int2001
Copy link
Contributor

int2001 commented Nov 1, 2025

good idea.
put an extra-button to it. users are already requested to see "All Bands" while CAT is turned on.

Idea a button to toggle:

  • ON (default): Follow CAT // Only CAT-Band shown
  • OFF: Follow CAT // All Bands shown

BTW: Its again very huge. we need time for proper review on those things.

@szporwolik
Copy link
Contributor Author

BTW: Its again very huge. we need time for proper review on those things.

Yes, but this time it was controlled. I have divided API and UI changes to keep those separate.
It huge but it's complete overhaul of the page, there was not really how to do it step by step. I really do try to keep everything organized this time. 😉

Let me work on that, code is still total spaghetti don't even bother with it yet.
Now it's time for the functionality and behavior discussion.

Thanks @int2001 for initial ideas - will do.

If somebody would like to have a cup of coffee and click through it, all feedback is highly appreciated.

@AndreasK79
Copy link
Contributor

AndreasK79 commented Nov 2, 2025

I gave this a test, and I like it very much. Well done!

While testing, I made a note of a few things:

  • The font size in the filter form is smaller than the rest of the page. Any reason for that? Perhaps keep it the same as the rest of the text/page?
  • imageShow which contest in mouseover? I didn't see it in the comments
  • imageSeems date for previous QSO is wrong. Perhaps an issue with dateformat?
  • When disabling CAT control, should it stop polling the db? Yes, I know about websocket, but for the people not using that :)

@int2001
Copy link
Contributor

int2001 commented Nov 2, 2025

i just tested it. What a beautiful update to my old UI. it needed that ;)
atm no things found besides those andreas already found. it's draft - so i'll wait for review until you tell us: "further tests needed"

@szporwolik
Copy link
Contributor Author

Thanks! Still a lots to do.

@int2001 not sure how the SAT spots are handled by the cache and there is not many to check. Shall we care, if so - any ideas how to handle it ?

@int2001
Copy link
Contributor

int2001 commented Nov 2, 2025

SAT is an own playground. Even if i also do a lot of LEO/GEO-SAT, @phl0 is our "SAT-Guru".
my 2 Ct. on SAT-Spots: SAT is most of the time done via special socialmedia-groups and not via Clusters.

Of course there are SAT-Spots from time to time. but i personally know no SAT-OP (and i know a lot of them ;) who is using a classic cluster.

@phl0
Copy link
Contributor

phl0 commented Nov 2, 2025

Same view as @int2001. LEO satellites have visibility of max. 15 - 20 min. Guess no one is watching the cluster while working the birds as you usually have one hand less than needed to operate satellites anyway...

@szporwolik
Copy link
Contributor Author

LOL, thanks - that makes things easier (or at least does not add additional complexity 😉 )

@int2001
Copy link
Contributor

int2001 commented Nov 2, 2025

Came just to my mind:
What about selecting more than one band or selecting "worked, not confirmed" and "not worked" in parallel?

Nothing urgent. Just as idea

@int2001
Copy link
Contributor

int2001 commented Nov 6, 2025

just oberved: clicking on a Spot opens "Post QSO" and not "Live QSO". intended?

@szporwolik
Copy link
Contributor Author

Intended for now - to be further discussed/tested. The issue is that if one has open both pages with radio control enabled, I'm not sure if there will be no collisions. Need to test and check - with the new DX Waterfall the issues are less likely (freq field is not controlling radio anymore).

@szporwolik szporwolik marked this pull request as ready for review November 7, 2025 19:18
Copy link
Contributor

@phl0 phl0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I rolled this out to my dev and clicked around for a while. No issues so far though tests only non-CAT here atm.

@AndreasK79 AndreasK79 merged commit 199fb97 into wavelog:dev Nov 10, 2025
@szporwolik szporwolik deleted the dev_dx_cluster_ui branch November 16, 2025 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants