Volunteering an alternate instrument UI upstream - #8
Open
on8st wants to merge 1 commit into
Open
Conversation
Doc-only PR (no functional changes) - Issues and Discussions are both disabled on this repo, so this is the closest available channel to open a conversation. See PROPOSAL.md for the full write-up: an alternate front-end UI built for a live multi-band (HF/VHF/UHF) station, offered upstream if there's interest. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Aug 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi Wayne,
I run a multi-band amateur station (ON8ST, Belgium) built on
ka9q-radio, covering HF (RX888), VHF (RTL-SDR, 2m) and UHF (Airspy R2, 70cm), with UberSDR andka9q-webboth running as front ends. Full details on the setup are on my shack server: https://shack.on8st.be/.ka9q-web's support for non-zero-centred (tuner-based) front ends needed a fair amount of work to get right for VHF/UHF specifically — happy to open a separate PR for those server-side fixes if useful, independent of everything below.The main reason I'm writing: I built a second, alternate front-end UI for
ka9q-web— a from-scratch "instrument" style interface (single scope canvas, segment+popover controls, mobile-responsive) that I ended up liking enough to make my station's default landing page, with the stock UI kept alongside for reference. In principle, most of the existing controls have been implemented for backward compatibility — feature parity with stock is mechanically checked, not just claimed — plus a few things stock doesn't have (band-edge markers, mode-by-frequency, a live status drawer). Some polishing is probably still needed here and there, but it's solid enough day-to-day that I've been running on it myself.I'd like to volunteer it back upstream if you're interested — not assuming you want a second bundled UI, just offering.
HF:
VHF:
UHF:
Live right now:
(stock UI is still there too, at
/legacy/radio.htmlon each)Source: https://github.com/on8st/ka9q-web, branch
on8st-vhf-uhf.No pressure either way — let me know if this is something you'd want, and if so how you'd want it structured (subdirectory, opt-in flag, separate repo, whatever fits your project best).
This PR is doc-only (a proposal writeup + screenshots, no functional changes) — Issues and Discussions are both off on this repo, so it's the closest channel I had to start a conversation. Happy to close it once we've talked, or turn it into a real PR if there's interest.
73,
on8st-stan