Rsclub2_2andClaude Fable 5.1
2eb1ba22cf
* build: configure the Windows MSI installer in the Compose windows block (#61) Add the jpackage/WiX options for a per-user MSI next to the existing icon: a fixed upgradeUuid so Windows Installer replaces an installed KST4Contest instead of installing side by side, a Start menu group and desktop shortcut, no UAC prompt, and a directory chooser. The portable ZIP (createDistributable) is unaffected; the MSI is produced only by the tagged-release workflow. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * ci: build and attach a Windows MSI installer for tagged releases (#61) The Windows job of tagged-release.yml now runs packageMsi after the portable ZIP, renames the result to KST4Contest-<tag>-windows-x64.msi (consistent with the other platforms; the ZIP keeps its praktiKST name) and uploads it as the windows-msi artifact, which the release job downloads and attaches next to the ZIP. The nightly workflow stays ZIP-only because a nightly MSI would always carry the same version. The website download data (downloads.js, beta.js) gets an MSI card that is shown only when the release actually has that asset, so the page never links to a file that does not exist for an older release. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * docs: describe the Windows MSI installer next to the portable ZIP (#61) The German and English installation manuals list the MSI in the package table, describe both Windows forms (installer: per user, Start menu entry, desktop shortcut, chosen directory, in-place upgrade, removal via the Windows apps list; ZIP: portable) and the shared data directory %USERPROFILE%\.praktiKST, and add the MSI path to the Windows update section. Changelog entries for v1.50 and a note in PROJECT_CONTEXT.md record the fixed upgrade UUID and the tags-only decision. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * ci: build the Windows MSI for stable tags only (#61) A beta MSI would carry the same composePackageVersion as the following stable release. jpackage's MSI upgrade table only accepts strictly higher versions, so Windows Installer would refuse the stable over an installed beta and the tester would have to uninstall first. Betas therefore stay ZIP-only like nightlies; the build, upload and download steps are skipped for beta- tags, and the release action tolerates the missing asset path. Manual, changelog and project context say so. Raised by the Codex review on #111. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
KST4Contest
KST4Contest is a Java-based client for the ON4KST chat, developed for coordinated VHF, UHF and microwave contest operation.
The application is developed by Marc Fröhlich (DO5AMF) and since 2026 Philipp Wagner (DN9APW).
Start here
- Project website
- Download Stable, Beta and Nightly builds
- Online manual
- GitHub wiki
- Issues and bug reports
- Development roadmap
What KST4Contest does
KST4Contest combines the ON4KST chat with information that is useful when coordinating contacts during a contest.
Among other things, it can:
- display and filter stations from the supported ON4KST chat categories;
- derive band and frequency information from chat messages and station names;
- maintain Worked and NOT QRV information for the available bands;
- calculate station priorities from distance, activity and other available information;
- manage internal skeds and received Win-Test skeds;
- use AirScout information when evaluating possible aircraft-scatter contacts;
- display stations, paths and additional propagation information on maps;
- exchange information with supported logging programs, Win-Test, PSTRotator and a local DX Cluster interface;
- provide configurable automatic replies for recurring chat requests.
Calculated scores, aircraft-scatter information and path assessments are operating aids. They depend on the available data and should not be treated as guarantees that a contact is possible.
Installation
Ready-to-use packages are available for Windows, Linux and macOS. These packages include the required Java runtime, so a separate Java installation is normally not necessary.
Use the central download page to select the appropriate build:
- Stable is intended for normal contest operation.
- Beta contains changes that are being prepared for a stable release.
- Nightly contains the latest automated development build and is mainly intended for testing.
Documentation
The documentation is available in German and English:
The Markdown sources used for the wiki and the generated PDF manuals are stored in github_docs.
Changes to operating behaviour should be documented together with their purpose and limitations. This is especially important for functions whose result depends on external data, heuristics or information derived from chat messages.
Building from source
Building KST4Contest requires JDK 21. The Gradle Wrapper included in the repository should be used, so a separate Gradle installation is not required.
Linux and macOS:
./gradlew clean build
Windows:
.\gradlew.bat clean build
Repository structure
core/– domain, controller and network code, free of user-interface technologyapp-desktop/– the Compose Multiplatform user interface and the packaging tasksgithub_docs/– German and English manual sourceswebsite/– project website sourcespackaging/– platform-specific packaging files
CI status
Documentation
Builds
License
KST4Contest is distributed under the GNU General Public License v3.0.