mirror of
https://github.com/praktimarc/kst4contest.git
synced 2026-06-23 06:16:37 +02:00
Compare commits
1 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 github-actions[bot]
|
a9088d50d7 |
@@ -1,258 +0,0 @@
|
|||||||
%% ============================================================
|
|
||||||
%% KST4Contest – pandoc LaTeX manual template
|
|
||||||
%% PDF engine: XeLaTeX
|
|
||||||
%% Usage: pandoc --template=manual-template.tex --pdf-engine=xelatex
|
|
||||||
%% ============================================================
|
|
||||||
\documentclass[11pt,a4paper]{article}
|
|
||||||
|
|
||||||
%% ─── Font / encoding ──────────────────────────────────────────────────────
|
|
||||||
\usepackage{fontspec}
|
|
||||||
% Latin Modern handles all Western European characters (umlauts etc.)
|
|
||||||
\defaultfontfeatures{Ligatures=TeX,Scale=MatchLowercase}
|
|
||||||
|
|
||||||
%% ─── Language ─────────────────────────────────────────────────────────────
|
|
||||||
\usepackage{polyglossia}
|
|
||||||
$if(polyglossia-lang)$
|
|
||||||
\setmainlanguage{$polyglossia-lang$}
|
|
||||||
$else$
|
|
||||||
\setmainlanguage{english}
|
|
||||||
$endif$
|
|
||||||
|
|
||||||
%% ─── Page layout ──────────────────────────────────────────────────────────
|
|
||||||
\usepackage[a4paper, top=2.5cm, bottom=2.5cm, left=2.5cm, right=2.5cm]{geometry}
|
|
||||||
|
|
||||||
%% ─── Text decorations (strikethrough via ~~...~~ in Markdown → \st{}) ────
|
|
||||||
\usepackage{soul}
|
|
||||||
|
|
||||||
%% ─── Colors ───────────────────────────────────────────────────────────────
|
|
||||||
\usepackage[dvipsnames,svgnames,x11names]{xcolor}
|
|
||||||
\definecolor{brand-green}{RGB}{7,166,54}
|
|
||||||
\definecolor{link-blue}{RGB}{0,86,163}
|
|
||||||
\definecolor{code-bg}{RGB}{245,247,250}
|
|
||||||
\definecolor{code-border}{RGB}{180,200,225}
|
|
||||||
\definecolor{blockquote-line}{RGB}{7,166,54}
|
|
||||||
|
|
||||||
%% ─── Hyperlinks ───────────────────────────────────────────────────────────
|
|
||||||
\usepackage{hyperref}
|
|
||||||
\hypersetup{
|
|
||||||
colorlinks = true,
|
|
||||||
linkcolor = link-blue,
|
|
||||||
urlcolor = link-blue,
|
|
||||||
filecolor = link-blue,
|
|
||||||
citecolor = link-blue,
|
|
||||||
pdftitle = {$title$},
|
|
||||||
pdfauthor = {DO5AMF (Marc Fröhlich), DN9APW (Philipp Wagner)},
|
|
||||||
pdfsubject = {KST4Contest User Manual},
|
|
||||||
pdfkeywords = {KST4Contest, pratiKST, VHF, Contest, Ham Radio},
|
|
||||||
bookmarks = true,
|
|
||||||
bookmarksnumbered = true,
|
|
||||||
bookmarksopen = true,
|
|
||||||
bookmarksopenlevel = 2,
|
|
||||||
pdfpagemode = UseOutlines,
|
|
||||||
}
|
|
||||||
|
|
||||||
%% ─── Graphics ─────────────────────────────────────────────────────────────
|
|
||||||
\usepackage{graphicx}
|
|
||||||
\graphicspath{{./}{./github_docs/}}
|
|
||||||
\makeatletter
|
|
||||||
\def\maxwidth{\ifdim\Gin@nat@width>\linewidth\linewidth\else\Gin@nat@width\fi}
|
|
||||||
\def\maxheight{\ifdim\Gin@nat@height>0.65\textheight 0.65\textheight\else\Gin@nat@height\fi}
|
|
||||||
\makeatother
|
|
||||||
\setkeys{Gin}{width=\maxwidth,height=\maxheight,keepaspectratio}
|
|
||||||
|
|
||||||
%% ─── Tables ───────────────────────────────────────────────────────────────
|
|
||||||
\usepackage{longtable}
|
|
||||||
\usepackage{booktabs}
|
|
||||||
\usepackage{array}
|
|
||||||
\usepackage{calc}
|
|
||||||
\usepackage{multirow}
|
|
||||||
\setlength{\tabcolsep}{8pt}
|
|
||||||
\renewcommand{\arraystretch}{1.35}
|
|
||||||
% Pandoc pipe-table helpers
|
|
||||||
\newcolumntype{L}[1]{>{\raggedright\arraybackslash}p{#1}}
|
|
||||||
\newcolumntype{C}[1]{>{\centering\arraybackslash}p{#1}}
|
|
||||||
\newcolumntype{R}[1]{>{\raggedleft\arraybackslash}p{#1}}
|
|
||||||
|
|
||||||
%% ─── Lists ────────────────────────────────────────────────────────────────
|
|
||||||
\providecommand{\tightlist}{%
|
|
||||||
\setlength{\itemsep}{2pt}\setlength{\parskip}{0pt}}
|
|
||||||
|
|
||||||
%% ─── Code blocks (--listings flag) ───────────────────────────────────
|
|
||||||
\usepackage{listings}
|
|
||||||
\lstset{
|
|
||||||
basicstyle = \ttfamily\small,
|
|
||||||
backgroundcolor = \color{code-bg},
|
|
||||||
frame = single,
|
|
||||||
framesep = 4pt,
|
|
||||||
rulecolor = \color{code-border},
|
|
||||||
breaklines = true,
|
|
||||||
breakatwhitespace= false,
|
|
||||||
showstringspaces = false,
|
|
||||||
extendedchars = true,
|
|
||||||
xleftmargin = 6pt,
|
|
||||||
xrightmargin = 6pt,
|
|
||||||
aboveskip = 8pt,
|
|
||||||
belowskip = 8pt,
|
|
||||||
literate = {→}{{\ensuremath{\rightarrow}}}1
|
|
||||||
{←}{{\ensuremath{\leftarrow}}}1
|
|
||||||
{↔}{{\ensuremath{\leftrightarrow}}}1,
|
|
||||||
}
|
|
||||||
|
|
||||||
%% ─── Blockquotes ──────────────────────────────────────────────────────────
|
|
||||||
\usepackage{mdframed}
|
|
||||||
\newmdenv[
|
|
||||||
topline = false,
|
|
||||||
rightline = false,
|
|
||||||
bottomline = false,
|
|
||||||
leftline = true,
|
|
||||||
linewidth = 3pt,
|
|
||||||
linecolor = blockquote-line,
|
|
||||||
backgroundcolor = code-bg,
|
|
||||||
leftmargin = 0pt,
|
|
||||||
rightmargin = 0pt,
|
|
||||||
innerleftmargin = 12pt,
|
|
||||||
innerrightmargin = 8pt,
|
|
||||||
innertopmargin = 6pt,
|
|
||||||
innerbottommargin= 6pt,
|
|
||||||
skipabove = 8pt,
|
|
||||||
skipbelow = 8pt,
|
|
||||||
]{blockquotebox}
|
|
||||||
|
|
||||||
\renewenvironment{quote}
|
|
||||||
{\begin{blockquotebox}\small\itshape}
|
|
||||||
{\end{blockquotebox}}
|
|
||||||
|
|
||||||
%% ─── Section styling ──────────────────────────────────────────────────────
|
|
||||||
\usepackage{titlesec}
|
|
||||||
|
|
||||||
\titleformat{\section}
|
|
||||||
{\Large\bfseries\color{brand-green}}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
[\color{brand-green}\titlerule]
|
|
||||||
\titlespacing{\section}{0pt}{20pt}{10pt}
|
|
||||||
|
|
||||||
\titleformat{\subsection}
|
|
||||||
{\large\bfseries\color{brand-green}}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
\titlespacing{\subsection}{0pt}{14pt}{6pt}
|
|
||||||
|
|
||||||
\titleformat{\subsubsection}
|
|
||||||
{\normalsize\bfseries}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
\titlespacing{\subsubsection}{0pt}{10pt}{4pt}
|
|
||||||
|
|
||||||
% Level 4 (####): displayed as a named block heading in dark-grey
|
|
||||||
\titleformat{\paragraph}
|
|
||||||
{\normalsize\bfseries\color{brand-green}}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
\titlespacing{\paragraph}{0pt}{8pt}{2pt}
|
|
||||||
|
|
||||||
% Level 5 (#####): slightly smaller, italic, lighter grey
|
|
||||||
\titleformat{\subparagraph}
|
|
||||||
{\small\bfseries\itshape\color{brand-green!85!black}}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
\titlespacing{\subparagraph}{0pt}{6pt}{1pt}
|
|
||||||
|
|
||||||
% Reserve two additional section levels for future use (###### and deeper).
|
|
||||||
% Pandoc currently maps up to \subparagraph for standard Markdown headings.
|
|
||||||
\titleclass{\subsubsubsection}{straight}[\subparagraph]
|
|
||||||
\newcounter{subsubsubsection}[subparagraph]
|
|
||||||
\renewcommand\thesubsubsubsection{\thesubparagraph.\arabic{subsubsubsection}}
|
|
||||||
\titleformat{\subsubsubsection}
|
|
||||||
{\small\bfseries\color{brand-green!75!black}}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
\titlespacing{\subsubsubsection}{0pt}{5pt}{1pt}
|
|
||||||
|
|
||||||
\titleclass{\subsubsubsubsection}{straight}[\subsubsubsection]
|
|
||||||
\newcounter{subsubsubsubsection}[subsubsubsection]
|
|
||||||
\renewcommand\thesubsubsubsubsection{\thesubsubsubsection.\arabic{subsubsubsubsection}}
|
|
||||||
\titleformat{\subsubsubsubsection}
|
|
||||||
{\small\itshape\color{brand-green!65!black}}
|
|
||||||
{}
|
|
||||||
{0em}
|
|
||||||
{}
|
|
||||||
\titlespacing{\subsubsubsubsection}{0pt}{4pt}{1pt}
|
|
||||||
|
|
||||||
\setcounter{secnumdepth}{6}
|
|
||||||
\setcounter{tocdepth}{6}
|
|
||||||
|
|
||||||
%% ─── Header / Footer ──────────────────────────────────────────────────────
|
|
||||||
\usepackage{fancyhdr}
|
|
||||||
\pagestyle{fancy}
|
|
||||||
\fancyhf{}
|
|
||||||
\fancyhead[L]{\small\color{brand-green}\textbf{KST4Contest}}
|
|
||||||
\fancyhead[R]{\small\color{brand-green}$if(version)$$version$$endif$}
|
|
||||||
\fancyfoot[L]{\small\color{gray}DO5AMF \textbar\ DN9APW}
|
|
||||||
\fancyfoot[C]{\small\color{gray}\thepage}
|
|
||||||
\fancyfoot[R]{\small\color{gray}$title$}
|
|
||||||
\renewcommand{\headrulewidth}{0.4pt}
|
|
||||||
\renewcommand{\footrulewidth}{0.3pt}
|
|
||||||
\renewcommand{\headrule}{\color{brand-green}\hrule width\headwidth height\headrulewidth}
|
|
||||||
|
|
||||||
%% ─── Paragraph spacing ────────────────────────────────────────────────────
|
|
||||||
\usepackage{parskip}
|
|
||||||
\setlength{\parskip}{6pt}
|
|
||||||
\setlength{\parindent}{0pt}
|
|
||||||
|
|
||||||
%% ─── TOC styling ──────────────────────────────────────────────────────────
|
|
||||||
\usepackage{tocloft}
|
|
||||||
\renewcommand{\cfttoctitlefont}{\Large\bfseries\color{brand-green}}
|
|
||||||
\renewcommand{\cftsecfont}{\bfseries\color{brand-green}}
|
|
||||||
\renewcommand{\cftsecpagefont}{\bfseries\color{brand-green}}
|
|
||||||
\renewcommand{\cftsubsecfont}{\color{brand-green}}
|
|
||||||
\renewcommand{\cftsubsecpagefont}{\color{brand-green}}
|
|
||||||
\renewcommand{\cftsubsubsecfont}{\color{brand-green!85!black}}
|
|
||||||
\renewcommand{\cftsubsubsecpagefont}{\color{brand-green!85!black}}
|
|
||||||
\renewcommand{\cftparafont}{\color{brand-green!75!black}}
|
|
||||||
\renewcommand{\cftparapagefont}{\color{brand-green!75!black}}
|
|
||||||
\renewcommand{\cftsubparafont}{\color{brand-green!65!black}}
|
|
||||||
\renewcommand{\cftsubparapagefont}{\color{brand-green!65!black}}
|
|
||||||
\setlength{\cftbeforesecskip}{4pt}
|
|
||||||
|
|
||||||
%% ─── Misc ─────────────────────────────────────────────────────────────────
|
|
||||||
\usepackage{amsmath}
|
|
||||||
\usepackage{microtype}
|
|
||||||
% Pandoc helper macros
|
|
||||||
\newcommand{\passthrough}[1]{#1}
|
|
||||||
|
|
||||||
%% ══════════════════════════════════════════════════════════════════════════
|
|
||||||
\begin{document}
|
|
||||||
|
|
||||||
%% ─── Title page ───────────────────────────────────────────────────────────
|
|
||||||
\begin{titlepage}
|
|
||||||
\pagecolor{brand-green}
|
|
||||||
\centering
|
|
||||||
\vspace*{3.5cm}
|
|
||||||
{\fontsize{52}{62}\selectfont\bfseries\color{white}KST4Contest}\\[0.4cm]
|
|
||||||
{\fontsize{22}{28}\selectfont\color{white!75!brand-green}pratiKST (ON4KST Chat Client)}\\[2.8cm]
|
|
||||||
\color{white!40!brand-green}\rule{10cm}{0.6pt}\\[1.8cm]
|
|
||||||
{\LARGE\bfseries\color{white}$title$}\\[1cm]
|
|
||||||
$if(version)${\large\color{white!80!brand-green}Version:\space$version$}\\[0.6cm]$endif$
|
|
||||||
\vfill
|
|
||||||
{\large\color{white}DO5AMF · Marc Fröhlich · DM5M · DN9APW · Philipp Wagner}\\[0.4cm]
|
|
||||||
{\color{white!70!brand-green}\today}\\[2cm]
|
|
||||||
\end{titlepage}
|
|
||||||
|
|
||||||
\pagecolor{white}
|
|
||||||
\newpage
|
|
||||||
|
|
||||||
%% ─── Table of Contents ────────────────────────────────────────────────────
|
|
||||||
\tableofcontents
|
|
||||||
\newpage
|
|
||||||
|
|
||||||
%% ─── Main content ─────────────────────────────────────────────────────────
|
|
||||||
$body$
|
|
||||||
|
|
||||||
\end{document}
|
|
||||||
@@ -1,156 +0,0 @@
|
|||||||
--[[
|
|
||||||
strip-wiki-links.lua – pandoc Lua filter for KST4Contest documentation
|
|
||||||
-----------------------------------------------------------------------
|
|
||||||
1. Removes language-switch blockquotes (GitHub Wiki navigation) that
|
|
||||||
are not relevant in the printed PDF manual.
|
|
||||||
2. Converts internal GitHub-wiki-style links to in-document anchors
|
|
||||||
so links jump within the generated PDF.
|
|
||||||
3. Replaces flag emoji and other symbols that XeLaTeX cannot render with
|
|
||||||
plain-text equivalents.
|
|
||||||
--]]
|
|
||||||
|
|
||||||
local PAGE_ANCHOR_MAP = {
|
|
||||||
["de-Home"] = "kst4contest-wiki",
|
|
||||||
["de-Installation"] = "installation",
|
|
||||||
["de-Konfiguration"] = "konfiguration",
|
|
||||||
["de-Funktionen"] = "funktionen",
|
|
||||||
["de-Benutzeroberflaeche"] = "benutzeroberflache",
|
|
||||||
["de-Makros-und-Variablen"] = "makros-und-variablen",
|
|
||||||
["de-Log-Synchronisation"] = "log-synchronisation",
|
|
||||||
["de-AirScout-Integration"] = "airscout-integration",
|
|
||||||
["de-DX-Cluster-Server"] = "integrierter-dx-cluster-server",
|
|
||||||
["de-Changelog"] = "changelog",
|
|
||||||
|
|
||||||
["en-Home"] = "kst4contest-wiki",
|
|
||||||
["en-Installation"] = "installation",
|
|
||||||
["en-Configuration"] = "configuration",
|
|
||||||
["en-Features"] = "features",
|
|
||||||
["en-User-Interface"] = "user-interface",
|
|
||||||
["en-Macros-and-Variables"] = "macros-and-variables",
|
|
||||||
["en-Log-Sync"] = "log-synchronisation",
|
|
||||||
["en-AirScout-Integration"] = "airscout-integration",
|
|
||||||
["en-DX-Cluster-Server"] = "built-in-dx-cluster-server",
|
|
||||||
["en-Changelog"] = "changelog",
|
|
||||||
|
|
||||||
["Installation"] = "installation",
|
|
||||||
["Konfiguration"] = "konfiguration",
|
|
||||||
["Funktionen"] = "funktionen",
|
|
||||||
["Benutzeroberflaeche"] = "benutzeroberflache",
|
|
||||||
["Makros-und-Variablen"] = "makros-und-variablen",
|
|
||||||
["Log-Synchronisation"] = "log-synchronisation",
|
|
||||||
["AirScout-Integration"] = "airscout-integration",
|
|
||||||
["DX-Cluster-Server"] = "integrierter-dx-cluster-server",
|
|
||||||
["Changelog"] = "changelog",
|
|
||||||
|
|
||||||
["Configuration"] = "configuration",
|
|
||||||
["Features"] = "features",
|
|
||||||
["User-Interface"] = "user-interface",
|
|
||||||
["Macros-and-Variables"] = "macros-and-variables",
|
|
||||||
["Log-Sync"] = "log-synchronisation",
|
|
||||||
}
|
|
||||||
|
|
||||||
local function normalize_anchor(text)
|
|
||||||
local s = text:lower()
|
|
||||||
s = s:gsub("%%20", "-")
|
|
||||||
s = s:gsub("ä", "a"):gsub("ö", "o"):gsub("ü", "u"):gsub("ß", "ss")
|
|
||||||
s = s:gsub("[^%w%s%-_]", "")
|
|
||||||
s = s:gsub("[_%s]+", "-")
|
|
||||||
s = s:gsub("%-+", "-")
|
|
||||||
s = s:gsub("^%-", ""):gsub("%-$", "")
|
|
||||||
return s
|
|
||||||
end
|
|
||||||
|
|
||||||
local function normalize_page_key(page)
|
|
||||||
local key = page:gsub("^%./", ""):gsub("^/", "")
|
|
||||||
key = key:gsub("^github_docs/", "")
|
|
||||||
key = key:gsub("%.md$", "")
|
|
||||||
return key
|
|
||||||
end
|
|
||||||
|
|
||||||
local function resolve_page_anchor(page)
|
|
||||||
local key = normalize_page_key(page)
|
|
||||||
return PAGE_ANCHOR_MAP[key] or normalize_anchor(key)
|
|
||||||
end
|
|
||||||
|
|
||||||
local function convert_url_token(token)
|
|
||||||
local url, trailing = token:match("^(https?://%S-)([%.%,%;%:%!%?]?)$")
|
|
||||||
if not url then
|
|
||||||
return nil
|
|
||||||
end
|
|
||||||
|
|
||||||
local link = pandoc.Link({pandoc.Str(url)}, url)
|
|
||||||
if trailing ~= "" then
|
|
||||||
return {link, pandoc.Str(trailing)}
|
|
||||||
end
|
|
||||||
return link
|
|
||||||
end
|
|
||||||
|
|
||||||
-- Map of emoji / special Unicode sequences → plain-text replacements.
|
|
||||||
-- Add more entries here as needed.
|
|
||||||
local EMOJI_MAP = {
|
|
||||||
-- Flag sequences
|
|
||||||
["\xF0\x9F\x87\xAC\xF0\x9F\x87\xA7"] = "[EN]", -- 🇬🇧
|
|
||||||
["\xF0\x9F\x87\xA9\xF0\x9F\x87\xAA"] = "[DE]", -- 🇩🇪
|
|
||||||
-- Status symbols
|
|
||||||
["\xE2\x9C\x85"] = "[OK]", -- ✅
|
|
||||||
["\xE2\x9D\x8C"] = "[--]", -- ❌
|
|
||||||
-- Misc symbols used in tables / text
|
|
||||||
["\xF0\x9F\x94\xB4"] = "[red]", -- 🔴
|
|
||||||
["\xF0\x9F\x9F\xA1"] = "[yellow]", -- 🟡
|
|
||||||
["\xF0\x9F\x9F\xA2"] = "[green]", -- 🟢
|
|
||||||
}
|
|
||||||
|
|
||||||
--- Replace emoji in a plain string.
|
|
||||||
local function replace_emoji(text)
|
|
||||||
for pattern, replacement in pairs(EMOJI_MAP) do
|
|
||||||
text = text:gsub(pattern, replacement)
|
|
||||||
end
|
|
||||||
return text
|
|
||||||
end
|
|
||||||
|
|
||||||
--- Filter: remove language-switch blockquotes from PDF output.
|
|
||||||
-- These blockquotes appear in every wiki page for GitHub navigation
|
|
||||||
-- but are not needed in the printed manual.
|
|
||||||
function BlockQuote(el)
|
|
||||||
local text = pandoc.utils.stringify(el)
|
|
||||||
if text:find("Du liest gerade die deutsche Version") or
|
|
||||||
text:find("You are reading the English version") then
|
|
||||||
return {}
|
|
||||||
end
|
|
||||||
return el
|
|
||||||
end
|
|
||||||
|
|
||||||
--- Filter: convert internal wiki links to in-PDF anchor links.
|
|
||||||
function Link(el)
|
|
||||||
local target = el.target
|
|
||||||
-- Keep external URLs unchanged.
|
|
||||||
if target:match("^https?://") or target:match("^mailto:") then
|
|
||||||
return el
|
|
||||||
end
|
|
||||||
|
|
||||||
if target:match("^#") then
|
|
||||||
local fragment = target:gsub("^#", "")
|
|
||||||
return pandoc.Link(el.content, "#" .. normalize_anchor(fragment), el.title, el.attr)
|
|
||||||
end
|
|
||||||
|
|
||||||
local page, fragment = target:match("^([^#]+)#(.+)$")
|
|
||||||
if page and fragment then
|
|
||||||
return pandoc.Link(el.content, "#" .. normalize_anchor(fragment), el.title, el.attr)
|
|
||||||
end
|
|
||||||
|
|
||||||
return pandoc.Link(el.content, "#" .. resolve_page_anchor(target), el.title, el.attr)
|
|
||||||
end
|
|
||||||
|
|
||||||
--- Filter: replace emoji sequences in plain Str elements.
|
|
||||||
function Str(el)
|
|
||||||
local linkified = convert_url_token(el.text)
|
|
||||||
if linkified then
|
|
||||||
return linkified
|
|
||||||
end
|
|
||||||
|
|
||||||
local replaced = replace_emoji(el.text)
|
|
||||||
if replaced ~= el.text then
|
|
||||||
return pandoc.Str(replaced)
|
|
||||||
end
|
|
||||||
return el
|
|
||||||
end
|
|
||||||
@@ -1,107 +0,0 @@
|
|||||||
name: Build Documentation PDF
|
|
||||||
|
|
||||||
# Runs when documentation changes are pushed to main, or on manual trigger.
|
|
||||||
# Also triggered as a dependency from the tagged-release workflow.
|
|
||||||
on:
|
|
||||||
push:
|
|
||||||
branches:
|
|
||||||
- main
|
|
||||||
paths:
|
|
||||||
- github_docs/**
|
|
||||||
- .github/latex-manual/**
|
|
||||||
- .github/workflows/docs-pdf.yml
|
|
||||||
workflow_dispatch:
|
|
||||||
|
|
||||||
env:
|
|
||||||
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
|
|
||||||
|
|
||||||
permissions:
|
|
||||||
contents: read
|
|
||||||
|
|
||||||
jobs:
|
|
||||||
build-docs-pdf:
|
|
||||||
name: Build Documentation PDF
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Resolve version string
|
|
||||||
run: |
|
|
||||||
if [[ "${{ github.ref }}" == refs/tags/* ]]; then
|
|
||||||
VERSION="${{ github.ref_name }}"
|
|
||||||
else
|
|
||||||
VERSION="$(grep -m1 '<version>' pom.xml | sed 's/.*<version>\(.*\)<\/version>.*/\1/')-${GITHUB_SHA::7}"
|
|
||||||
fi
|
|
||||||
echo "DOC_VERSION=$VERSION" >> "$GITHUB_ENV"
|
|
||||||
|
|
||||||
- name: Install pandoc and LaTeX toolchain
|
|
||||||
run: |
|
|
||||||
sudo apt-get update -qq
|
|
||||||
sudo apt-get install -y --no-install-recommends \
|
|
||||||
pandoc \
|
|
||||||
texlive-xetex \
|
|
||||||
texlive-fonts-recommended \
|
|
||||||
texlive-latex-extra \
|
|
||||||
texlive-plain-generic
|
|
||||||
|
|
||||||
- name: Build English PDF manual
|
|
||||||
run: |
|
|
||||||
mkdir -p dist
|
|
||||||
pandoc \
|
|
||||||
--from=markdown-yaml_metadata_block \
|
|
||||||
--template=.github/latex-manual/manual-template.tex \
|
|
||||||
--pdf-engine=xelatex \
|
|
||||||
--lua-filter=.github/latex-manual/strip-wiki-links.lua \
|
|
||||||
--resource-path=.:github_docs \
|
|
||||||
--listings \
|
|
||||||
--toc \
|
|
||||||
--toc-depth=6 \
|
|
||||||
-V title="User Manual" \
|
|
||||||
-V polyglossia-lang=english \
|
|
||||||
-V version="${DOC_VERSION}" \
|
|
||||||
-o dist/KST4Contest-${DOC_VERSION}-manual-en.pdf \
|
|
||||||
github_docs/en-Home.md \
|
|
||||||
github_docs/en-Installation.md \
|
|
||||||
github_docs/en-Configuration.md \
|
|
||||||
github_docs/en-Features.md \
|
|
||||||
github_docs/en-User-Interface.md \
|
|
||||||
github_docs/en-Macros-and-Variables.md \
|
|
||||||
github_docs/en-Log-Sync.md \
|
|
||||||
github_docs/en-AirScout-Integration.md \
|
|
||||||
github_docs/en-DX-Cluster-Server.md \
|
|
||||||
github_docs/en-Changelog.md
|
|
||||||
|
|
||||||
- name: Build German PDF manual
|
|
||||||
run: |
|
|
||||||
pandoc \
|
|
||||||
--from=markdown-yaml_metadata_block \
|
|
||||||
--template=.github/latex-manual/manual-template.tex \
|
|
||||||
--pdf-engine=xelatex \
|
|
||||||
--lua-filter=.github/latex-manual/strip-wiki-links.lua \
|
|
||||||
--resource-path=.:github_docs \
|
|
||||||
--listings \
|
|
||||||
--toc \
|
|
||||||
--toc-depth=6 \
|
|
||||||
-V title="Benutzerhandbuch" \
|
|
||||||
-V polyglossia-lang=german \
|
|
||||||
-V version="${DOC_VERSION}" \
|
|
||||||
-o dist/KST4Contest-${DOC_VERSION}-manual-de.pdf \
|
|
||||||
github_docs/de-Home.md \
|
|
||||||
github_docs/de-Installation.md \
|
|
||||||
github_docs/de-Konfiguration.md \
|
|
||||||
github_docs/de-Funktionen.md \
|
|
||||||
github_docs/de-Benutzeroberflaeche.md \
|
|
||||||
github_docs/de-Makros-und-Variablen.md \
|
|
||||||
github_docs/de-Log-Synchronisation.md \
|
|
||||||
github_docs/de-AirScout-Integration.md \
|
|
||||||
github_docs/de-DX-Cluster-Server.md \
|
|
||||||
github_docs/de-Changelog.md
|
|
||||||
|
|
||||||
- name: Upload PDF artifacts
|
|
||||||
uses: actions/upload-artifact@v4.3.4
|
|
||||||
with:
|
|
||||||
name: docs-pdf
|
|
||||||
path: dist/KST4Contest-*-manual-*.pdf
|
|
||||||
retention-days: 30
|
|
||||||
@@ -1,21 +0,0 @@
|
|||||||
name: Publish wiki
|
|
||||||
on:
|
|
||||||
push:
|
|
||||||
branches: [main]
|
|
||||||
paths:
|
|
||||||
- github_docs/**
|
|
||||||
- .github/workflows/github-wiki.yml
|
|
||||||
concurrency:
|
|
||||||
group: publish-wiki
|
|
||||||
cancel-in-progress: true
|
|
||||||
permissions:
|
|
||||||
contents: write
|
|
||||||
jobs:
|
|
||||||
publish-wiki:
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
steps:
|
|
||||||
- uses: actions/checkout@v4
|
|
||||||
- uses: Andrew-Chen-Wang/github-wiki-action@v4
|
|
||||||
with:
|
|
||||||
path: github_docs
|
|
||||||
disable-empty-commits: true
|
|
||||||
@@ -1,154 +0,0 @@
|
|||||||
name: Nightly Runtime Artifacts
|
|
||||||
|
|
||||||
on:
|
|
||||||
push:
|
|
||||||
branches:
|
|
||||||
- main
|
|
||||||
schedule:
|
|
||||||
- cron: "20 2 * * *"
|
|
||||||
workflow_dispatch:
|
|
||||||
|
|
||||||
env:
|
|
||||||
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
|
|
||||||
|
|
||||||
jobs:
|
|
||||||
build-windows-zip:
|
|
||||||
name: Build Windows ZIP
|
|
||||||
runs-on: windows-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Resolve nightly version info
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
$xml = [xml](Get-Content pom.xml)
|
|
||||||
$version = $xml.project.version
|
|
||||||
$shortSha = "${{ github.sha }}".Substring(0, 7)
|
|
||||||
Add-Content -Path $env:GITHUB_ENV -Value "VERSION=$version"
|
|
||||||
Add-Content -Path $env:GITHUB_ENV -Value "SHORT_SHA=$shortSha"
|
|
||||||
Add-Content -Path $env:GITHUB_ENV -Value "ASSET_BASENAME=praktiKST-$version-$shortSha"
|
|
||||||
|
|
||||||
- name: Set up Java 17
|
|
||||||
uses: actions/setup-java@v4.1.0
|
|
||||||
with:
|
|
||||||
distribution: temurin
|
|
||||||
java-version: "17"
|
|
||||||
|
|
||||||
- name: Install WiX Toolset
|
|
||||||
shell: pwsh
|
|
||||||
run: choco install wixtoolset --no-progress -y
|
|
||||||
|
|
||||||
- name: Build JAR and copy runtime dependencies
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
.\mvnw.cmd -B -DskipTests package dependency:copy-dependencies -DincludeScope=runtime -DoutputDirectory=target/dist-libs
|
|
||||||
$jar = Get-ChildItem -Path target -Filter 'praktiKST-*.jar' | Sort-Object LastWriteTime -Descending | Select-Object -First 1
|
|
||||||
if (-not $jar) {
|
|
||||||
throw "No project JAR produced"
|
|
||||||
}
|
|
||||||
Copy-Item $jar.FullName target/dist-libs/app.jar
|
|
||||||
|
|
||||||
- name: Build app-image with jpackage
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
New-Item -ItemType Directory -Force -Path dist | Out-Null
|
|
||||||
jpackage --type app-image --name praktiKST --input target/dist-libs --main-jar app.jar --main-class kst4contest.view.Kst4ContestApplication --module-path target/dist-libs --add-modules javafx.controls,javafx.graphics,javafx.fxml,javafx.web,javafx.media,java.sql --dest dist
|
|
||||||
|
|
||||||
- name: Create Windows ZIP
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
if (-not (Test-Path dist/praktiKST)) {
|
|
||||||
throw "No Windows app-image produced by jpackage"
|
|
||||||
}
|
|
||||||
Compress-Archive -Path dist/praktiKST -DestinationPath "dist/$env:ASSET_BASENAME-windows-x64.zip" -Force
|
|
||||||
|
|
||||||
- name: Upload Windows artifact
|
|
||||||
uses: actions/upload-artifact@v4.3.4
|
|
||||||
with:
|
|
||||||
name: windows-zip
|
|
||||||
path: dist/praktiKST-*-windows-x64.zip
|
|
||||||
retention-days: 14
|
|
||||||
|
|
||||||
build-linux-appimage:
|
|
||||||
name: Build Linux AppImage
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Resolve nightly version info
|
|
||||||
run: |
|
|
||||||
VERSION=$(grep -m1 '<version>' pom.xml | sed 's/.*<version>\(.*\)<\/version>.*/\1/')
|
|
||||||
SHORT_SHA="${GITHUB_SHA::7}"
|
|
||||||
echo "VERSION=$VERSION" >> "$GITHUB_ENV"
|
|
||||||
echo "SHORT_SHA=$SHORT_SHA" >> "$GITHUB_ENV"
|
|
||||||
echo "ASSET_BASENAME=praktiKST-${VERSION}-${SHORT_SHA}" >> "$GITHUB_ENV"
|
|
||||||
|
|
||||||
- name: Set up Java 17
|
|
||||||
uses: actions/setup-java@v4.1.0
|
|
||||||
with:
|
|
||||||
distribution: temurin
|
|
||||||
java-version: "17"
|
|
||||||
|
|
||||||
- name: Ensure mvnw is executable
|
|
||||||
run: chmod +x mvnw
|
|
||||||
|
|
||||||
- name: Build JAR and copy runtime dependencies
|
|
||||||
run: |
|
|
||||||
./mvnw -B -DskipTests package dependency:copy-dependencies -DincludeScope=runtime -DoutputDirectory=target/dist-libs
|
|
||||||
cp "$(ls -t target/praktiKST-*.jar | head -n 1)" target/dist-libs/app.jar
|
|
||||||
|
|
||||||
- name: Build app-image with jpackage
|
|
||||||
run: |
|
|
||||||
mkdir -p dist
|
|
||||||
jpackage \
|
|
||||||
--type app-image \
|
|
||||||
--name praktiKST \
|
|
||||||
--input target/dist-libs \
|
|
||||||
--main-jar app.jar \
|
|
||||||
--main-class kst4contest.view.Kst4ContestApplication \
|
|
||||||
--module-path target/dist-libs \
|
|
||||||
--add-modules javafx.controls,javafx.graphics,javafx.fxml,javafx.web,javafx.media,java.sql \
|
|
||||||
--dest dist
|
|
||||||
|
|
||||||
- name: Create AppDir metadata
|
|
||||||
run: |
|
|
||||||
rm -rf target/praktiKST.AppDir
|
|
||||||
cp -a dist/praktiKST target/praktiKST.AppDir
|
|
||||||
|
|
||||||
cat > target/praktiKST.AppDir/AppRun << 'EOF'
|
|
||||||
#!/bin/sh
|
|
||||||
HERE="$(dirname "$(readlink -f "$0")")"
|
|
||||||
exec "$HERE/bin/praktiKST" "$@"
|
|
||||||
EOF
|
|
||||||
chmod +x target/praktiKST.AppDir/AppRun
|
|
||||||
|
|
||||||
cat > target/praktiKST.AppDir/praktiKST.desktop << 'EOF'
|
|
||||||
[Desktop Entry]
|
|
||||||
Type=Application
|
|
||||||
Name=praktiKST
|
|
||||||
Exec=praktiKST
|
|
||||||
Icon=praktiKST
|
|
||||||
Categories=Network;HamRadio;
|
|
||||||
Terminal=false
|
|
||||||
EOF
|
|
||||||
|
|
||||||
if [ -f target/praktiKST.AppDir/lib/praktiKST.png ]; then
|
|
||||||
cp target/praktiKST.AppDir/lib/praktiKST.png target/praktiKST.AppDir/praktiKST.png
|
|
||||||
fi
|
|
||||||
|
|
||||||
- name: Build AppImage
|
|
||||||
run: |
|
|
||||||
wget -q -O target/appimagetool.AppImage https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage
|
|
||||||
chmod +x target/appimagetool.AppImage
|
|
||||||
APPIMAGE_EXTRACT_AND_RUN=1 ARCH=x86_64 target/appimagetool.AppImage target/praktiKST.AppDir "dist/${ASSET_BASENAME}-linux-x86_64.AppImage"
|
|
||||||
|
|
||||||
- name: Upload Linux artifact
|
|
||||||
uses: actions/upload-artifact@v4.3.4
|
|
||||||
with:
|
|
||||||
name: linux-appimage
|
|
||||||
path: dist/praktiKST-*-linux-x86_64.AppImage
|
|
||||||
retention-days: 14
|
|
||||||
@@ -1,31 +0,0 @@
|
|||||||
name: PR Compile Check
|
|
||||||
|
|
||||||
on:
|
|
||||||
pull_request:
|
|
||||||
branches:
|
|
||||||
- main
|
|
||||||
workflow_dispatch:
|
|
||||||
|
|
||||||
env:
|
|
||||||
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
|
|
||||||
|
|
||||||
jobs:
|
|
||||||
compile:
|
|
||||||
name: Compile (Java 17)
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Set up Java 17
|
|
||||||
uses: actions/setup-java@v4.1.0
|
|
||||||
with:
|
|
||||||
distribution: temurin
|
|
||||||
java-version: "17"
|
|
||||||
|
|
||||||
- name: Ensure mvnw is executable
|
|
||||||
run: chmod +x mvnw
|
|
||||||
|
|
||||||
- name: Compile
|
|
||||||
run: ./mvnw -B -DskipTests compile
|
|
||||||
@@ -1,256 +0,0 @@
|
|||||||
name: Tagged Release Build
|
|
||||||
|
|
||||||
on:
|
|
||||||
push:
|
|
||||||
tags:
|
|
||||||
- "*"
|
|
||||||
workflow_dispatch:
|
|
||||||
|
|
||||||
permissions:
|
|
||||||
contents: write
|
|
||||||
|
|
||||||
env:
|
|
||||||
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
|
|
||||||
|
|
||||||
jobs:
|
|
||||||
build-windows-zip:
|
|
||||||
name: Build Windows ZIP
|
|
||||||
runs-on: windows-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Set up Java 17
|
|
||||||
uses: actions/setup-java@v4.1.0
|
|
||||||
with:
|
|
||||||
distribution: temurin
|
|
||||||
java-version: "17"
|
|
||||||
|
|
||||||
- name: Install WiX Toolset
|
|
||||||
shell: pwsh
|
|
||||||
run: choco install wixtoolset --no-progress -y
|
|
||||||
|
|
||||||
- name: Build JAR and copy runtime dependencies
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
.\mvnw.cmd -B -DskipTests package dependency:copy-dependencies -DincludeScope=runtime -DoutputDirectory=target/dist-libs
|
|
||||||
$jar = Get-ChildItem -Path target -Filter 'praktiKST-*.jar' | Sort-Object LastWriteTime -Descending | Select-Object -First 1
|
|
||||||
if (-not $jar) {
|
|
||||||
throw "No project JAR produced"
|
|
||||||
}
|
|
||||||
Copy-Item $jar.FullName target/dist-libs/app.jar
|
|
||||||
|
|
||||||
- name: Build app-image with jpackage
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
New-Item -ItemType Directory -Force -Path dist | Out-Null
|
|
||||||
jpackage --type app-image --name praktiKST --input target/dist-libs --main-jar app.jar --main-class kst4contest.view.Kst4ContestApplication --module-path target/dist-libs --add-modules javafx.controls,javafx.graphics,javafx.fxml,javafx.web,javafx.media,java.sql --dest dist
|
|
||||||
|
|
||||||
- name: Create Windows ZIP
|
|
||||||
shell: pwsh
|
|
||||||
run: |
|
|
||||||
if (-not (Test-Path dist/praktiKST)) {
|
|
||||||
throw "No Windows app-image produced by jpackage"
|
|
||||||
}
|
|
||||||
Compress-Archive -Path dist/praktiKST -DestinationPath dist/praktiKST-${{ github.ref_name }}-windows-x64.zip -Force
|
|
||||||
|
|
||||||
- name: Upload Windows artifact
|
|
||||||
uses: actions/upload-artifact@v4.3.4
|
|
||||||
with:
|
|
||||||
name: windows-zip
|
|
||||||
path: dist/praktiKST-${{ github.ref_name }}-windows-x64.zip
|
|
||||||
|
|
||||||
build-linux-appimage:
|
|
||||||
name: Build Linux AppImage
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Set up Java 17
|
|
||||||
uses: actions/setup-java@v4.1.0
|
|
||||||
with:
|
|
||||||
distribution: temurin
|
|
||||||
java-version: "17"
|
|
||||||
|
|
||||||
- name: Ensure mvnw is executable
|
|
||||||
run: chmod +x mvnw
|
|
||||||
|
|
||||||
- name: Build JAR and copy runtime dependencies
|
|
||||||
run: |
|
|
||||||
./mvnw -B -DskipTests package dependency:copy-dependencies -DincludeScope=runtime -DoutputDirectory=target/dist-libs
|
|
||||||
cp "$(ls -t target/praktiKST-*.jar | head -n 1)" target/dist-libs/app.jar
|
|
||||||
|
|
||||||
- name: Build app-image with jpackage
|
|
||||||
run: |
|
|
||||||
mkdir -p dist
|
|
||||||
jpackage \
|
|
||||||
--type app-image \
|
|
||||||
--name praktiKST \
|
|
||||||
--input target/dist-libs \
|
|
||||||
--main-jar app.jar \
|
|
||||||
--main-class kst4contest.view.Kst4ContestApplication \
|
|
||||||
--module-path target/dist-libs \
|
|
||||||
--add-modules javafx.controls,javafx.graphics,javafx.fxml,javafx.web,javafx.media,java.sql \
|
|
||||||
--dest dist
|
|
||||||
|
|
||||||
- name: Create AppDir metadata
|
|
||||||
run: |
|
|
||||||
rm -rf target/praktiKST.AppDir
|
|
||||||
cp -a dist/praktiKST target/praktiKST.AppDir
|
|
||||||
|
|
||||||
cat > target/praktiKST.AppDir/AppRun << 'EOF'
|
|
||||||
#!/bin/sh
|
|
||||||
HERE="$(dirname "$(readlink -f "$0")")"
|
|
||||||
exec "$HERE/bin/praktiKST" "$@"
|
|
||||||
EOF
|
|
||||||
chmod +x target/praktiKST.AppDir/AppRun
|
|
||||||
|
|
||||||
cat > target/praktiKST.AppDir/praktiKST.desktop << 'EOF'
|
|
||||||
[Desktop Entry]
|
|
||||||
Type=Application
|
|
||||||
Name=praktiKST
|
|
||||||
Exec=praktiKST
|
|
||||||
Icon=praktiKST
|
|
||||||
Categories=Network;HamRadio;
|
|
||||||
Terminal=false
|
|
||||||
EOF
|
|
||||||
|
|
||||||
if [ -f target/praktiKST.AppDir/lib/praktiKST.png ]; then
|
|
||||||
cp target/praktiKST.AppDir/lib/praktiKST.png target/praktiKST.AppDir/praktiKST.png
|
|
||||||
fi
|
|
||||||
|
|
||||||
- name: Build AppImage
|
|
||||||
run: |
|
|
||||||
wget -q -O target/appimagetool.AppImage https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage
|
|
||||||
chmod +x target/appimagetool.AppImage
|
|
||||||
APPIMAGE_EXTRACT_AND_RUN=1 ARCH=x86_64 target/appimagetool.AppImage target/praktiKST.AppDir dist/praktiKST-${{ github.ref_name }}-linux-x86_64.AppImage
|
|
||||||
|
|
||||||
- name: Upload Linux artifact
|
|
||||||
uses: actions/upload-artifact@v4.3.4
|
|
||||||
with:
|
|
||||||
name: linux-appimage
|
|
||||||
path: dist/praktiKST-${{ github.ref_name }}-linux-x86_64.AppImage
|
|
||||||
|
|
||||||
build-docs-pdf:
|
|
||||||
name: Build Documentation PDF
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Checkout
|
|
||||||
uses: actions/checkout@v4.1.7
|
|
||||||
|
|
||||||
- name: Install pandoc and LaTeX toolchain
|
|
||||||
run: |
|
|
||||||
sudo apt-get update -qq
|
|
||||||
sudo apt-get install -y --no-install-recommends \
|
|
||||||
pandoc \
|
|
||||||
texlive-xetex \
|
|
||||||
texlive-fonts-recommended \
|
|
||||||
texlive-latex-extra \
|
|
||||||
texlive-plain-generic
|
|
||||||
|
|
||||||
- name: Build English PDF manual
|
|
||||||
run: |
|
|
||||||
mkdir -p dist
|
|
||||||
pandoc \
|
|
||||||
--from=markdown-yaml_metadata_block \
|
|
||||||
--template=.github/latex-manual/manual-template.tex \
|
|
||||||
--pdf-engine=xelatex \
|
|
||||||
--lua-filter=.github/latex-manual/strip-wiki-links.lua \
|
|
||||||
--resource-path=.:github_docs \
|
|
||||||
--listings \
|
|
||||||
--toc \
|
|
||||||
--toc-depth=3 \
|
|
||||||
-V title="User Manual" \
|
|
||||||
-V polyglossia-lang=english \
|
|
||||||
-V version="${{ github.ref_name }}" \
|
|
||||||
-o dist/KST4Contest-${{ github.ref_name }}-manual-en.pdf \
|
|
||||||
github_docs/en-Home.md \
|
|
||||||
github_docs/en-Installation.md \
|
|
||||||
github_docs/en-Configuration.md \
|
|
||||||
github_docs/en-Features.md \
|
|
||||||
github_docs/en-User-Interface.md \
|
|
||||||
github_docs/en-Macros-and-Variables.md \
|
|
||||||
github_docs/en-Log-Sync.md \
|
|
||||||
github_docs/en-AirScout-Integration.md \
|
|
||||||
github_docs/en-DX-Cluster-Server.md \
|
|
||||||
github_docs/en-Changelog.md
|
|
||||||
|
|
||||||
- name: Build German PDF manual
|
|
||||||
run: |
|
|
||||||
pandoc \
|
|
||||||
--from=markdown-yaml_metadata_block \
|
|
||||||
--template=.github/latex-manual/manual-template.tex \
|
|
||||||
--pdf-engine=xelatex \
|
|
||||||
--lua-filter=.github/latex-manual/strip-wiki-links.lua \
|
|
||||||
--resource-path=.:github_docs \
|
|
||||||
--listings \
|
|
||||||
--toc \
|
|
||||||
--toc-depth=3 \
|
|
||||||
-V title="Benutzerhandbuch" \
|
|
||||||
-V polyglossia-lang=german \
|
|
||||||
-V version="${{ github.ref_name }}" \
|
|
||||||
-o dist/KST4Contest-${{ github.ref_name }}-manual-de.pdf \
|
|
||||||
github_docs/de-Home.md \
|
|
||||||
github_docs/de-Installation.md \
|
|
||||||
github_docs/de-Konfiguration.md \
|
|
||||||
github_docs/de-Funktionen.md \
|
|
||||||
github_docs/de-Benutzeroberflaeche.md \
|
|
||||||
github_docs/de-Makros-und-Variablen.md \
|
|
||||||
github_docs/de-Log-Synchronisation.md \
|
|
||||||
github_docs/de-AirScout-Integration.md \
|
|
||||||
github_docs/de-DX-Cluster-Server.md \
|
|
||||||
github_docs/de-Changelog.md
|
|
||||||
|
|
||||||
- name: Upload PDF artifacts
|
|
||||||
uses: actions/upload-artifact@v4.3.4
|
|
||||||
with:
|
|
||||||
name: docs-pdf
|
|
||||||
path: dist/KST4Contest-${{ github.ref_name }}-manual-*.pdf
|
|
||||||
|
|
||||||
release-tag:
|
|
||||||
name: Publish Tagged Release
|
|
||||||
runs-on: ubuntu-latest
|
|
||||||
needs:
|
|
||||||
- build-windows-zip
|
|
||||||
- build-linux-appimage
|
|
||||||
- build-docs-pdf
|
|
||||||
|
|
||||||
steps:
|
|
||||||
- name: Download Windows artifact
|
|
||||||
uses: actions/download-artifact@v4.1.3
|
|
||||||
with:
|
|
||||||
name: windows-zip
|
|
||||||
path: release-assets/windows
|
|
||||||
|
|
||||||
- name: Download Linux artifact
|
|
||||||
uses: actions/download-artifact@v4.1.3
|
|
||||||
with:
|
|
||||||
name: linux-appimage
|
|
||||||
path: release-assets/linux
|
|
||||||
|
|
||||||
- name: Download PDF manuals
|
|
||||||
uses: actions/download-artifact@v4.1.3
|
|
||||||
with:
|
|
||||||
name: docs-pdf
|
|
||||||
path: release-assets/docs
|
|
||||||
|
|
||||||
- name: Create tagged release
|
|
||||||
uses: ncipollo/release-action@v1
|
|
||||||
with:
|
|
||||||
token: ${{ secrets.GITHUB_TOKEN }}
|
|
||||||
tag: ${{ github.ref_name }}
|
|
||||||
name: ${{ startsWith(github.ref_name, 'beta-') && format('Beta {0}', github.ref_name) || format('Release {0}', github.ref_name) }}
|
|
||||||
prerelease: ${{ startsWith(github.ref_name, 'beta-') }}
|
|
||||||
allowUpdates: false
|
|
||||||
replacesArtifacts: false
|
|
||||||
makeLatest: ${{ !startsWith(github.ref_name, 'beta-') }}
|
|
||||||
generateReleaseNotes: true
|
|
||||||
artifacts: >-
|
|
||||||
release-assets/windows/praktiKST-${{ github.ref_name }}-windows-x64.zip,
|
|
||||||
release-assets/linux/praktiKST-${{ github.ref_name }}-linux-x86_64.AppImage,
|
|
||||||
release-assets/docs/KST4Contest-${{ github.ref_name }}-manual-en.pdf,
|
|
||||||
release-assets/docs/KST4Contest-${{ github.ref_name }}-manual-de.pdf
|
|
||||||
-37
@@ -1,37 +0,0 @@
|
|||||||
# Fleet IDE
|
|
||||||
.fleet
|
|
||||||
|
|
||||||
# Intellij
|
|
||||||
.idea
|
|
||||||
*.iml
|
|
||||||
|
|
||||||
# Eclipse
|
|
||||||
.project
|
|
||||||
.classpath
|
|
||||||
|
|
||||||
# Maven
|
|
||||||
target
|
|
||||||
|
|
||||||
|
|
||||||
debug.out
|
|
||||||
.DS_Store
|
|
||||||
|
|
||||||
#Logfiles
|
|
||||||
SimpleLogFile.txt
|
|
||||||
udpReaderBackup.txt
|
|
||||||
|
|
||||||
#tempfiles
|
|
||||||
.idea/
|
|
||||||
out/
|
|
||||||
|
|
||||||
#targetfiles - mvn wrapper
|
|
||||||
target/
|
|
||||||
|
|
||||||
#builds
|
|
||||||
build/
|
|
||||||
|
|
||||||
#pdf output directory
|
|
||||||
dist/
|
|
||||||
|
|
||||||
#zip files for local backups
|
|
||||||
*.zip
|
|
||||||
Vendored
BIN
Binary file not shown.
-18
@@ -1,18 +0,0 @@
|
|||||||
# Licensed to the Apache Software Foundation (ASF) under one
|
|
||||||
# or more contributor license agreements. See the NOTICE file
|
|
||||||
# distributed with this work for additional information
|
|
||||||
# regarding copyright ownership. The ASF licenses this file
|
|
||||||
# to you under the Apache License, Version 2.0 (the
|
|
||||||
# "License"); you may not use this file except in compliance
|
|
||||||
# with the License. You may obtain a copy of the License at
|
|
||||||
#
|
|
||||||
# http://www.apache.org/licenses/LICENSE-2.0
|
|
||||||
#
|
|
||||||
# Unless required by applicable law or agreed to in writing,
|
|
||||||
# software distributed under the License is distributed on an
|
|
||||||
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
||||||
# KIND, either express or implied. See the License for the
|
|
||||||
# specific language governing permissions and limitations
|
|
||||||
# under the License.
|
|
||||||
distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.2/apache-maven-3.9.2-bin.zip
|
|
||||||
wrapperUrl=https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.2.0/maven-wrapper-3.2.0.jar
|
|
||||||
@@ -1,674 +0,0 @@
|
|||||||
GNU GENERAL PUBLIC LICENSE
|
|
||||||
Version 3, 29 June 2007
|
|
||||||
|
|
||||||
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
|
|
||||||
Everyone is permitted to copy and distribute verbatim copies
|
|
||||||
of this license document, but changing it is not allowed.
|
|
||||||
|
|
||||||
Preamble
|
|
||||||
|
|
||||||
The GNU General Public License is a free, copyleft license for
|
|
||||||
software and other kinds of works.
|
|
||||||
|
|
||||||
The licenses for most software and other practical works are designed
|
|
||||||
to take away your freedom to share and change the works. By contrast,
|
|
||||||
the GNU General Public License is intended to guarantee your freedom to
|
|
||||||
share and change all versions of a program--to make sure it remains free
|
|
||||||
software for all its users. We, the Free Software Foundation, use the
|
|
||||||
GNU General Public License for most of our software; it applies also to
|
|
||||||
any other work released this way by its authors. You can apply it to
|
|
||||||
your programs, too.
|
|
||||||
|
|
||||||
When we speak of free software, we are referring to freedom, not
|
|
||||||
price. Our General Public Licenses are designed to make sure that you
|
|
||||||
have the freedom to distribute copies of free software (and charge for
|
|
||||||
them if you wish), that you receive source code or can get it if you
|
|
||||||
want it, that you can change the software or use pieces of it in new
|
|
||||||
free programs, and that you know you can do these things.
|
|
||||||
|
|
||||||
To protect your rights, we need to prevent others from denying you
|
|
||||||
these rights or asking you to surrender the rights. Therefore, you have
|
|
||||||
certain responsibilities if you distribute copies of the software, or if
|
|
||||||
you modify it: responsibilities to respect the freedom of others.
|
|
||||||
|
|
||||||
For example, if you distribute copies of such a program, whether
|
|
||||||
gratis or for a fee, you must pass on to the recipients the same
|
|
||||||
freedoms that you received. You must make sure that they, too, receive
|
|
||||||
or can get the source code. And you must show them these terms so they
|
|
||||||
know their rights.
|
|
||||||
|
|
||||||
Developers that use the GNU GPL protect your rights with two steps:
|
|
||||||
(1) assert copyright on the software, and (2) offer you this License
|
|
||||||
giving you legal permission to copy, distribute and/or modify it.
|
|
||||||
|
|
||||||
For the developers' and authors' protection, the GPL clearly explains
|
|
||||||
that there is no warranty for this free software. For both users' and
|
|
||||||
authors' sake, the GPL requires that modified versions be marked as
|
|
||||||
changed, so that their problems will not be attributed erroneously to
|
|
||||||
authors of previous versions.
|
|
||||||
|
|
||||||
Some devices are designed to deny users access to install or run
|
|
||||||
modified versions of the software inside them, although the manufacturer
|
|
||||||
can do so. This is fundamentally incompatible with the aim of
|
|
||||||
protecting users' freedom to change the software. The systematic
|
|
||||||
pattern of such abuse occurs in the area of products for individuals to
|
|
||||||
use, which is precisely where it is most unacceptable. Therefore, we
|
|
||||||
have designed this version of the GPL to prohibit the practice for those
|
|
||||||
products. If such problems arise substantially in other domains, we
|
|
||||||
stand ready to extend this provision to those domains in future versions
|
|
||||||
of the GPL, as needed to protect the freedom of users.
|
|
||||||
|
|
||||||
Finally, every program is threatened constantly by software patents.
|
|
||||||
States should not allow patents to restrict development and use of
|
|
||||||
software on general-purpose computers, but in those that do, we wish to
|
|
||||||
avoid the special danger that patents applied to a free program could
|
|
||||||
make it effectively proprietary. To prevent this, the GPL assures that
|
|
||||||
patents cannot be used to render the program non-free.
|
|
||||||
|
|
||||||
The precise terms and conditions for copying, distribution and
|
|
||||||
modification follow.
|
|
||||||
|
|
||||||
TERMS AND CONDITIONS
|
|
||||||
|
|
||||||
0. Definitions.
|
|
||||||
|
|
||||||
"This License" refers to version 3 of the GNU General Public License.
|
|
||||||
|
|
||||||
"Copyright" also means copyright-like laws that apply to other kinds of
|
|
||||||
works, such as semiconductor masks.
|
|
||||||
|
|
||||||
"The Program" refers to any copyrightable work licensed under this
|
|
||||||
License. Each licensee is addressed as "you". "Licensees" and
|
|
||||||
"recipients" may be individuals or organizations.
|
|
||||||
|
|
||||||
To "modify" a work means to copy from or adapt all or part of the work
|
|
||||||
in a fashion requiring copyright permission, other than the making of an
|
|
||||||
exact copy. The resulting work is called a "modified version" of the
|
|
||||||
earlier work or a work "based on" the earlier work.
|
|
||||||
|
|
||||||
A "covered work" means either the unmodified Program or a work based
|
|
||||||
on the Program.
|
|
||||||
|
|
||||||
To "propagate" a work means to do anything with it that, without
|
|
||||||
permission, would make you directly or secondarily liable for
|
|
||||||
infringement under applicable copyright law, except executing it on a
|
|
||||||
computer or modifying a private copy. Propagation includes copying,
|
|
||||||
distribution (with or without modification), making available to the
|
|
||||||
public, and in some countries other activities as well.
|
|
||||||
|
|
||||||
To "convey" a work means any kind of propagation that enables other
|
|
||||||
parties to make or receive copies. Mere interaction with a user through
|
|
||||||
a computer network, with no transfer of a copy, is not conveying.
|
|
||||||
|
|
||||||
An interactive user interface displays "Appropriate Legal Notices"
|
|
||||||
to the extent that it includes a convenient and prominently visible
|
|
||||||
feature that (1) displays an appropriate copyright notice, and (2)
|
|
||||||
tells the user that there is no warranty for the work (except to the
|
|
||||||
extent that warranties are provided), that licensees may convey the
|
|
||||||
work under this License, and how to view a copy of this License. If
|
|
||||||
the interface presents a list of user commands or options, such as a
|
|
||||||
menu, a prominent item in the list meets this criterion.
|
|
||||||
|
|
||||||
1. Source Code.
|
|
||||||
|
|
||||||
The "source code" for a work means the preferred form of the work
|
|
||||||
for making modifications to it. "Object code" means any non-source
|
|
||||||
form of a work.
|
|
||||||
|
|
||||||
A "Standard Interface" means an interface that either is an official
|
|
||||||
standard defined by a recognized standards body, or, in the case of
|
|
||||||
interfaces specified for a particular programming language, one that
|
|
||||||
is widely used among developers working in that language.
|
|
||||||
|
|
||||||
The "System Libraries" of an executable work include anything, other
|
|
||||||
than the work as a whole, that (a) is included in the normal form of
|
|
||||||
packaging a Major Component, but which is not part of that Major
|
|
||||||
Component, and (b) serves only to enable use of the work with that
|
|
||||||
Major Component, or to implement a Standard Interface for which an
|
|
||||||
implementation is available to the public in source code form. A
|
|
||||||
"Major Component", in this context, means a major essential component
|
|
||||||
(kernel, window system, and so on) of the specific operating system
|
|
||||||
(if any) on which the executable work runs, or a compiler used to
|
|
||||||
produce the work, or an object code interpreter used to run it.
|
|
||||||
|
|
||||||
The "Corresponding Source" for a work in object code form means all
|
|
||||||
the source code needed to generate, install, and (for an executable
|
|
||||||
work) run the object code and to modify the work, including scripts to
|
|
||||||
control those activities. However, it does not include the work's
|
|
||||||
System Libraries, or general-purpose tools or generally available free
|
|
||||||
programs which are used unmodified in performing those activities but
|
|
||||||
which are not part of the work. For example, Corresponding Source
|
|
||||||
includes interface definition files associated with source files for
|
|
||||||
the work, and the source code for shared libraries and dynamically
|
|
||||||
linked subprograms that the work is specifically designed to require,
|
|
||||||
such as by intimate data communication or control flow between those
|
|
||||||
subprograms and other parts of the work.
|
|
||||||
|
|
||||||
The Corresponding Source need not include anything that users
|
|
||||||
can regenerate automatically from other parts of the Corresponding
|
|
||||||
Source.
|
|
||||||
|
|
||||||
The Corresponding Source for a work in source code form is that
|
|
||||||
same work.
|
|
||||||
|
|
||||||
2. Basic Permissions.
|
|
||||||
|
|
||||||
All rights granted under this License are granted for the term of
|
|
||||||
copyright on the Program, and are irrevocable provided the stated
|
|
||||||
conditions are met. This License explicitly affirms your unlimited
|
|
||||||
permission to run the unmodified Program. The output from running a
|
|
||||||
covered work is covered by this License only if the output, given its
|
|
||||||
content, constitutes a covered work. This License acknowledges your
|
|
||||||
rights of fair use or other equivalent, as provided by copyright law.
|
|
||||||
|
|
||||||
You may make, run and propagate covered works that you do not
|
|
||||||
convey, without conditions so long as your license otherwise remains
|
|
||||||
in force. You may convey covered works to others for the sole purpose
|
|
||||||
of having them make modifications exclusively for you, or provide you
|
|
||||||
with facilities for running those works, provided that you comply with
|
|
||||||
the terms of this License in conveying all material for which you do
|
|
||||||
not control copyright. Those thus making or running the covered works
|
|
||||||
for you must do so exclusively on your behalf, under your direction
|
|
||||||
and control, on terms that prohibit them from making any copies of
|
|
||||||
your copyrighted material outside their relationship with you.
|
|
||||||
|
|
||||||
Conveying under any other circumstances is permitted solely under
|
|
||||||
the conditions stated below. Sublicensing is not allowed; section 10
|
|
||||||
makes it unnecessary.
|
|
||||||
|
|
||||||
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
|
|
||||||
|
|
||||||
No covered work shall be deemed part of an effective technological
|
|
||||||
measure under any applicable law fulfilling obligations under article
|
|
||||||
11 of the WIPO copyright treaty adopted on 20 December 1996, or
|
|
||||||
similar laws prohibiting or restricting circumvention of such
|
|
||||||
measures.
|
|
||||||
|
|
||||||
When you convey a covered work, you waive any legal power to forbid
|
|
||||||
circumvention of technological measures to the extent such circumvention
|
|
||||||
is effected by exercising rights under this License with respect to
|
|
||||||
the covered work, and you disclaim any intention to limit operation or
|
|
||||||
modification of the work as a means of enforcing, against the work's
|
|
||||||
users, your or third parties' legal rights to forbid circumvention of
|
|
||||||
technological measures.
|
|
||||||
|
|
||||||
4. Conveying Verbatim Copies.
|
|
||||||
|
|
||||||
You may convey verbatim copies of the Program's source code as you
|
|
||||||
receive it, in any medium, provided that you conspicuously and
|
|
||||||
appropriately publish on each copy an appropriate copyright notice;
|
|
||||||
keep intact all notices stating that this License and any
|
|
||||||
non-permissive terms added in accord with section 7 apply to the code;
|
|
||||||
keep intact all notices of the absence of any warranty; and give all
|
|
||||||
recipients a copy of this License along with the Program.
|
|
||||||
|
|
||||||
You may charge any price or no price for each copy that you convey,
|
|
||||||
and you may offer support or warranty protection for a fee.
|
|
||||||
|
|
||||||
5. Conveying Modified Source Versions.
|
|
||||||
|
|
||||||
You may convey a work based on the Program, or the modifications to
|
|
||||||
produce it from the Program, in the form of source code under the
|
|
||||||
terms of section 4, provided that you also meet all of these conditions:
|
|
||||||
|
|
||||||
a) The work must carry prominent notices stating that you modified
|
|
||||||
it, and giving a relevant date.
|
|
||||||
|
|
||||||
b) The work must carry prominent notices stating that it is
|
|
||||||
released under this License and any conditions added under section
|
|
||||||
7. This requirement modifies the requirement in section 4 to
|
|
||||||
"keep intact all notices".
|
|
||||||
|
|
||||||
c) You must license the entire work, as a whole, under this
|
|
||||||
License to anyone who comes into possession of a copy. This
|
|
||||||
License will therefore apply, along with any applicable section 7
|
|
||||||
additional terms, to the whole of the work, and all its parts,
|
|
||||||
regardless of how they are packaged. This License gives no
|
|
||||||
permission to license the work in any other way, but it does not
|
|
||||||
invalidate such permission if you have separately received it.
|
|
||||||
|
|
||||||
d) If the work has interactive user interfaces, each must display
|
|
||||||
Appropriate Legal Notices; however, if the Program has interactive
|
|
||||||
interfaces that do not display Appropriate Legal Notices, your
|
|
||||||
work need not make them do so.
|
|
||||||
|
|
||||||
A compilation of a covered work with other separate and independent
|
|
||||||
works, which are not by their nature extensions of the covered work,
|
|
||||||
and which are not combined with it such as to form a larger program,
|
|
||||||
in or on a volume of a storage or distribution medium, is called an
|
|
||||||
"aggregate" if the compilation and its resulting copyright are not
|
|
||||||
used to limit the access or legal rights of the compilation's users
|
|
||||||
beyond what the individual works permit. Inclusion of a covered work
|
|
||||||
in an aggregate does not cause this License to apply to the other
|
|
||||||
parts of the aggregate.
|
|
||||||
|
|
||||||
6. Conveying Non-Source Forms.
|
|
||||||
|
|
||||||
You may convey a covered work in object code form under the terms
|
|
||||||
of sections 4 and 5, provided that you also convey the
|
|
||||||
machine-readable Corresponding Source under the terms of this License,
|
|
||||||
in one of these ways:
|
|
||||||
|
|
||||||
a) Convey the object code in, or embodied in, a physical product
|
|
||||||
(including a physical distribution medium), accompanied by the
|
|
||||||
Corresponding Source fixed on a durable physical medium
|
|
||||||
customarily used for software interchange.
|
|
||||||
|
|
||||||
b) Convey the object code in, or embodied in, a physical product
|
|
||||||
(including a physical distribution medium), accompanied by a
|
|
||||||
written offer, valid for at least three years and valid for as
|
|
||||||
long as you offer spare parts or customer support for that product
|
|
||||||
model, to give anyone who possesses the object code either (1) a
|
|
||||||
copy of the Corresponding Source for all the software in the
|
|
||||||
product that is covered by this License, on a durable physical
|
|
||||||
medium customarily used for software interchange, for a price no
|
|
||||||
more than your reasonable cost of physically performing this
|
|
||||||
conveying of source, or (2) access to copy the
|
|
||||||
Corresponding Source from a network server at no charge.
|
|
||||||
|
|
||||||
c) Convey individual copies of the object code with a copy of the
|
|
||||||
written offer to provide the Corresponding Source. This
|
|
||||||
alternative is allowed only occasionally and noncommercially, and
|
|
||||||
only if you received the object code with such an offer, in accord
|
|
||||||
with subsection 6b.
|
|
||||||
|
|
||||||
d) Convey the object code by offering access from a designated
|
|
||||||
place (gratis or for a charge), and offer equivalent access to the
|
|
||||||
Corresponding Source in the same way through the same place at no
|
|
||||||
further charge. You need not require recipients to copy the
|
|
||||||
Corresponding Source along with the object code. If the place to
|
|
||||||
copy the object code is a network server, the Corresponding Source
|
|
||||||
may be on a different server (operated by you or a third party)
|
|
||||||
that supports equivalent copying facilities, provided you maintain
|
|
||||||
clear directions next to the object code saying where to find the
|
|
||||||
Corresponding Source. Regardless of what server hosts the
|
|
||||||
Corresponding Source, you remain obligated to ensure that it is
|
|
||||||
available for as long as needed to satisfy these requirements.
|
|
||||||
|
|
||||||
e) Convey the object code using peer-to-peer transmission, provided
|
|
||||||
you inform other peers where the object code and Corresponding
|
|
||||||
Source of the work are being offered to the general public at no
|
|
||||||
charge under subsection 6d.
|
|
||||||
|
|
||||||
A separable portion of the object code, whose source code is excluded
|
|
||||||
from the Corresponding Source as a System Library, need not be
|
|
||||||
included in conveying the object code work.
|
|
||||||
|
|
||||||
A "User Product" is either (1) a "consumer product", which means any
|
|
||||||
tangible personal property which is normally used for personal, family,
|
|
||||||
or household purposes, or (2) anything designed or sold for incorporation
|
|
||||||
into a dwelling. In determining whether a product is a consumer product,
|
|
||||||
doubtful cases shall be resolved in favor of coverage. For a particular
|
|
||||||
product received by a particular user, "normally used" refers to a
|
|
||||||
typical or common use of that class of product, regardless of the status
|
|
||||||
of the particular user or of the way in which the particular user
|
|
||||||
actually uses, or expects or is expected to use, the product. A product
|
|
||||||
is a consumer product regardless of whether the product has substantial
|
|
||||||
commercial, industrial or non-consumer uses, unless such uses represent
|
|
||||||
the only significant mode of use of the product.
|
|
||||||
|
|
||||||
"Installation Information" for a User Product means any methods,
|
|
||||||
procedures, authorization keys, or other information required to install
|
|
||||||
and execute modified versions of a covered work in that User Product from
|
|
||||||
a modified version of its Corresponding Source. The information must
|
|
||||||
suffice to ensure that the continued functioning of the modified object
|
|
||||||
code is in no case prevented or interfered with solely because
|
|
||||||
modification has been made.
|
|
||||||
|
|
||||||
If you convey an object code work under this section in, or with, or
|
|
||||||
specifically for use in, a User Product, and the conveying occurs as
|
|
||||||
part of a transaction in which the right of possession and use of the
|
|
||||||
User Product is transferred to the recipient in perpetuity or for a
|
|
||||||
fixed term (regardless of how the transaction is characterized), the
|
|
||||||
Corresponding Source conveyed under this section must be accompanied
|
|
||||||
by the Installation Information. But this requirement does not apply
|
|
||||||
if neither you nor any third party retains the ability to install
|
|
||||||
modified object code on the User Product (for example, the work has
|
|
||||||
been installed in ROM).
|
|
||||||
|
|
||||||
The requirement to provide Installation Information does not include a
|
|
||||||
requirement to continue to provide support service, warranty, or updates
|
|
||||||
for a work that has been modified or installed by the recipient, or for
|
|
||||||
the User Product in which it has been modified or installed. Access to a
|
|
||||||
network may be denied when the modification itself materially and
|
|
||||||
adversely affects the operation of the network or violates the rules and
|
|
||||||
protocols for communication across the network.
|
|
||||||
|
|
||||||
Corresponding Source conveyed, and Installation Information provided,
|
|
||||||
in accord with this section must be in a format that is publicly
|
|
||||||
documented (and with an implementation available to the public in
|
|
||||||
source code form), and must require no special password or key for
|
|
||||||
unpacking, reading or copying.
|
|
||||||
|
|
||||||
7. Additional Terms.
|
|
||||||
|
|
||||||
"Additional permissions" are terms that supplement the terms of this
|
|
||||||
License by making exceptions from one or more of its conditions.
|
|
||||||
Additional permissions that are applicable to the entire Program shall
|
|
||||||
be treated as though they were included in this License, to the extent
|
|
||||||
that they are valid under applicable law. If additional permissions
|
|
||||||
apply only to part of the Program, that part may be used separately
|
|
||||||
under those permissions, but the entire Program remains governed by
|
|
||||||
this License without regard to the additional permissions.
|
|
||||||
|
|
||||||
When you convey a copy of a covered work, you may at your option
|
|
||||||
remove any additional permissions from that copy, or from any part of
|
|
||||||
it. (Additional permissions may be written to require their own
|
|
||||||
removal in certain cases when you modify the work.) You may place
|
|
||||||
additional permissions on material, added by you to a covered work,
|
|
||||||
for which you have or can give appropriate copyright permission.
|
|
||||||
|
|
||||||
Notwithstanding any other provision of this License, for material you
|
|
||||||
add to a covered work, you may (if authorized by the copyright holders of
|
|
||||||
that material) supplement the terms of this License with terms:
|
|
||||||
|
|
||||||
a) Disclaiming warranty or limiting liability differently from the
|
|
||||||
terms of sections 15 and 16 of this License; or
|
|
||||||
|
|
||||||
b) Requiring preservation of specified reasonable legal notices or
|
|
||||||
author attributions in that material or in the Appropriate Legal
|
|
||||||
Notices displayed by works containing it; or
|
|
||||||
|
|
||||||
c) Prohibiting misrepresentation of the origin of that material, or
|
|
||||||
requiring that modified versions of such material be marked in
|
|
||||||
reasonable ways as different from the original version; or
|
|
||||||
|
|
||||||
d) Limiting the use for publicity purposes of names of licensors or
|
|
||||||
authors of the material; or
|
|
||||||
|
|
||||||
e) Declining to grant rights under trademark law for use of some
|
|
||||||
trade names, trademarks, or service marks; or
|
|
||||||
|
|
||||||
f) Requiring indemnification of licensors and authors of that
|
|
||||||
material by anyone who conveys the material (or modified versions of
|
|
||||||
it) with contractual assumptions of liability to the recipient, for
|
|
||||||
any liability that these contractual assumptions directly impose on
|
|
||||||
those licensors and authors.
|
|
||||||
|
|
||||||
All other non-permissive additional terms are considered "further
|
|
||||||
restrictions" within the meaning of section 10. If the Program as you
|
|
||||||
received it, or any part of it, contains a notice stating that it is
|
|
||||||
governed by this License along with a term that is a further
|
|
||||||
restriction, you may remove that term. If a license document contains
|
|
||||||
a further restriction but permits relicensing or conveying under this
|
|
||||||
License, you may add to a covered work material governed by the terms
|
|
||||||
of that license document, provided that the further restriction does
|
|
||||||
not survive such relicensing or conveying.
|
|
||||||
|
|
||||||
If you add terms to a covered work in accord with this section, you
|
|
||||||
must place, in the relevant source files, a statement of the
|
|
||||||
additional terms that apply to those files, or a notice indicating
|
|
||||||
where to find the applicable terms.
|
|
||||||
|
|
||||||
Additional terms, permissive or non-permissive, may be stated in the
|
|
||||||
form of a separately written license, or stated as exceptions;
|
|
||||||
the above requirements apply either way.
|
|
||||||
|
|
||||||
8. Termination.
|
|
||||||
|
|
||||||
You may not propagate or modify a covered work except as expressly
|
|
||||||
provided under this License. Any attempt otherwise to propagate or
|
|
||||||
modify it is void, and will automatically terminate your rights under
|
|
||||||
this License (including any patent licenses granted under the third
|
|
||||||
paragraph of section 11).
|
|
||||||
|
|
||||||
However, if you cease all violation of this License, then your
|
|
||||||
license from a particular copyright holder is reinstated (a)
|
|
||||||
provisionally, unless and until the copyright holder explicitly and
|
|
||||||
finally terminates your license, and (b) permanently, if the copyright
|
|
||||||
holder fails to notify you of the violation by some reasonable means
|
|
||||||
prior to 60 days after the cessation.
|
|
||||||
|
|
||||||
Moreover, your license from a particular copyright holder is
|
|
||||||
reinstated permanently if the copyright holder notifies you of the
|
|
||||||
violation by some reasonable means, this is the first time you have
|
|
||||||
received notice of violation of this License (for any work) from that
|
|
||||||
copyright holder, and you cure the violation prior to 30 days after
|
|
||||||
your receipt of the notice.
|
|
||||||
|
|
||||||
Termination of your rights under this section does not terminate the
|
|
||||||
licenses of parties who have received copies or rights from you under
|
|
||||||
this License. If your rights have been terminated and not permanently
|
|
||||||
reinstated, you do not qualify to receive new licenses for the same
|
|
||||||
material under section 10.
|
|
||||||
|
|
||||||
9. Acceptance Not Required for Having Copies.
|
|
||||||
|
|
||||||
You are not required to accept this License in order to receive or
|
|
||||||
run a copy of the Program. Ancillary propagation of a covered work
|
|
||||||
occurring solely as a consequence of using peer-to-peer transmission
|
|
||||||
to receive a copy likewise does not require acceptance. However,
|
|
||||||
nothing other than this License grants you permission to propagate or
|
|
||||||
modify any covered work. These actions infringe copyright if you do
|
|
||||||
not accept this License. Therefore, by modifying or propagating a
|
|
||||||
covered work, you indicate your acceptance of this License to do so.
|
|
||||||
|
|
||||||
10. Automatic Licensing of Downstream Recipients.
|
|
||||||
|
|
||||||
Each time you convey a covered work, the recipient automatically
|
|
||||||
receives a license from the original licensors, to run, modify and
|
|
||||||
propagate that work, subject to this License. You are not responsible
|
|
||||||
for enforcing compliance by third parties with this License.
|
|
||||||
|
|
||||||
An "entity transaction" is a transaction transferring control of an
|
|
||||||
organization, or substantially all assets of one, or subdividing an
|
|
||||||
organization, or merging organizations. If propagation of a covered
|
|
||||||
work results from an entity transaction, each party to that
|
|
||||||
transaction who receives a copy of the work also receives whatever
|
|
||||||
licenses to the work the party's predecessor in interest had or could
|
|
||||||
give under the previous paragraph, plus a right to possession of the
|
|
||||||
Corresponding Source of the work from the predecessor in interest, if
|
|
||||||
the predecessor has it or can get it with reasonable efforts.
|
|
||||||
|
|
||||||
You may not impose any further restrictions on the exercise of the
|
|
||||||
rights granted or affirmed under this License. For example, you may
|
|
||||||
not impose a license fee, royalty, or other charge for exercise of
|
|
||||||
rights granted under this License, and you may not initiate litigation
|
|
||||||
(including a cross-claim or counterclaim in a lawsuit) alleging that
|
|
||||||
any patent claim is infringed by making, using, selling, offering for
|
|
||||||
sale, or importing the Program or any portion of it.
|
|
||||||
|
|
||||||
11. Patents.
|
|
||||||
|
|
||||||
A "contributor" is a copyright holder who authorizes use under this
|
|
||||||
License of the Program or a work on which the Program is based. The
|
|
||||||
work thus licensed is called the contributor's "contributor version".
|
|
||||||
|
|
||||||
A contributor's "essential patent claims" are all patent claims
|
|
||||||
owned or controlled by the contributor, whether already acquired or
|
|
||||||
hereafter acquired, that would be infringed by some manner, permitted
|
|
||||||
by this License, of making, using, or selling its contributor version,
|
|
||||||
but do not include claims that would be infringed only as a
|
|
||||||
consequence of further modification of the contributor version. For
|
|
||||||
purposes of this definition, "control" includes the right to grant
|
|
||||||
patent sublicenses in a manner consistent with the requirements of
|
|
||||||
this License.
|
|
||||||
|
|
||||||
Each contributor grants you a non-exclusive, worldwide, royalty-free
|
|
||||||
patent license under the contributor's essential patent claims, to
|
|
||||||
make, use, sell, offer for sale, import and otherwise run, modify and
|
|
||||||
propagate the contents of its contributor version.
|
|
||||||
|
|
||||||
In the following three paragraphs, a "patent license" is any express
|
|
||||||
agreement or commitment, however denominated, not to enforce a patent
|
|
||||||
(such as an express permission to practice a patent or covenant not to
|
|
||||||
sue for patent infringement). To "grant" such a patent license to a
|
|
||||||
party means to make such an agreement or commitment not to enforce a
|
|
||||||
patent against the party.
|
|
||||||
|
|
||||||
If you convey a covered work, knowingly relying on a patent license,
|
|
||||||
and the Corresponding Source of the work is not available for anyone
|
|
||||||
to copy, free of charge and under the terms of this License, through a
|
|
||||||
publicly available network server or other readily accessible means,
|
|
||||||
then you must either (1) cause the Corresponding Source to be so
|
|
||||||
available, or (2) arrange to deprive yourself of the benefit of the
|
|
||||||
patent license for this particular work, or (3) arrange, in a manner
|
|
||||||
consistent with the requirements of this License, to extend the patent
|
|
||||||
license to downstream recipients. "Knowingly relying" means you have
|
|
||||||
actual knowledge that, but for the patent license, your conveying the
|
|
||||||
covered work in a country, or your recipient's use of the covered work
|
|
||||||
in a country, would infringe one or more identifiable patents in that
|
|
||||||
country that you have reason to believe are valid.
|
|
||||||
|
|
||||||
If, pursuant to or in connection with a single transaction or
|
|
||||||
arrangement, you convey, or propagate by procuring conveyance of, a
|
|
||||||
covered work, and grant a patent license to some of the parties
|
|
||||||
receiving the covered work authorizing them to use, propagate, modify
|
|
||||||
or convey a specific copy of the covered work, then the patent license
|
|
||||||
you grant is automatically extended to all recipients of the covered
|
|
||||||
work and works based on it.
|
|
||||||
|
|
||||||
A patent license is "discriminatory" if it does not include within
|
|
||||||
the scope of its coverage, prohibits the exercise of, or is
|
|
||||||
conditioned on the non-exercise of one or more of the rights that are
|
|
||||||
specifically granted under this License. You may not convey a covered
|
|
||||||
work if you are a party to an arrangement with a third party that is
|
|
||||||
in the business of distributing software, under which you make payment
|
|
||||||
to the third party based on the extent of your activity of conveying
|
|
||||||
the work, and under which the third party grants, to any of the
|
|
||||||
parties who would receive the covered work from you, a discriminatory
|
|
||||||
patent license (a) in connection with copies of the covered work
|
|
||||||
conveyed by you (or copies made from those copies), or (b) primarily
|
|
||||||
for and in connection with specific products or compilations that
|
|
||||||
contain the covered work, unless you entered into that arrangement,
|
|
||||||
or that patent license was granted, prior to 28 March 2007.
|
|
||||||
|
|
||||||
Nothing in this License shall be construed as excluding or limiting
|
|
||||||
any implied license or other defenses to infringement that may
|
|
||||||
otherwise be available to you under applicable patent law.
|
|
||||||
|
|
||||||
12. No Surrender of Others' Freedom.
|
|
||||||
|
|
||||||
If conditions are imposed on you (whether by court order, agreement or
|
|
||||||
otherwise) that contradict the conditions of this License, they do not
|
|
||||||
excuse you from the conditions of this License. If you cannot convey a
|
|
||||||
covered work so as to satisfy simultaneously your obligations under this
|
|
||||||
License and any other pertinent obligations, then as a consequence you may
|
|
||||||
not convey it at all. For example, if you agree to terms that obligate you
|
|
||||||
to collect a royalty for further conveying from those to whom you convey
|
|
||||||
the Program, the only way you could satisfy both those terms and this
|
|
||||||
License would be to refrain entirely from conveying the Program.
|
|
||||||
|
|
||||||
13. Use with the GNU Affero General Public License.
|
|
||||||
|
|
||||||
Notwithstanding any other provision of this License, you have
|
|
||||||
permission to link or combine any covered work with a work licensed
|
|
||||||
under version 3 of the GNU Affero General Public License into a single
|
|
||||||
combined work, and to convey the resulting work. The terms of this
|
|
||||||
License will continue to apply to the part which is the covered work,
|
|
||||||
but the special requirements of the GNU Affero General Public License,
|
|
||||||
section 13, concerning interaction through a network will apply to the
|
|
||||||
combination as such.
|
|
||||||
|
|
||||||
14. Revised Versions of this License.
|
|
||||||
|
|
||||||
The Free Software Foundation may publish revised and/or new versions of
|
|
||||||
the GNU General Public License from time to time. Such new versions will
|
|
||||||
be similar in spirit to the present version, but may differ in detail to
|
|
||||||
address new problems or concerns.
|
|
||||||
|
|
||||||
Each version is given a distinguishing version number. If the
|
|
||||||
Program specifies that a certain numbered version of the GNU General
|
|
||||||
Public License "or any later version" applies to it, you have the
|
|
||||||
option of following the terms and conditions either of that numbered
|
|
||||||
version or of any later version published by the Free Software
|
|
||||||
Foundation. If the Program does not specify a version number of the
|
|
||||||
GNU General Public License, you may choose any version ever published
|
|
||||||
by the Free Software Foundation.
|
|
||||||
|
|
||||||
If the Program specifies that a proxy can decide which future
|
|
||||||
versions of the GNU General Public License can be used, that proxy's
|
|
||||||
public statement of acceptance of a version permanently authorizes you
|
|
||||||
to choose that version for the Program.
|
|
||||||
|
|
||||||
Later license versions may give you additional or different
|
|
||||||
permissions. However, no additional obligations are imposed on any
|
|
||||||
author or copyright holder as a result of your choosing to follow a
|
|
||||||
later version.
|
|
||||||
|
|
||||||
15. Disclaimer of Warranty.
|
|
||||||
|
|
||||||
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
|
|
||||||
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
|
|
||||||
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
|
|
||||||
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
|
|
||||||
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
||||||
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
|
|
||||||
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
|
|
||||||
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
|
|
||||||
|
|
||||||
16. Limitation of Liability.
|
|
||||||
|
|
||||||
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
|
|
||||||
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
|
|
||||||
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
|
|
||||||
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
|
|
||||||
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
|
|
||||||
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
|
|
||||||
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
|
|
||||||
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
|
|
||||||
SUCH DAMAGES.
|
|
||||||
|
|
||||||
17. Interpretation of Sections 15 and 16.
|
|
||||||
|
|
||||||
If the disclaimer of warranty and limitation of liability provided
|
|
||||||
above cannot be given local legal effect according to their terms,
|
|
||||||
reviewing courts shall apply local law that most closely approximates
|
|
||||||
an absolute waiver of all civil liability in connection with the
|
|
||||||
Program, unless a warranty or assumption of liability accompanies a
|
|
||||||
copy of the Program in return for a fee.
|
|
||||||
|
|
||||||
END OF TERMS AND CONDITIONS
|
|
||||||
|
|
||||||
How to Apply These Terms to Your New Programs
|
|
||||||
|
|
||||||
If you develop a new program, and you want it to be of the greatest
|
|
||||||
possible use to the public, the best way to achieve this is to make it
|
|
||||||
free software which everyone can redistribute and change under these terms.
|
|
||||||
|
|
||||||
To do so, attach the following notices to the program. It is safest
|
|
||||||
to attach them to the start of each source file to most effectively
|
|
||||||
state the exclusion of warranty; and each file should have at least
|
|
||||||
the "copyright" line and a pointer to where the full notice is found.
|
|
||||||
|
|
||||||
<one line to give the program's name and a brief idea of what it does.>
|
|
||||||
Copyright (C) <year> <name of author>
|
|
||||||
|
|
||||||
This program is free software: you can redistribute it and/or modify
|
|
||||||
it under the terms of the GNU General Public License as published by
|
|
||||||
the Free Software Foundation, either version 3 of the License, or
|
|
||||||
(at your option) any later version.
|
|
||||||
|
|
||||||
This program is distributed in the hope that it will be useful,
|
|
||||||
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
||||||
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
||||||
GNU General Public License for more details.
|
|
||||||
|
|
||||||
You should have received a copy of the GNU General Public License
|
|
||||||
along with this program. If not, see <https://www.gnu.org/licenses/>.
|
|
||||||
|
|
||||||
Also add information on how to contact you by electronic and paper mail.
|
|
||||||
|
|
||||||
If the program does terminal interaction, make it output a short
|
|
||||||
notice like this when it starts in an interactive mode:
|
|
||||||
|
|
||||||
<program> Copyright (C) <year> <name of author>
|
|
||||||
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
|
|
||||||
This is free software, and you are welcome to redistribute it
|
|
||||||
under certain conditions; type `show c' for details.
|
|
||||||
|
|
||||||
The hypothetical commands `show w' and `show c' should show the appropriate
|
|
||||||
parts of the General Public License. Of course, your program's commands
|
|
||||||
might be different; for a GUI interface, you would use an "about box".
|
|
||||||
|
|
||||||
You should also get your employer (if you work as a programmer) or school,
|
|
||||||
if any, to sign a "copyright disclaimer" for the program, if necessary.
|
|
||||||
For more information on this, and how to apply and follow the GNU GPL, see
|
|
||||||
<https://www.gnu.org/licenses/>.
|
|
||||||
|
|
||||||
The GNU General Public License does not permit incorporating your program
|
|
||||||
into proprietary programs. If your program is a subroutine library, you
|
|
||||||
may consider it more useful to permit linking proprietary applications with
|
|
||||||
the library. If this is what you want to do, use the GNU Lesser General
|
|
||||||
Public License instead of this License. But first, please read
|
|
||||||
<https://www.gnu.org/licenses/why-not-lgpl.html>.
|
|
||||||
@@ -1,38 +0,0 @@
|
|||||||
# KST4Contest
|
|
||||||
|
|
||||||
KST4Contest (also known as pratiKST) is a Java-based chat client for ON4KST, focused on VHF/UHF/SHF contest operation.
|
|
||||||
|
|
||||||
## Documentation
|
|
||||||
|
|
||||||
The full user documentation is maintained in the project wiki:
|
|
||||||
|
|
||||||
- https://github.com/praktimarc/kst4contest/wiki
|
|
||||||
|
|
||||||
Direct entry points:
|
|
||||||
|
|
||||||
- German start page: https://github.com/praktimarc/kst4contest/wiki/de-Home
|
|
||||||
- English start page: https://github.com/praktimarc/kst4contest/wiki/en-Home
|
|
||||||
|
|
||||||
## Build
|
|
||||||
|
|
||||||
Compile locally with Maven Wrapper:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
./mvnw -B -DskipTests compile
|
|
||||||
```
|
|
||||||
|
|
||||||
## Notes
|
|
||||||
|
|
||||||
- Source code is under `src/`.
|
|
||||||
- Documentation markdown pages for wiki/PDF are under `github_docs/`.
|
|
||||||
|
|
||||||
## Status of the latest CI:
|
|
||||||
Wiki Publishing:
|
|
||||||
|
|
||||||
[](https://github.com/praktimarc/kst4contest/actions/workflows/github-wiki.yml)
|
|
||||||
|
|
||||||
[](https://github.com/praktimarc/kst4contest/actions/workflows/docs-pdf.yml)
|
|
||||||
|
|
||||||
Builds:
|
|
||||||
|
|
||||||
[](https://github.com/praktimarc/kst4contest/actions/workflows/nightly-artifacts.yml)
|
|
||||||
@@ -1,2 +0,0 @@
|
|||||||
dr2x
|
|
||||||
oe3cin
|
|
||||||
-15832
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,8 @@
|
|||||||
|
[Flatpak Ref]
|
||||||
|
Name=de.x08.KST4Contest
|
||||||
|
Branch=stable
|
||||||
|
Title=KST4Contest – ON4KST Chat Client
|
||||||
|
Url=https://praktimarc.github.io/kst4contest/
|
||||||
|
RuntimeRepo=https://flathub.org/repo/flathub.flatpakrepo
|
||||||
|
GPGKey=mQINBGowB94BEACrD2AV/0kpwPjfu/hk8TJdlx8a7kvMOHzqJJLVOh1Nsp4BWXb3Wd2CUdFoFoRroclMiHEMNljGjD4Zov4B3Q1mDWwmgxAWrW6Gs5LeNXwBhrMss6m6sW1oPX/7Dbivb2YHlkQ/cLKMjFsAXF5YRwyox3kgJSWQkuke5feNI7zlE9L5cf/eyrpmy/YGUJjgZ36nDLGJeqa20BWMLjBd9KQoe0R1GO9I3LUeyQAr5a+FFvGtJ/c3kQcvWszWq0V2a4PnjMYcyu2MGkx+X0Eeou51Z08FdUB1+2ZOF3vPD/lNVfTCP2pLZ95KSRofkpfX93segEm3rHraxpFUnZyPSlPfP7mLNy5uZPU1XRvbQc9nQ2Nmot8R6indRM08yl/ZVym4FJQaYL0DdHXP7H95Rcm/S0QdIN4RbUBuXwtJI3Ru5rJ40SkO3kezFLb6elKlddwNkWlotvtL320/2S6OvSXB/Z2QPQvr2u1JkKOaypwxKFW73yqCpxtZjYTJfWmUtg6qSL3RoEXfIZIJQQqNUqyBUjxbzJA+INQfMPCmLAff3AeBkrQ6PoEszenDn89gz5lAKV8U0nls6nmI6ejTHRRB3a9eqIAvRYVTk7tVkaO2HDYmrbGLFvicLlHg3EZMKUVed4sPooRKZsTm+HSYIOp3WYrGm4KDejcVvbX6RaecMQARAQABtClLU1Q0Q29udGVzdCBGbGF0cGFrIDxmbGF0cGFrQGtzdDRjb250ZXN0PokCTwQTAQoAORYhBOR4Druu7f7iLrxAqJ+GlquNiTZgBQJqMAfeAxsvBAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRCfhparjYk2YL/JD/9SJglBeCtNPf8H1+lo5OlS4Gha+cBngESMWfrGQww6TonULuSSMtyMabFotEQUmZ9rGmEerwAWENH96KXJlv+fVPUIz4dREiJf4nPAluDb2yapWVQjVxorHR1OI185OXPWq0OXZ6OdZH+e5zHIDDHRlwwWU0LdyeSZrGoCe8vkWHe4x7BbG2+Ocafno14MzbTFSkHbuYgQi0DAfLhp4xuZpop4qktHs8mcEFzn97IDk2z/vXETw4Lm5jwmEFUk2wM3N65HS3DkhujR4fvZf/OKJvQ+oRCWJ2LYseAsopoPBjUT2EkhlMQKDSR6L2P2cN4gUnbwmGO6wzKRsvRIZFBAzkASHSr6gwizhOVoRILh3uTPrshbea8qif/jXfLbhMJiYpfp4zLtjPCevyaBY6ZfMKVeIR+yjUzBfqOGRQwdXW8zsfmSPMT0acurr3nvg3RNA+4gJAbbcIQRcbjeEmIeeUSiPjK3xvNz7WdyA3e6U4ocjZivTDv+xQ4Nmowz1Q3Iy9N5/k18nu2hIl9YfVt9Vn4XfJuqtYruIX9dA/F7x6uQ9M4jM8jwU+NV9HqOdlHV+eIiZuMKUy7pLPwW1QaLxmMN2nc2wutjHdh5Ywn1whVszvXgE+W1L4W4PmzW/Iw5KbjyTehEFfLNUM6bnME05fQpEcuQgmDfHPWkMf6fIA==
|
||||||
|
IsRuntime=false
|
||||||
@@ -1,53 +0,0 @@
|
|||||||
# KST4Contest – Wiki
|
|
||||||
|
|
||||||
**KST4Contest** (auch bekannt als *PraktiKST*) ist ein Java-basierter Chat-Client für den [ON4KST-Chat](http://www.on4kst.info/chat/), speziell entwickelt für den Contest-Betrieb auf den VHF/UHF/SHF-Bändern.
|
|
||||||
|
|
||||||
Entwickelt von **DO5AMF (Marc Fröhlich)**, Operator bei DM5M.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## 🌐 Sprache / Language
|
|
||||||
|
|
||||||
| 🇩🇪 Deutsch | 🇬🇧 English |
|
|
||||||
|---|---|
|
|
||||||
| [Startseite (Deutsch)](de-Home) | [Home (English)](en-Home) |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## 🇩🇪 Inhalt (Deutsch)
|
|
||||||
|
|
||||||
| Seite | Inhalt |
|
|
||||||
|---|---|
|
|
||||||
| [Installation](de-Installation) | Download, Java-Voraussetzungen, Update |
|
|
||||||
| [Konfiguration](de-Konfiguration) | Alle Einstellungen im Detail |
|
|
||||||
| [Log-Synchronisation](de-Log-Synchronisation) | UCXLog, N1MM+, QARTest, DXLog.net, WinTest |
|
|
||||||
| [AirScout-Integration](de-AirScout-Integration) | Flugzeug-Scatter-Erkennung |
|
|
||||||
| [DX-Cluster-Server](de-DX-Cluster-Server) | Integrierter DX-Cluster für das Log-Programm |
|
|
||||||
| [Funktionen](de-Funktionen) | Alle Features im Überblick |
|
|
||||||
| [Makros und Variablen](de-Makros-und-Variablen) | Text-Snippets, Shortcuts, Variablen |
|
|
||||||
| [Benutzeroberfläche](de-Benutzeroberflaeche) | UI-Erklärung und Bedienung |
|
|
||||||
| [Changelog](de-Changelog) | Versionsgeschichte |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## 🇬🇧 Contents (English)
|
|
||||||
|
|
||||||
| Page | Contents |
|
|
||||||
|---|---|
|
|
||||||
| [Installation](en-Installation) | Download, Java requirements, updates |
|
|
||||||
| [Configuration](en-Configuration) | All settings in detail |
|
|
||||||
| [Log Synchronisation](en-Log-Sync) | UCXLog, N1MM+, QARTest, DXLog.net, WinTest |
|
|
||||||
| [AirScout Integration](en-AirScout-Integration) | Aircraft scatter detection |
|
|
||||||
| [DX Cluster Server](en-DX-Cluster-Server) | Built-in DX cluster for your logging software |
|
|
||||||
| [Features](en-Features) | All features at a glance |
|
|
||||||
| [Macros and Variables](en-Macros-and-Variables) | Text snippets, shortcuts, variables |
|
|
||||||
| [User Interface](en-User-Interface) | UI explained and how to operate it |
|
|
||||||
| [Changelog](en-Changelog) | Version history |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Schnellinfo / Quick Info
|
|
||||||
|
|
||||||
- **Download**: https://github.com/praktimarc/kst4contest/releases
|
|
||||||
- **GitHub**: https://github.com/praktimarc/kst4contest
|
|
||||||
- **Kontakt / Contact**: praktimarc+kst4contest@gmail.com
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 46 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 143 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 148 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 110 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 109 KiB |
@@ -1,116 +0,0 @@
|
|||||||
# AirScout-Integration
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-AirScout-Integration) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
AirScout (von DL2ALF) ist ein Programm zur Erkennung von Flugzeugen für den Aircraft-Scatter-Betrieb. KST4Contest ist eng mit AirScout integriert und zeigt reflektierbare Flugzeuge direkt in der Benutzerliste an.
|
|
||||||
|
|
||||||
> **Aircraft Scatter** ermöglicht sehr weitreichende Verbindungen auf VHF und höher – auch für Stationen mit geringer Höhe über NN oder ungünstigen topografischen Verhältnissen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AirScout herunterladen
|
|
||||||
|
|
||||||
Download von AirScout:
|
|
||||||
- http://airscout.eu/index.php/download
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Flugzeugdaten-Feeds (ADSB)
|
|
||||||
|
|
||||||
Öffentliche Flugzeugdaten-Feeds im Internet sind oft unzuverlässig und begrenzt nutzbar. Eine empfohlene Alternative bietet **OV3T (Thomas)** mit einem dedizierten ADSB-Feed-Dienst:
|
|
||||||
|
|
||||||
- https://airscatter.dk/
|
|
||||||
- https://www.facebook.com/groups/825093981868542
|
|
||||||
|
|
||||||
Für diesen Dienst ist ein Account erforderlich. Bitte eine Spende für Thomas in Betracht ziehen – der Server-Betrieb ist nicht kostenlos!
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AirScout einrichten
|
|
||||||
|
|
||||||
### Schritt 1: ADSB-Feed in AirScout konfigurieren
|
|
||||||
|
|
||||||
1. AirScout starten.
|
|
||||||
2. In den AirScout-Einstellungen den OV3T-Feed-Account eintragen (Benutzername, Passwort, URL).
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. Verbindung testen.
|
|
||||||
|
|
||||||
### Schritt 2: UDP-Kommunikation für KST4Contest aktivieren
|
|
||||||
|
|
||||||
In AirScout die UDP-Schnittstelle aktivieren:
|
|
||||||
|
|
||||||
- In den AirScout-Einstellungen die entsprechende Checkbox aktivieren (nur eine Checkbox notwendig).
|
|
||||||
- Standard-Ports nicht ändern, wenn kein besonderer Grund vorliegt.
|
|
||||||
|
|
||||||
### Schritt 3: KST4Contest-Einstellungen
|
|
||||||
|
|
||||||
In den KST4Contest-Preferences → **AirScout Settings**:
|
|
||||||
- AirScout-Kommunikation aktivieren
|
|
||||||
- IP und Port auf Standardwerte lassen (sofern nicht geändert)
|
|
||||||
|
|
||||||
{ width=85% }
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Kommunikation zwischen KST4Contest und AirScout (ab v1.263)
|
|
||||||
|
|
||||||
**Verbesserung in v1.263**: KST4Contest sendet nur noch Stationen an AirScout, deren QRB (Entfernung) kleiner als das eingestellte **Maximum-QRB** ist. Das Abfrageintervall wurde von 12 Sekunden auf **60 Sekunden** verlängert.
|
|
||||||
|
|
||||||
**Vorteile:**
|
|
||||||
- Deutlich weniger Berechnungsaufwand für AirScout
|
|
||||||
- Deutlich weniger Nachrichtenverkehr
|
|
||||||
- Das Tracking-Problem mit dem „Show Path in AirScout"-Button wurde dadurch deutlich verbessert
|
|
||||||
- Weniger Rechenleistung insgesamt
|
|
||||||
|
|
||||||
Außerdem: Der Name des KST4Contest-Clients und des AirScout-Servers war früher hartcodiert (`KST` und `AS`). Ab v1.263 werden die in den Preferences eingetragenen Namen verwendet.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Mehrere KST4Contest-Instanzen und AirScout
|
|
||||||
|
|
||||||
> **Achtung**: Wenn mehrere KST4Contest-Instanzen gleichzeitig betrieben werden und bei beiden die AirScout-Kommunikation aktiviert ist, antwortet AirScout **an beide Instanzen**.
|
|
||||||
|
|
||||||
Das ist unproblematisch, wenn:
|
|
||||||
- Beide Instanzen denselben Locator verwenden, **oder**
|
|
||||||
- Beide Instanzen unterschiedliche Login-Rufzeichen haben.
|
|
||||||
|
|
||||||
Andernfalls kann es zu fehlerhaften AP-Daten kommen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AP-Spalte in der Benutzerliste
|
|
||||||
|
|
||||||
Nach der Einrichtung erscheint in der Benutzerliste eine **AP-Spalte** mit bis zu zwei reflektierbaren Flugzeugen pro Station.
|
|
||||||
|
|
||||||
Beispiel-Darstellung:
|
|
||||||
|
|
||||||
| Station | AP-Info |
|
|
||||||
|---|---|
|
|
||||||
| DF9QX | 2 Planes: 0 min / 0 min, je 100% |
|
|
||||||
| F5DYD | 2 Planes: 14 min / 31 min, je 50% |
|
|
||||||
|
|
||||||
Die AP-Informationen sind auch im **Privatnachrichten-Fenster** verfügbar.
|
|
||||||
|
|
||||||
Die Prozentzahl gibt das Reflexionspotenzial an (Größe des Flugzeugs, Höhe, Entfernung).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AP-Variablen in Nachrichten
|
|
||||||
|
|
||||||
Die Flugzeugdaten können direkt in Nachrichten eingefügt werden:
|
|
||||||
|
|
||||||
- `FIRSTAP` → z. B. `a very big AP in 1 min`
|
|
||||||
- `SECONDAP` → z. B. `Next big AP in 9 min`
|
|
||||||
|
|
||||||
Details: [Makros und Variablen](Makros-und-Variablen#variablen)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## „Show Path in AirScout"-Button
|
|
||||||
|
|
||||||
In der Benutzerliste gibt es einen Button mit einem Pfeil, der die Richtung (QTF) zur ausgewählten Station anzeigt. Ein Klick maximiert AirScout und zeigt den Pfad mit reflektierbaren Flugzeugen zum ausgewählten Gesprächspartner.
|
|
||||||
@@ -1,105 +0,0 @@
|
|||||||
# Benutzeroberfläche
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-User-Interface) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
## Verbinden mit dem Chat
|
|
||||||
|
|
||||||
1. Im Einstellungsfenster eine **Chat-Kategorie** auswählen (z. B. 144 MHz VHF, 432 MHz UHF, …).
|
|
||||||
2. **Connect**-Button klicken.
|
|
||||||
3. Warten bis die Verbindung aufgebaut ist.
|
|
||||||
|
|
||||||
> Trennen und Neu-Verbinden ist nur über das Einstellungsfenster möglich. Es empfiehlt sich daher, das Einstellungsfenster geöffnet zu lassen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Hauptfenster-Überblick
|
|
||||||
|
|
||||||
Das Hauptfenster besteht aus mehreren Bereichen:
|
|
||||||
|
|
||||||
### PM-Fenster (oben links)
|
|
||||||
|
|
||||||
Zeigt alle empfangenen **Privatnachrichten** sowie abgefangene öffentliche Nachrichten, die das eigene Rufzeichen enthalten. Neue Nachrichten erscheinen in **Rot** und faden alle 30 Sekunden über Gelb bis Weiß ab.
|
|
||||||
|
|
||||||
### Benutzerliste (Chat Members)
|
|
||||||
|
|
||||||
Die zentrale Tabelle aller aktuell aktiven Chat-Nutzer. Spalten (je nach Konfiguration):
|
|
||||||
|
|
||||||
| Spalte | Inhalt |
|
|
||||||
|---|---|
|
|
||||||
| Call | Rufzeichen der Station |
|
|
||||||
| Name | Name aus dem Chat-Namenfeld |
|
|
||||||
| Loc | Maidenhead-Locator |
|
|
||||||
| QRB | Entfernung in km |
|
|
||||||
| QTF | Richtung in Grad |
|
|
||||||
| QRG | Automatisch erkannte Frequenz |
|
|
||||||
| AP | AirScout-Flugzeugdaten (wenn aktiv) |
|
|
||||||
| Band-Farben | Worked/NOT-QRV-Status pro Band |
|
|
||||||
|
|
||||||
**Sortierung**: Klick auf Spaltenköpfe. QRB-Sortierung arbeitet numerisch (ab v1.22 korrigiert).
|
|
||||||
|
|
||||||
### Sendfeld
|
|
||||||
|
|
||||||
Texteingabe für ausgehende Nachrichten. Nach Klick auf ein Rufzeichen in der Benutzerliste erhält das Sendfeld automatisch den Fokus – sofort tippen ohne Doppelklick (ab v1.22).
|
|
||||||
|
|
||||||
### MYQRG-Feld
|
|
||||||
|
|
||||||
Rechts neben dem Sendbutton. Zeigt die aktuelle eigene QRG an, kann auch manuell eingetragen werden.
|
|
||||||
|
|
||||||
### MYQTF-Feld *(für v1.3)*
|
|
||||||
|
|
||||||
Eingabefeld für die aktuelle Antennenrichtung. Wird für die geplante `MYQTF`-Variable verwendet.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Filter
|
|
||||||
|
|
||||||
Die Filter-Leiste (ab v1.21 als Flowpane für kleine Bildschirme):
|
|
||||||
|
|
||||||
- **Show only QTF**: Richtungsfilter aktivieren (Buttons N/NE/E/… oder Grad-Eingabe)
|
|
||||||
- **Show only QRB [km] <=**: Entfernungsfilter aktivieren (Toggle-Button)
|
|
||||||
- **Hide Worked [Band]**: Gearbeitete Stationen pro Band ausblenden (je ein Toggle pro Band)
|
|
||||||
- **Hide NOT-QRV [Band]**: NOT-QRV-markierte Stationen pro Band ausblenden
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Stationsinfo-Panel (Further Info)
|
|
||||||
|
|
||||||
Rechts unten: Zeigt alle Nachrichten einer ausgewählten Station (CQ-Nachrichten und PMs in einem Panel). Ein Nachrichtenfilter lässt sich über den Standard-Filter in den Preferences vorbelegen.
|
|
||||||
|
|
||||||
Hier können auch **Sked-Erinnerungen** aktiviert werden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Prioritätsliste
|
|
||||||
|
|
||||||
Zeigt die vom Score-Service berechneten Top-Kandidaten. Aktualisiert sich automatisch im Hintergrund basierend auf Richtung, Entfernung und AP-Verfügbarkeit.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Cluster & QSO der anderen
|
|
||||||
|
|
||||||
Separates Fenster (kann miniaturisiert werden). Zeigt den Kommunikationsfluss zwischen anderen Stationen – interessant in ruhigeren Phasen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Menü
|
|
||||||
|
|
||||||
### Window
|
|
||||||
- **Use Dark Mode** (ab v1.26): Dunkles Farbschema aktivieren/deaktivieren.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Fenstergrößen und Divider
|
|
||||||
|
|
||||||
Ab **v1.21** werden beim Klick auf **„Save Settings"** auch Fenstergrößen und Divider-Positionen aller Panels in der Konfigurationsdatei gespeichert und beim nächsten Start wiederhergestellt.
|
|
||||||
|
|
||||||
Bei Problemen mit der Darstellung: Konfigurationsdatei löschen → KST4Contest erstellt neue Standardwerte.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Tipps zur Bedienung
|
|
||||||
|
|
||||||
- **Einstellungsfenster geöffnet lassen**: Schneller Zugriff auf Beacon-Aktivierung/Deaktivierung.
|
|
||||||
- **Rechtsklick in der Benutzerliste**: Öffnet das Snippet-Menü und weitere Aktionen (QRZ.com-Profil, NOT-QRV-Tags setzen).
|
|
||||||
- **Enter aus dem Chat heraus**: Wenn im Sendfeld Text steht, sendet Enter direkt – auch wenn der Fokus woanders liegt.
|
|
||||||
- **Beacon stoppen**: Beim Scannen von Frequenzen den Beacon ausschalten, damit der Chat nicht mit Meldungen überflutet wird.
|
|
||||||
@@ -1,235 +0,0 @@
|
|||||||
# Changelog
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Changelog) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
Versionsverlauf von KST4Contest / PraktiKST.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
letzter Changelog bitte aus GitHub entnehmen. Der bisherige Changelog
|
|
||||||
|
|
||||||
## v1.40 (2026-02-16)
|
|
||||||
**Großes Feature-Release: Score-System, AP-Timeline, Win-Test, PSTRotator**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- **Chatmember Score-System**: Jeder Chatmember erhält automatisch eine Prioritätsbewertung anhand von Antennenrichtung, Aktivitätszeit, Nachrichtenanzahl, aktiven Bändern, Frequenzen, Sked-Richtung und anderen Faktoren. Die Top-Kandidaten werden in einer eigenen Liste hervorgehoben.
|
|
||||||
- **AP-Timeline**: Für jeden möglichen AP-Ankunftsminuten-Slot werden bis zu 4 hochbewertete Stationen angezeigt, die erreichbar wären. Bevorzugt werden APs mit dem höchsten Potenzial, nicht die schnellste Ankunft. Stationen, auf die die eigene Antenne nicht zeigt, werden transparent dargestellt.
|
|
||||||
- **Win-Test-Unterstützung** (ab v1.31 als Beta, jetzt vollständig konfigurierbar): Log-Synchronisation, Frequenzauswertung und **Sked-Übergabe via UDP** vollständig integriert. In den Preferences aktivier-/deaktivierbar.
|
|
||||||
- **PSTRotator-Interface** (ab v1.31 als Beta, jetzt vollständig konfigurierbar): Aktualisierung der Rotatorposition direkt aus KST4Contest. In den Preferences aktivier-/deaktivierbar.
|
|
||||||
- **QSO-Sniffer**: Nachrichten von konfigurierbaren Rufzeichen-Listen werden automatisch in das PM-Fenster weitergeleitet.
|
|
||||||
- **Band-Alert bei gearbeiteten Stationen**: Wenn eine Station geloggt wird, erscheint ein Hinweis, wenn diese Station ein weiteres Band aktiv hat, auf dem man selbst ebenfalls QRV ist.
|
|
||||||
- **Sked-Erinnerungs-ALERT**: Pro Chatmember kann ein Sked-Alarm mit automatischen Nachrichten in konfigurierbaren Intervallen (2+1 / 5+2+1 / 10+5+2+1 Minuten vor dem Sked) eingerichtet werden, plus akustische und optische Benachrichtigung.
|
|
||||||
- **Chat-Historie beim Start laden**: Beim Verbindungsaufbau wird die Serverhistorie geladen, um aktive Chatmember und letzte Nachrichten sofort sichtbar zu machen.
|
|
||||||
- **Skedfail-Button**: Im FurtherInfo-Panel kann ein Sked-Misserfolg für einen Chatmember markiert werden, was dessen Score senkt.
|
|
||||||
|
|
||||||
**Geändert:**
|
|
||||||
- AP-Notizen in DX-Cluster-Spots integriert.
|
|
||||||
- Scrolling der Chatmember-Tabelle folgt automatisch der aktuellen Nachrichtenauswahl.
|
|
||||||
- Generic Auto-Antwort und QRG-Auto-Antwort senden max. einmal pro 45 Sekunden pro Rufzeichen (verhindert Spam-Schleifen).
|
|
||||||
- Speicherbare Einstellungen erweitert: ServerDNS/Port, PSTRotator-Interface, Win-Test-Interface, Callsign-Sniffer, Dark-Mode-Standard.
|
|
||||||
- Datum in der Chat-Tabelle entfernt (nur Uhrzeit verbleibt – spart Platz).
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Benutzerliste wird jetzt bei jedem Neu-Login automatisch sortiert.
|
|
||||||
- Posonpill-Nachrichten beenden jetzt nur genau eine Client-Instanz (nicht alle und nicht wtKST).
|
|
||||||
- wtKST: Absturz bei KST4Contest-Trennung behoben.
|
|
||||||
- Mehrere Probleme mit Rufzeichen-Suffixen wie `/p`, `-2` etc. behoben.
|
|
||||||
- `QTFDefault` wurde nicht korrekt gespeichert → behoben.
|
|
||||||
- AirScout-Watchlist (ASWATCHLIST) wurde nicht korrekt aktualisiert → behoben.
|
|
||||||
- Dark Mode: QRG-Felder wurden nicht vollständig angezeigt → behoben.
|
|
||||||
- Versionsnummer-Anzeige korrigiert.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.31 (2025-12-13)
|
|
||||||
**Win-Test + PSTRotator Beta, QSO-Sniffer, DNS-Hotfix**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- **Win-Test-Unterstützung** (Beta, noch nicht deaktivierbar): Log-Synchronisation und Frequenzauswertung.
|
|
||||||
- **PSTRotator-Unterstützung** (Beta, noch nicht deaktivierbar).
|
|
||||||
- **QSO-Sniffer**: Nachrichten von konfigurierbaren Rufzeichen werden ins PM-Fenster weitergeleitet.
|
|
||||||
|
|
||||||
**Geändert:**
|
|
||||||
- **DNS-Server geändert**: Von `www.on4kst.info` auf `www.on4kst.org` (Hotfix). Der DNS-Server ist ab sofort in den Preferences änderbar.
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Endlosschleife im Fehlerfall friert den Client ein → behoben.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.266 (2025-10-03)
|
|
||||||
**AirScout-Fix für Rufzeichen mit Suffix**
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- AirScout-Interface funktionierte nicht, wenn das Login-Rufzeichen einen Suffix enthielt (z. B. `9A1W-2`). AirScout kann mit diesem Format nicht umgehen – es wird jetzt nur noch das Basis-Rufzeichen ohne Suffix an AirScout übergeben.
|
|
||||||
|
|
||||||
*(Fehler gemeldet und getestet von 9A2HM / Kreso – herzlichen Dank!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.265 (2025-09-28)
|
|
||||||
**Richtungs-Buttons bleiben aktiviert eingefärbt**
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Richtungs-Buttons (N / NE / E usw.) behalten jetzt ihre Farbe, wenn sie aktiviert sind, sodass der Aktivierungsstatus auf einen Blick erkennbar ist.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.264 (2025-08-02)
|
|
||||||
**Simplelogfile: Rufzeichen-Erkennung verbessert**
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Rufzeichen wie `S53CC`, `S51A` usw. wurden in der SimpleLogFile-Auswertung nicht als gearbeitet markiert → Erkennungsmuster verbessert.
|
|
||||||
|
|
||||||
*(Fehler gemeldet von Boris, S53CC – danke!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.263 (2025-06-08)
|
|
||||||
**AirScout-Kommunikation und Login-Name**
|
|
||||||
|
|
||||||
**Geändert:**
|
|
||||||
- AirScout-Kommunikation grundlegend überarbeitet: Nur noch Stationen mit QRB < max-QRB werden an AirScout gesendet.
|
|
||||||
- Abfrage-Intervall von 12 Sekunden auf **60 Sekunden** erhöht.
|
|
||||||
- Deutlich weniger Berechnungsaufwand und Nachrichtenverkehr → Stabileres AirScout-Tracking.
|
|
||||||
- Name des AS-Clients und AS-Servers ist jetzt aus den Preferences konfigurierbar (war vorher hartcodiert auf „KST" / „AS").
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- „Track in AirScout"-Button war sehr träge → durch neue Kommunikationslogik deutlich verbessert.
|
|
||||||
- Name im Chat ist jetzt speicherbar (Fehler behoben).
|
|
||||||
- Visuelle Korrekturen vor und nach dem Login.
|
|
||||||
- Fehler behoben, der von 9A2HM (Kreso) gemeldet wurde.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.262 (2025-05-21)
|
|
||||||
**Freeze-Fix bei vorzeitiger Nachrichtenlieferung**
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- ON4KST liefert manchmal Nachrichten, bevor der Login abgeschlossen ist. Das verursachte Fehler in der Nachrichtenverarbeitung → jetzt behoben.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.26 (2025-05)
|
|
||||||
**Multi-Channel-Login und Dark Mode**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- **Dark Mode**: Umschaltbar über `Window → Use Dark Mode`.
|
|
||||||
- **Multi-Channel-Login**: Gleichzeitiger Login in zwei Chat-Kategorien.
|
|
||||||
- **Opposite Station Multi-Callsign Login-Tagging**: Unterstützung für Stationen mit mehreren Rufzeichen.
|
|
||||||
|
|
||||||
**Geändert:**
|
|
||||||
- Farbgebungs-Mechanismus überarbeitet: Farben können jetzt über CSS angepasst werden.
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Stationsmarkierung komplett überarbeitet und korrekt gestellt.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.251 (2025-02)
|
|
||||||
**Bugfix für UDP-Broadcast-Spot-Info**
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Problem beim Lesen von UDP-Broadcast-Spot-Informationen behoben (gemeldet von Steve Clements – danke!).
|
|
||||||
- Stationsmarkierung (erneut verbessert).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.25 (2025-02)
|
|
||||||
**Wunschliste umgesetzt**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- **Neuer Einstellungs-Tab: Messagehandling**
|
|
||||||
- Auto-Antwort auf eingehende Nachrichten konfigurierbar.
|
|
||||||
- Automatische Antwort mit eigener CQ-QRG, wenn jemand danach fragt.
|
|
||||||
- Konfigurierbarer Standard-Filter für das Userinfo-Fenster *(für Gianluca :-) )*.
|
|
||||||
- **Farbige PM-Zeilen**: Neue Privatnachrichten erscheinen rot und faden alle 30 Sekunden über Gelb bis Weiß ab *(Idee von IU3OAR, Gianluca)*.
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Stationen mit Suffixen wie „-2" und „-70" wurden nicht als gearbeitet markiert → werden jetzt ignoriert, Station wird korrekt markiert.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.24 (2024-11)
|
|
||||||
**Wunschliste + DX-Cluster-Spots**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- Button zum Öffnen des **QRZ.com-Profils** der ausgewählten Station.
|
|
||||||
- Button zum Öffnen des **QRZ-CQ-Profils** der ausgewählten Station.
|
|
||||||
- **DX-Cluster-Server-Integration**: Richtungs-Warnungen werden als Spots an das Logprogramm gesendet (wenn QRG bekannt).
|
|
||||||
|
|
||||||
*(Zusätzlich wurden Farbgebungen der PM-Zeilen hinzugefügt – tnx Gianluca)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.23 (2024-10)
|
|
||||||
**Integrierter DX-Cluster-Server**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- KST4Contest enthält jetzt einen **integrierten DX-Cluster-Server**.
|
|
||||||
- Generiert DX-Cluster-Spots und sendet sie an das Logprogramm, wenn eine Richtungs-Warnung ausgelöst und eine QRG bekannt ist.
|
|
||||||
- Spotter-Rufzeichen muss sich vom Contest-Rufzeichen unterscheiden (für korrekte Filterung im Logprogramm).
|
|
||||||
|
|
||||||
*(Idee von OM0AAO, Viliam Petrik – danke!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.22 (2024-05)
|
|
||||||
**Usability-Verbesserungen und AirScout-Button-Fix**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- Neue Variablen (tnx OM0AAO, Viliam Petrik):
|
|
||||||
- `MYLOCATORSHORT`
|
|
||||||
- `MYQRGSHORT`
|
|
||||||
- `QRZNAME`
|
|
||||||
|
|
||||||
**Geändert:**
|
|
||||||
- Sendfeld-Fokus: Nach Klick auf Rufzeichen in der Benutzerliste erhält das Sendfeld sofort den Fokus – kein Doppelklick notwendig *(tnx Gianluca)*.
|
|
||||||
|
|
||||||
**Behoben:**
|
|
||||||
- Worked-Station-Filter ist jetzt live-aktiv: Gearbeitete Stationen verschwinden sofort nach Aktivierung des Filters *(tnx Gianluca)*.
|
|
||||||
- QRB-Sortierung war lexikografisch → jetzt numerisch *(tnx Alessandro Murador)*.
|
|
||||||
- AirScout-„Show Path"-Button: Klick maximiert AirScout und zeigt den Pfad korrekt an.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.21 (2024-04)
|
|
||||||
**Usability-Verbesserungen**
|
|
||||||
|
|
||||||
**Geändert:**
|
|
||||||
- Fenstergrößen und Divider-Positionen werden beim Klick auf „Save Settings" in der Konfigurationsdatei gespeichert und beim Start wiederhergestellt.
|
|
||||||
- Filter-Bereich als Flowpane → bessere Darstellung auf kleineren Bildschirmen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.2 (2024-04)
|
|
||||||
**Bandselektion und NOT-QRV-Tags**
|
|
||||||
|
|
||||||
**Neu:**
|
|
||||||
- **Bandselektion**: In den Preferences auswählbar, welche Bänder aktiv sind. Nur für gewählte Bänder erscheinen Buttons und Felder in der UI. Speichern und Neustart erforderlich.
|
|
||||||
- **NOT-QRV-Tags pro Station und Band**: Stationen können für jedes Band als „nicht QRV" markiert werden. Kombinierbar mit dem Userlist-Filter.
|
|
||||||
- **QTF-Pfeil**: Der „Show path in AS"-Button zeigt jetzt einen Pfeil mit dem QTF der ausgewählten Station an.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Frühere Versionen
|
|
||||||
|
|
||||||
### v1.1
|
|
||||||
Erste öffentlich veröffentlichte Version. Grundfunktionen:
|
|
||||||
- Worked-Markierung via Simplelogfile und UDP
|
|
||||||
- Sked-Richtungs-Hervorhebung
|
|
||||||
- QRG-Erkennung
|
|
||||||
- Text-Snippets und Shortcuts
|
|
||||||
- AirScout-Interface (erste Version)
|
|
||||||
- Intervall-Beacon
|
|
||||||
- PM-Abfang für öffentliche Nachrichten mit eigenem Rufzeichen
|
|
||||||
- Update-Hinweis-Dienst
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Geplante Features
|
|
||||||
|
|
||||||
- `MYQTF`-Variable (eigene Antennenrichtung als Text)
|
|
||||||
- ~~Lebensdauer für den Worked-Status (automatisches Zurücksetzen)~~ ✅ **Umgesetzt in v1.40** (3-Tage-Lebensdauer, kein manuelles Zurücksetzen mehr nötig)
|
|
||||||
- Filterung des „Cluster & QSO der anderen"-Fensters auf eigenes QTF
|
|
||||||
- Weitere Topografie-basierte Berechnungen für die Richtungswarnung
|
|
||||||
@@ -1,76 +0,0 @@
|
|||||||
# Integrierter DX-Cluster-Server
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-DX-Cluster-Server) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
Ab **Version 1.23** enthält KST4Contest einen integrierten DX-Cluster-Server. Dieser sendet Spots direkt an das Logprogramm, wenn eine Richtungs-Warnung ausgelöst wird.
|
|
||||||
|
|
||||||
*(Idee von OM0AAO, Viliam Petrik – danke!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Wozu dient der integrierte DX-Cluster-Server?
|
|
||||||
|
|
||||||
Wenn KST4Contest erkennt, dass eine Station aus der eigenen Richtung ein Sked anfragt und gleichzeitig eine QRG bekannt ist, wird **automatisch ein DX-Cluster-Spot generiert** und an den Cluster-Client des Logprogramms gesendet.
|
|
||||||
|
|
||||||
Das Logprogramm zeigt den Spot in der Bandkarte an. Ein Klick auf den Spot stellt Frequenz und Mode des Transceivers direkt ein – ohne manuelles Eintippen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Einrichtung
|
|
||||||
|
|
||||||
### In KST4Contest
|
|
||||||
|
|
||||||
In den Preferences → **DX-Cluster-Server-Einstellungen**:
|
|
||||||
|
|
||||||
1. **Port** des internen Servers eintragen (z. B. 7300 oder 8000 – muss mit dem Logprogramm übereinstimmen).
|
|
||||||
2. **Spotter-Rufzeichen** eintragen – **unbedingt ein anderes Rufzeichen als das Contest-Rufzeichen verwenden!**
|
|
||||||
- Grund: Logprogramme filtern Spots, die vom eigenen Rufzeichen stammen, als „gearbeitet" heraus. Wenn der Spotter dasselbe Rufzeichen hat, werden die Spots nicht angezeigt.
|
|
||||||
3. **Angenommene MHz** eintragen: Bei Frequenzangaben wie „.205" im Chat muss KST4Contest entscheiden, ob 144.205, 432.205 oder 1296.205 gemeint ist. Bei Einband-Contests einfach die entsprechende Bandmitte eintragen. Vollständige Frequenzangaben wie „144.205" oder „1296.338" im Chat werden immer korrekt erkannt.
|
|
||||||
|
|
||||||
### In UCXLog
|
|
||||||
|
|
||||||
- Verbindung zu einem DX-Cluster-Server konfigurieren:
|
|
||||||
- Host: `127.0.0.1` (oder IP des KST4Contest-Computers)
|
|
||||||
- Port: Wie in KST4Contest konfiguriert
|
|
||||||
- Passwort: kann leer bleiben
|
|
||||||
- Über die Schaltfläche **„Send a test message to your log"** kann die Verbindung getestet werden.
|
|
||||||
|
|
||||||
### In N1MM+
|
|
||||||
|
|
||||||
Ähnliche Einstellungen:
|
|
||||||
- Host: `127.0.0.1` (oder IP des KST4Contest-Computers)
|
|
||||||
- Port: Wie in KST4Contest konfiguriert
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Funktionsweise
|
|
||||||
|
|
||||||
Ein Spot wird generiert, wenn **beide** Bedingungen erfüllt sind:
|
|
||||||
|
|
||||||
1. Eine **Richtungs-Warnung** wurde ausgelöst (Station macht ein Sked in die eigene Richtung).
|
|
||||||
2. **QRG der Station ist bekannt** (aus dem Chat ausgelesen oder manuell eingetragen).
|
|
||||||
|
|
||||||
Der generierte Spot enthält:
|
|
||||||
- Rufzeichen der Station
|
|
||||||
- Frequenz
|
|
||||||
- Spotterzeit
|
|
||||||
|
|
||||||
Das Logprogramm kann den Spot dann in der Bandkarte anzeigen und den TRX per Mausklick auf die Frequenz abstimmen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multi-Computer-Setup
|
|
||||||
|
|
||||||
Wenn KST4Contest auf einem separaten Computer läuft (nicht auf dem Log-Computer):
|
|
||||||
|
|
||||||
- Host im Logprogramm: IP des KST4Contest-Computers (nicht `127.0.0.1`)
|
|
||||||
- Entspricht der Konfiguration der QSO-UDP-Broadcast-Pakete (siehe [Log-Synchronisation](de-Log-Synchronisation))
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Getestete Logprogramme
|
|
||||||
|
|
||||||
- **UCXLog** ✓
|
|
||||||
- **N1MM+** ✓
|
|
||||||
|
|
||||||
Weitere Testergebnisse sind willkommen – bitte per E-Mail an DO5AMF melden.
|
|
||||||
@@ -1,237 +0,0 @@
|
|||||||
# Funktionen
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Features) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
Übersicht aller Hauptfunktionen von KST4Contest.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sked-Richtungs-Hervorhebung
|
|
||||||
|
|
||||||
Eine der Kernfunktionen: Wenn eine Station ein Sked in die **eigene Richtung** sendet, wird sie in der Benutzerliste **grün und fett** hervorgehoben.
|
|
||||||
|
|
||||||
### Wie funktioniert das?
|
|
||||||
|
|
||||||
Die Berechnung basiert auf folgender Logik:
|
|
||||||
|
|
||||||
- Wenn Station A eine Sked-Anfrage an Station B sendet, wird angenommen, dass A ihre Antenne auf B ausrichtet.
|
|
||||||
- Wenn die daraus resultierende Richtung von A zur eigenen Station innerhalb des halben Öffnungswinkels der eigenen Antenne liegt, wird A hervorgehoben.
|
|
||||||
|
|
||||||
**Beispiel** (Öffnungswinkel 69°, Halbwinkel 34,5°):
|
|
||||||
|
|
||||||
| Situation | Ergebnis für DO5AMF in JN49 |
|
|
||||||
|---|---|
|
|
||||||
| Sked von F5FEN → DM5M | ✅ Hervorhebung (F5FEN zeigt Richtung DM5M, das liegt nahe JN49) |
|
|
||||||
| Sked von DM5M → F5FEN | ✅ Hervorhebung (DM5M antwortet in Richtung F5FEN) |
|
|
||||||
| F1DBN ist unbeteiligt | ❌ Keine Hervorhebung |
|
|
||||||
| DO5AMF/P (anderer Standort) | ❌ Keine Hervorhebung für Sked-Antwort |
|
|
||||||
|
|
||||||
Die Berechnung berücksichtigt keine topografischen Wegberechnungen – das ist eine bewusste Vereinfachung. Möglicherweise wird das in einer späteren Version ergänzt.
|
|
||||||
|
|
||||||
> Konfiguration: [Konfiguration – Antennen-Öffnungswinkel](Konfiguration#antennen-öffnungswinkel-antenna-beamwidth)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sked-Richtungs-Spots (Integrierter DX-Cluster)
|
|
||||||
|
|
||||||
Ab **v1.23**: Richtungs-Warnungen werden als DX-Cluster-Spots an das Logprogramm weitergeleitet, wenn eine QRG bekannt ist. Details: [DX-Cluster-Server](de-DX-Cluster-Server).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## QRG-Erkennung (QRG Reading)
|
|
||||||
|
|
||||||
KST4Contest verarbeitet jede Chat-Nachricht und extrahiert automatisch **Frequenzangaben**. Diese werden in der Benutzerliste in der **QRG-Spalte** angezeigt.
|
|
||||||
|
|
||||||
Erkannte Formate: `144.205`, `432.088`, `.205` (mit konfigurierter Bandannahme), etc.
|
|
||||||
|
|
||||||
**Nutzen**: Ohne nachzufragen kann man direkt auf die QRG einer Station schauen und entscheiden, ob eine Verbindung möglich ist.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked-Markierung
|
|
||||||
|
|
||||||
Gearbeitete Stationen werden in der Benutzerliste visuell markiert – pro Band. Grundlage ist die [Log-Synchronisation](de-Log-Synchronisation) via UDP oder Simplelogfile.
|
|
||||||
|
|
||||||
Vor jedem Contest die Datenbank zurücksetzen: [Konfiguration – Worked Station Database Settings](Konfiguration#worked-station-database-settings).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## NOT-QRV-Tags (ab v1.2)
|
|
||||||
|
|
||||||
Wenn eine Station mitteilt, dass sie auf einem bestimmten Band nicht QRV ist, kann dies manuell markiert werden:
|
|
||||||
|
|
||||||
1. Station in der Benutzerliste auswählen.
|
|
||||||
2. Rechtsklick → NOT-QRV für das entsprechende Band setzen.
|
|
||||||
|
|
||||||
Diese Tags werden in der internen Datenbank gespeichert und bleiben nach einem Neustart von KST4Contest erhalten. Zurücksetzen über die Einstellungen möglich.
|
|
||||||
|
|
||||||
**Nutzen**: Verhindert wiederholte Sked-Anfragen auf Bändern, auf denen die Station nicht QRV ist – schont sowohl die eigenen Nerven als auch die der Gegenstation.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Richtungsfilter (Direction Filter)
|
|
||||||
|
|
||||||
Zeigt in der Benutzerliste nur Stationen an, die sich in einer bestimmten Richtung befinden. Aktivierbar über die Buttons N / NE / E / SE / S / SW / W / NW oder durch manuelle Eingabe von Grad.
|
|
||||||
|
|
||||||
Sinnvoll: Während man CQ in eine bestimmte Richtung ruft, nur Stationen in dieser Richtung anzeigen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Entfernungsfilter (Distance Filter)
|
|
||||||
|
|
||||||
Stationen jenseits einer maximalen Entfernung ausblenden. Schaltfläche **„Show only QRB [km] <="** ist ein Toggle-Button.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked- und NOT-QRV-Filter
|
|
||||||
|
|
||||||
Toggle-Buttons (einer pro Band) zum Ausblenden bereits gearbeiteter Stationen und/oder NOT-QRV-markierter Stationen. Der Filter wirkt **sofort** ohne manuelles Neu-Aktivieren (ab v1.22 live).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Farbige PM-Zeilen (ab v1.25)
|
|
||||||
|
|
||||||
Neue Privatnachrichten erscheinen in **Rot**. Die Farbe wechselt alle 30 Sekunden über Gelb bis Weiß – wie ein Regenbogen-Fade. So ist auf einen Blick erkennbar, wie aktuell eine Nachricht ist.
|
|
||||||
|
|
||||||
*(Idee von IU3OAR, Gianluca Costantino – danke!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## PM-Abfang (Catching Personal Messages)
|
|
||||||
|
|
||||||
Manche Nutzer senden Direktnachrichten versehentlich öffentlich, z. B.:
|
|
||||||
|
|
||||||
```
|
|
||||||
(DM5M) pse ur qrg
|
|
||||||
```
|
|
||||||
|
|
||||||
KST4Contest erkennt solche Nachrichten, die das eigene Rufzeichen enthalten, und sortiert sie automatisch in die **Privatnachrichten-Tabelle** ein. So gehen keine Nachrichten verloren.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multi-Channel-Login (ab v1.26)
|
|
||||||
|
|
||||||
Gleichzeitiger Login in **zwei Chat-Kategorien** (z. B. 144 MHz und 432 MHz). Beide Chats werden parallel überwacht.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Dark Mode (ab v1.26)
|
|
||||||
|
|
||||||
Aktivierbar über: **Window → Use Dark Mode**
|
|
||||||
|
|
||||||
Für individuelle Farbanpassungen: CSS-Datei bearbeiten (Pfad in den Programmunterlagen).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Opposite Station Multi-Callsign Login-Tagging (ab v1.26)
|
|
||||||
|
|
||||||
Unterstützung für Stationen, die mit mehreren Rufzeichen gleichzeitig im Chat aktiv sind (z. B. Expedition-Setups).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## QRZ.com und QRZ-CQ Profil-Buttons (ab v1.24)
|
|
||||||
|
|
||||||
Für ausgewählte Stationen in der Benutzerliste gibt es direkte Buttons, um das **QRZ.com-Profil** und das **QRZ-CQ-Profil** im Browser zu öffnen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sked-Erinnerungen mit ALERT (ab v1.40)
|
|
||||||
|
|
||||||
Für jeden Chatmember kann ein Sked-Erinnerungsdienst mit automatischen Nachrichten aktiviert werden. Konfigurierbare Intervallmuster:
|
|
||||||
|
|
||||||
- **2+1 Minuten**: Nachrichten bei 2 min und 1 min vor dem Sked.
|
|
||||||
- **5+2+1 Minuten**: Nachrichten bei 5, 2 und 1 min vor dem Sked.
|
|
||||||
- **10+5+2+1 Minuten**: Nachrichten bei 10, 5, 2 und 1 min vor dem Sked.
|
|
||||||
|
|
||||||
Zusätzlich zu den Nachrichten an die Gegenstation gibt es eine **akustische und optische Benachrichtigung** für den eigenen Operator, sodass kein Sked vergessen wird.
|
|
||||||
|
|
||||||
Aktivierung: FurtherInfo-Panel der entsprechenden Station.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## QSO-Sniffer (ab v1.31)
|
|
||||||
|
|
||||||
Der QSO-Sniffer überwacht den Chat auf Nachrichten von einer konfigurierbaren Rufzeichen-Liste und leitet diese automatisch in das **PM-Fenster** weiter. So gehen keine relevanten Nachrichten im allgemeinen Chat-Rauschen unter.
|
|
||||||
|
|
||||||
Konfiguration: [Konfiguration – Sniffer-Einstellungen](de-Konfiguration#sniffer-einstellungen-ab-v131)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Win-Test-Integration (ab v1.31, vollständig ab v1.40)
|
|
||||||
|
|
||||||
KST4Contest unterstützt [Win-Test](https://www.win-test.com/) vollständig als Logprogramm:
|
|
||||||
|
|
||||||
- **Log-Synchronisation**: Gearbeitete Stationen werden automatisch aus Win-Test übernommen und in der Benutzerliste markiert.
|
|
||||||
- **Frequenz-Auswertung**: Die aktuelle TRX-Frequenz wird aus Win-Test-UDP-Paketen ausgewertet und befüllt die `MYQRG`-Variable.
|
|
||||||
- **Sked-Übergabe (SKED Push via UDP)**: Vereinbarte Skeds aus KST4Contest können direkt an Win-Test übertragen werden, sodass das Rufzeichen der Gegenstation im Win-Test-Sked-Fenster erscheint.
|
|
||||||
|
|
||||||
Details zur Konfiguration: [Konfiguration – Win-Test-Netzwerk-Listener](de-Konfiguration#win-test-netzwerk-listener)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## PSTRotator-Interface (ab v1.31, vollständig ab v1.40)
|
|
||||||
|
|
||||||
KST4Contest kann die Antennenrichtung direkt über **PSTRotator** steuern. Wenn in der Benutzerliste eine Station ausgewählt wird, kann der Rotator automatisch auf den QTF zur ausgewählten Station gedreht werden.
|
|
||||||
|
|
||||||
Konfiguration: [Konfiguration – PSTRotator-Einstellungen](de-Konfiguration#pstrotator-einstellungen-ab-v131)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Band-Alert bei neuen QSOs (ab v1.40)
|
|
||||||
|
|
||||||
Wenn eine Station geloggt wird, prüft KST4Contest automatisch, ob diese Station im Chat weitere aktive Bänder angezeigt hat, auf denen man selbst ebenfalls QRV ist. Falls ja, erscheint ein **Hinweis-Alert**, damit keine Multi-Band-Möglichkeit übersehen wird.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked-Tag-Lebensdauer (ab v1.40)
|
|
||||||
|
|
||||||
Gearbeitete Stationen werden nach **3 Tagen** automatisch aus der Datenbank entfernt. Ein manuelles Zurücksetzen der Worked-Datenbank vor jedem Contest ist damit nicht mehr zwingend notwendig – die Datenbank hält sich selbst aktuell.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Chatmember Score-System / Prioritätsliste (ab v1.40)
|
|
||||||
|
|
||||||
KST4Contest berechnet automatisch eine **Prioritätsbewertung** für jeden aktiven Chatmember. Der Score setzt sich zusammen aus:
|
|
||||||
|
|
||||||
- Antennenrichtung der Gegenstation (zeigt sie auf mich?)
|
|
||||||
- QRB (Entfernung)
|
|
||||||
- Aktivitätszeit und Nachrichtenanzahl
|
|
||||||
- Aktive Bänder und Frequenzen
|
|
||||||
- AP-Verfügbarkeit (AirScout)
|
|
||||||
- Sked-Richtung
|
|
||||||
- Sked-Erfolgsrate und Skedfail-Markierungen
|
|
||||||
|
|
||||||
Die Top-Kandidaten werden in einer eigenen Prioritätsliste hervorgehoben und helfen, im Contest-Stress die wichtigsten Stationen nicht zu übersehen.
|
|
||||||
|
|
||||||
Stationen, bei denen ein Sked gescheitert ist, können über den **Skedfail-Button** im FurtherInfo-Panel markiert werden – das senkt ihren Score vorübergehend.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AP-Timeline (ab v1.40)
|
|
||||||
|
|
||||||
Eine visuelle Zeitleiste zeigt für jeden möglichen AP-Ankunftsminuten-Slot bis zu 4 hochbewertete Stationen, die per Aircraft Scatter erreichbar wären. Priorisierungskriterien:
|
|
||||||
|
|
||||||
- Bevorzugt werden APs mit dem **höchsten Reflexionspotenzial** (nicht unbedingt die schnellste Ankunft).
|
|
||||||
- Stationen, auf die die eigene Antenne nicht zeigt, werden **transparent** dargestellt.
|
|
||||||
|
|
||||||
So kann der Contest-Operator auf einem Blick sehen, welche Stationen wann und über welche Flugzeuge erreichbar sein werden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Intervall-Beacon
|
|
||||||
|
|
||||||
Automatische CQ-Meldungen im öffentlichen Kanal in konfigurierbarem Intervall. Empfohlene Verwendung mit der Variable `MYQRG` für aktuelle Frequenzangabe. Details: [Konfiguration – Beacon Settings](Konfiguration#beacon-settings-automatischer-beacon).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Simplelogfile
|
|
||||||
|
|
||||||
Dateibasierte Log-Auswertung per Regex. Details: [Log-Synchronisation](Log-Synchronisation#methode-1-universal-file-based-callsign-interpreter-simplelogfile).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Cluster & QSO der anderen
|
|
||||||
|
|
||||||
Ein separates Fenster zeigt den QSO-Fluss zwischen anderen Stationen. Besonders interessant in ruhigeren Nacht-Stunden während des Contests, wenn weniger Verkehr herrscht.
|
|
||||||
|
|
||||||
Dieses Fenster kann miniaturisiert werden, wenn es nicht benötigt wird. Zukünftig geplant: Filterung auf Stationen im ausgewählten QTF.
|
|
||||||
@@ -1,51 +0,0 @@
|
|||||||
# KST4Contest – Wiki
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Home) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
**KST4Contest** (auch bekannt als *PraktiKST*) ist ein Java-basierter Chat-Client für den [ON4KST-Chat](http://www.on4kst.info/chat/), der speziell für den Contest-Betrieb auf den VHF/UHF/SHF-Bändern (144 MHz und aufwärts) entwickelt wurde.
|
|
||||||
|
|
||||||
Entwickelt von **DO5AMF (Marc Fröhlich)**, Operator bei DM5M.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Schnellnavigation
|
|
||||||
|
|
||||||
| Seite | Inhalt |
|
|
||||||
|---|---|
|
|
||||||
| [Installation](de-Installation) | Download, Java-Voraussetzungen, Update |
|
|
||||||
| [Konfiguration](de-Konfiguration) | Alle Einstellungen im Detail |
|
|
||||||
| [Log-Synchronisation](de-Log-Synchronisation) | UCXLog, N1MM+, QARTest, DXLog.net, WinTest |
|
|
||||||
| [AirScout-Integration](de-AirScout-Integration) | Flugzeug-Scatter-Erkennung |
|
|
||||||
| [DX-Cluster-Server](de-DX-Cluster-Server) | Integrierter DX-Cluster für das Log-Programm |
|
|
||||||
| [Funktionen](de-Funktionen) | Alle Features im Überblick |
|
|
||||||
| [Makros und Variablen](de-Makros-und-Variablen) | Text-Snippets, Shortcuts, Variablen |
|
|
||||||
| [Benutzeroberfläche](de-Benutzeroberflaeche) | UI-Erklärung und Bedienung |
|
|
||||||
| [Changelog](de-Changelog) | Versionsgeschichte |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Was ist KST4Contest?
|
|
||||||
|
|
||||||
Der ON4KST-Chat ist der De-facto-Standard für Skeds auf den 144-MHz-und-höher-Bändern. KST4Contest erweitert die Chat-Nutzung um contest-spezifische Funktionen:
|
|
||||||
|
|
||||||
- **Worked-Markierung**: Bereits gearbeitete Stationen werden farblich markiert, direkt aus dem Logprogramm via UDP synchronisiert.
|
|
||||||
- **Sked-Richtungs-Erkennung**: Wenn eine Station eine andere aus deiner Richtung anruft, wird sie grün und fett hervorgehoben.
|
|
||||||
- **QRG-Erkennung**: KST4Contest liest Frequenzen automatisch aus dem Chat-Verkehr und zeigt sie in der Benutzerliste an.
|
|
||||||
- **AirScout-Interface**: Anzeige reflektierbarer Flugzeuge direkt in der Benutzerliste.
|
|
||||||
- **Integrierter DX-Cluster-Server**: Spots werden direkt an das Logprogramm gesendet.
|
|
||||||
- **Dark Mode** (ab v1.26): Schont die Augen in der Nacht.
|
|
||||||
- **Multi-Channel-Login** (ab v1.26): Gleichzeitig in zwei Chat-Kategorien einloggen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Kontakt & Support
|
|
||||||
|
|
||||||
- **E-Mail**: praktimarc+kst4contest@gmail.com *(nur für kst4contest-Themen)*
|
|
||||||
- **GitHub**: https://github.com/praktimarc/kst4contest
|
|
||||||
- **Download**: https://github.com/praktimarc/kst4contest/releases/latest
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Danksagungen
|
|
||||||
|
|
||||||
Besonderer Dank gilt: Gianluca Costantino (IU3OAR), Alessandro Murador (IZ3VTH), Reczetár István (HA1FV), OM0AAO (Viliam Petrik, DX-Cluster-Idee), DC9DJ (Konrad Neitzel, Projektstruktur), DO5ALF (Andreas, Webmaster funkerportal.de), PE0WGA (Franz van Velzen, Tester) sowie allen weiteren Testern und Ideengebern.
|
|
||||||
@@ -1,114 +0,0 @@
|
|||||||
# Installation
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Installation) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
## Voraussetzungen
|
|
||||||
|
|
||||||
Es wird eine Mindestauflösung von 1200px mal 720px empfohlen
|
|
||||||
|
|
||||||
### ON4KST-Account
|
|
||||||
|
|
||||||
Um den Chat zu nutzen, ist ein registrierter Account beim ON4KST-Chat-Dienst erforderlich:
|
|
||||||
|
|
||||||
- Registrierung unter: http://www.on4kst.info/chat/register.php
|
|
||||||
|
|
||||||
### Verhaltensregeln im Chat
|
|
||||||
|
|
||||||
Die offizielle Sprache im ON4KST-Chat ist **Englisch**. Auch bei Kommunikation mit Stationen aus dem eigenen Land bitte Englisch verwenden. Übliche HAM-Abkürzungen (agn, dir, pse, rrr, tnx, 73 …) sind gang und gäbe.
|
|
||||||
|
|
||||||
### Persönliche Nachrichten
|
|
||||||
|
|
||||||
Um eine Privatnachricht an eine andere Station zu senden, immer folgendes Format verwenden:
|
|
||||||
|
|
||||||
```
|
|
||||||
/CQ RUFZEICHEN Nachrichtentext
|
|
||||||
```
|
|
||||||
|
|
||||||
Beispiel: `/CQ DL5ASG pse sked 144.205?`
|
|
||||||
|
|
||||||
Bei starkem Chat-Verkehr (5–6 Nachrichten pro Sekunde im Contest) gehen öffentliche Nachrichten, die an ein bestimmtes Rufzeichen gerichtet sind, leicht unter. KST4Contest fängt solche Nachrichten aber auch dann ab, wenn sie fälschlicherweise öffentlich gepostet werden (siehe [Funktionen – PM-Abfang](Funktionen#catching-personal-messages)).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Download
|
|
||||||
|
|
||||||
### Windows
|
|
||||||
|
|
||||||
Die aktuelle Version kann als ZIP-Datei heruntergeladen werden:
|
|
||||||
|
|
||||||
**https://github.com/praktimarc/kst4contest/releases/latest**
|
|
||||||
|
|
||||||
Der Dateiname hat das Format `praktiKST-v<Versionsnummer>-windows-x64.zip `.
|
|
||||||
|
|
||||||
### Linux
|
|
||||||
|
|
||||||
Die aktuelle Version kann als AppImage heruntergeladen werden:
|
|
||||||
|
|
||||||
**https://github.com/praktimarc/kst4contest/releases/latest**
|
|
||||||
|
|
||||||
Der Dateiname hat das Format `praktiKST-v<Versionsnummer>-linux-x86_64.AppImage`.
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Installation
|
|
||||||
|
|
||||||
### Windows
|
|
||||||
|
|
||||||
1. ZIP-Datei herunterladen.
|
|
||||||
2. ZIP-Datei in einen gewünschten Ordner entpacken.
|
|
||||||
3. `praktiKST.exe` ausführen.
|
|
||||||
|
|
||||||
Die Einstellungen werden unter `%USERPROFILE%\.praktikst\preferences.xml` gespeichert.
|
|
||||||
|
|
||||||
### Linux
|
|
||||||
1. AppImage herunterladen.
|
|
||||||
2. AppImage in gewünschten Ordner entpacken.
|
|
||||||
3. AppImage ausführbar machen (geht im Terminal mit `chmod +x praktiKST-v<Versionsnummer>-linux-x86_64.AppImage`)
|
|
||||||
4. AppImage ausführen.
|
|
||||||
|
|
||||||
Die Einstellungen werden unter `~/.praktikst/preferences.xml` gespeichert.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Update
|
|
||||||
|
|
||||||
KST4Contest enthält einen **automatischen Update-Hinweis-Dienst**: Sobald eine neue Version verfügbar ist, erscheint beim Start ein Fenster mit:
|
|
||||||
- der Information, dass eine neue Version vorliegt,
|
|
||||||
- einem Changelog,
|
|
||||||
- dem Download-Link zur neuen Version.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Update-Prozess
|
|
||||||
|
|
||||||
#### Windows
|
|
||||||
|
|
||||||
Derzeit gibt es nur einen Weg zum Aktualisieren:
|
|
||||||
|
|
||||||
1. Den alten Ordner löschen.
|
|
||||||
2. Das neue ZIP entpacken.
|
|
||||||
|
|
||||||
Die Einstellungsdatei (`preferences.xml`) bleibt erhalten, da sie im Benutzerordner gespeichert ist – nicht im Programmordner.
|
|
||||||
|
|
||||||
#### Linux
|
|
||||||
|
|
||||||
Derzeit folgendermaßen:
|
|
||||||
1. neues AppImage herunterladen
|
|
||||||
2. neues AppImage ausführbar makieren
|
|
||||||
3. (optional) altes AppImage löschen.
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Bekannte Probleme beim Start
|
|
||||||
|
|
||||||
### Norton 360
|
|
||||||
|
|
||||||
Norton 360 stuft `praktiKST.exe` als gefährlich ein (Fehlalarm). Es muss eine Ausnahme für die Datei eingerichtet werden:
|
|
||||||
|
|
||||||
1. Norton 360 öffnen.
|
|
||||||
2. Sicherheit → Verlauf → Das entsprechende Ereignis suchen.
|
|
||||||
3. „Wiederherstellen & Ausnahme hinzufügen" wählen.
|
|
||||||
|
|
||||||
*(Gemeldet von PE0WGA, Franz van Velzen – danke!)*
|
|
||||||
@@ -1,200 +0,0 @@
|
|||||||
# Konfiguration
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Configuration) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
Nach dem ersten Start öffnet sich das **Einstellungsfenster** – dieses ist der zentrale Ausgangspunkt für alle Konfigurationen. Es empfiehlt sich, das Einstellungsfenster während des Betriebs geöffnet zu lassen (z. B. um den Beacon schnell ein- und auszuschalten).
|
|
||||||
|
|
||||||
> **Wichtig**: Nach jeder Änderung unbedingt **„Save Settings"** klicken! Die Einstellungen werden unter Linux in `~/.praktikst/preferences.xml` und unter Windows in `%USERPROFILE%\.praktikst\preferences.xml` (bzw. `C:\Users\<Benutzername>\.praktikst\preferences.xml`) gespeichert. Ab v1.21 werden auch Fenstergrößen und Divider-Positionen beim Speichern gesichert.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Station Settings (Stationseinstellungen)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Login und Chat-Kategorien
|
|
||||||
|
|
||||||
Hier werden die Zugangsdaten für den ON4KST-Chat eingetragen (Rufzeichen und Passwort).
|
|
||||||
Zudem wird die **primäre Chat-Kategorie** (z. B. IARU Region 1 VHF/Microwave) ausgewählt.
|
|
||||||
|
|
||||||
Mit der Option für einen **zweiten Chat** (Multi-Channel-Login) kann man sich gleichzeitig in eine weitere Kategorie (z. B. UHF/SHF) einloggen. Beide Chats werden dann parallel überwacht. Hier kann optional auch ein abweichender Login-Name für den zweiten Chat vergeben werden (nützlich für Opposite Station Multi-Callsign Logging).
|
|
||||||
|
|
||||||
### Rufzeichen und Locator
|
|
||||||
|
|
||||||
Eigenes Rufzeichen und Maidenhead-Locator (6-stellig, z. B. `JN49IJ`) eintragen. Diese Werte werden für Distanz- und Richtungsberechnungen benötigt.
|
|
||||||
|
|
||||||
### Aktivierte Bänder
|
|
||||||
|
|
||||||
Über die **„my station uses band"**-Checkboxen werden die aktiven Bänder ausgewählt. Nur für ausgewählte Bänder erscheinen Schaltflächen und Tabellenzeilen in der Benutzeroberfläche. Nach Änderungen muss die Software neu gestartet werden.
|
|
||||||
|
|
||||||
### Antennen-Öffnungswinkel (Antenna Beamwidth)
|
|
||||||
|
|
||||||
Einen realistischen Wert für den Öffnungswinkel der eigenen Antenne eintragen (in Grad). Dieser Wert wird für die [Sked-Richtungs-Hervorhebung](Funktionen#sked-richtungs-hervorhebung) verwendet. Ein Testwert von 50° hat sich bewährt; DM5M nutzt Quads mit 69°.
|
|
||||||
|
|
||||||
> **Keinesfalls** Fantasy-Werte eintragen – die Richtungsberechnungen werden sonst unbrauchbar.
|
|
||||||
|
|
||||||
### Standard-Maximum-QRB
|
|
||||||
|
|
||||||
Maximale Entfernung (in km), für die Richtungs-Warnungen ausgelöst werden sollen. Realistischer Wert für DM5M: 900 km. Stationen, die weiter entfernt sind, werden für Highlighting-Zwecke ignoriert.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Server-Einstellungen (ab v1.31)
|
|
||||||
|
|
||||||
Der Chat-Server-DNS und -Port sind in den Preferences konfigurierbar:
|
|
||||||
|
|
||||||
- **Server-DNS**: Standard `www.on4kst.org` (ab v1.31 geändert von `www.on4kst.info`).
|
|
||||||
- **Port**: Standardport des ON4KST-Servers.
|
|
||||||
|
|
||||||
Eine Änderung ist nur notwendig, wenn der Server umzieht oder ein alternativer Endpunkt genutzt wird.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Log-Sync-Einstellungen
|
|
||||||
|
|
||||||
Drei Methoden stehen zur Verfügung, um gearbeitete Stationen automatisch zu markieren. Details: [Log-Synchronisation](de-Log-Synchronisation).
|
|
||||||
|
|
||||||
### Universal File Based Callsign Interpreter (Simplelogfile)
|
|
||||||
|
|
||||||
Interpretiert beliebige Log-Dateien per Regex nach Rufzeichen-Mustern. Keine Bandinformation möglich. Geeignet als Fallback oder für nicht direkt unterstützte Logprogramme.
|
|
||||||
|
|
||||||
### Netzwerk-Listener für QSO-UDP-Broadcast
|
|
||||||
|
|
||||||
**Empfohlene Methode.** KST4Contest hört auf UDP-Pakete, die das Logprogramm beim Speichern eines QSOs an die Broadcast-Adresse sendet. Die Stationen werden mit Bandinformation markiert. UDP-Port: Standard **12060**. (Wird z. B. von UCXLog, N1MM+, QARTest, DXLog.net genutzt).
|
|
||||||
|
|
||||||
### Win-Test Network-Listener (Zusätzlicher UDP-Listener)
|
|
||||||
|
|
||||||
Dedizierter Netzwerk-Erkenner für Win-Test. KST4Contest empfängt und verarbeitet Win-Test-spezifische UDP-Pakete (inkl. Sked-Übergabe) auf dem dafür konfigurierten Port.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## TRX-Sync-Einstellungen
|
|
||||||
|
|
||||||
Empfängt die aktuelle Frequenz des Transceivers vom Logprogramm via UDP. Ermöglicht die automatische Befüllung der Variable `MYQRG`. Nützlich für:
|
|
||||||
|
|
||||||
- Schnelles Einfügen der eigenen QRG in Chat-Nachrichten.
|
|
||||||
- Automatische CQ-Baken mit aktueller Frequenz.
|
|
||||||
|
|
||||||
> **Hinweis für Multi-Setup**: Wenn zwei Logprogramme an zwei Computern betrieben werden, aber nur eine KST4Contest-Instanz, darf nur ein Logprogramm die Frequenzpakete senden. KST4Contest kann nicht zwischen den Quellen unterscheiden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AirScout-Einstellungen
|
|
||||||
|
|
||||||
Konfiguration der Schnittstelle zu AirScout für die Flugzeug-Scatter-Erkennung. Details: [AirScout-Integration](de-AirScout-Integration).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Notification Settings (Benachrichtigungen)
|
|
||||||
|
|
||||||
Drei Benachrichtigungstypen stehen zur Wahl:
|
|
||||||
|
|
||||||
1. **Einfache Sounds**: TADA-Sound für eingehende Nachrichten, Tick für Sked-Richtungserkennung usw.
|
|
||||||
2. **CW-Ansage**: Das Rufzeichen einer Station, die eine Privatnachricht sendet, wird als CW-Signal ausgegeben.
|
|
||||||
3. **Phonetische Ansage**: Das Rufzeichen wird phonetisch ausgesprochen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Shortcut Settings (Schnellzugriff-Schaltflächen)
|
|
||||||
|
|
||||||
Konfiguration von Schnellzugriff-Schaltflächen, die direkt im Hauptfenster erscheinen. Ein Klick auf eine Schaltfläche fügt den konfigurierten Text in das Sendfeld ein. Alle [Variablen](Makros-und-Variablen#variablen) können verwendet werden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Snippet Settings (Text-Snippets)
|
|
||||||
|
|
||||||
Text-Snippets sind über folgende Wege abrufbar:
|
|
||||||
|
|
||||||
- **Rechtsklick** auf ein Rufzeichen in der Benutzerliste
|
|
||||||
- **Rechtsklick** in der CQ-Nachrichtentabelle
|
|
||||||
- **Rechtsklick** in der PM-Nachrichtentabelle
|
|
||||||
- **Tastenkombinationen**: `Ctrl+1` bis `Ctrl+0` für die ersten 10 Snippets
|
|
||||||
|
|
||||||
Wenn in der Benutzerliste ein Rufzeichen ausgewählt ist, wird der Snippet als Direktnachricht adressiert:
|
|
||||||
`/CQ RUFZEICHEN <Snippet-Text>`
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Beacon Settings (Automatischer Beacon)
|
|
||||||
|
|
||||||
Konfiguration eines automatischen Intervall-Beacons im öffentlichen Chat-Kanal. Empfohlen: Variable `MYQRG` im Text verwenden, damit die aktuelle Frequenz immer aktuell ist. Intervall und Text sind frei konfigurierbar.
|
|
||||||
|
|
||||||
> **Tipp**: Beacon beim CQ-Rufen aktivieren und im Einstellungsfenster schnell deaktivieren, wenn kein CQ gerufen wird.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Messagehandling Settings (ab v1.25)
|
|
||||||
|
|
||||||
Neuer Einstellungsbereich mit folgenden Optionen:
|
|
||||||
|
|
||||||
- **Auto-Antwort auf alle eingehenden Nachrichten**: Automatische Antwort auf Privatnachrichten konfigurierbar.
|
|
||||||
- **Auto-Antwort mit eigener CQ-QRG**: Wenn jemand nach der eigenen QRG fragt, antwortet KST4Contest automatisch mit dem Inhalt der `MYQRG`-Variable.
|
|
||||||
- **Standard-Filter für das Userinfo-Fenster**: Voreingestellter Nachrichtenfilter für das Stationsinfo-Fenster konfigurierbar *(für Gianluca :-) )*.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Win-Test-Netzwerk-Listener (ab v1.31)
|
|
||||||
|
|
||||||
Dedizierter Empfänger für Win-Test-spezifische UDP-Pakete. Ermöglicht:
|
|
||||||
|
|
||||||
- **Log-Synchronisation**: Gearbeitete Stationen werden aus Win-Test übernommen und in der Benutzerliste markiert.
|
|
||||||
- **Frequenz-Auswertung**: Die aktuelle TRX-Frequenz aus Win-Test befüllt die `MYQRG`-Variable.
|
|
||||||
- **Sked-Übergabe (SKED Push)**: Skeds aus KST4Contest werden via UDP direkt an Win-Test übergeben. Der UDP-Broadcast-Standardport von Win-Test (9871) wird verwendet.
|
|
||||||
|
|
||||||
Einstellungen:
|
|
||||||
- **Aktivieren/Deaktivieren**: Checkbox in den Preferences (ab v1.40).
|
|
||||||
- **Port**: Konfigurierbarer UDP-Port für den Win-Test-Listener.
|
|
||||||
- **Sked-UDP-Adresse und Port**: Zieladresse und Port für die SKED-Übergabe an Win-Test.
|
|
||||||
|
|
||||||
> **Hinweis**: Der Win-Test-Listener ist ein **zusätzlicher** Listener – der Standard-QSO-UDP-Broadcast-Listener auf Port 12060 bleibt davon unabhängig.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## PSTRotator-Einstellungen (ab v1.31)
|
|
||||||
|
|
||||||
KST4Contest kann die Antennenrichtung über PSTRotator steuern.
|
|
||||||
|
|
||||||
Einstellungen:
|
|
||||||
- **Aktivieren/Deaktivieren**: Checkbox in den Preferences (ab v1.40).
|
|
||||||
- **IP-Adresse**: IP-Adresse des PSTRotator-Rechners (Standard: `127.0.0.1` bei Betrieb auf demselben PC).
|
|
||||||
- **Port**: Kommunikationsport von PSTRotator.
|
|
||||||
|
|
||||||
> **Hinweis**: Nach einem Klick auf den Richtungs-Button wartet KST4Contest kurz auf die Rotatorantwort. Bei langsamen Rotoren (z. B. SPID) kann es zu einer kleinen Verzögerung kommen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sniffer-Einstellungen (ab v1.31)
|
|
||||||
|
|
||||||
Der QSO-Sniffer filtert Chat-Nachrichten von konfigurierbaren Rufzeichen und leitet sie ins PM-Fenster weiter.
|
|
||||||
|
|
||||||
Einstellungen:
|
|
||||||
- **Rufzeichen-Liste**: Kommagetrennte Liste von Rufzeichen, deren Nachrichten immer in das PM-Fenster weitergeleitet werden sollen.
|
|
||||||
|
|
||||||
Anwendungsfall: Wichtige Stationen (z. B. DX-Peditionen oder feste Verbündete im Contest) im Auge behalten, ohne den Haupt-Chat ständig zu beobachten.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked Station Database Settings (Gearbeitete-Stationen-Datenbank)
|
|
||||||
|
|
||||||
Die interne Worked-Datenbank enthält:
|
|
||||||
|
|
||||||
- Worked-Status aller Stationen (pro Band)
|
|
||||||
- NOT-QRV-Tags (seit v1.2)
|
|
||||||
|
|
||||||
**Ab v1.40**: Einträge haben eine automatische Lebensdauer von **3 Tagen** – ein manuelles Zurücksetzen vor jedem Contest ist nicht mehr zwingend notwendig. Für ein vollständiges Reset kann trotzdem die Schaltfläche **„Reinitialize"** verwendet werden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Dark Mode (ab v1.26)
|
|
||||||
|
|
||||||
Umschaltbar über das Menü: **Window → Use Dark Mode**. Die Farben können über CSS individuell angepasst werden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Einstellungen speichern
|
|
||||||
|
|
||||||
Nach **jeder** Änderung **„Save Settings"** klicken! Ohne Speichern gehen alle Änderungen beim nächsten Start verloren.
|
|
||||||
|
|
||||||
- Speicherort: unter Linux `~/.praktikst/preferences.xml` und unter Windows `%USERPROFILE%\.praktikst\preferences.xml` (bzw. `C:\Users\<Benutzername>\.praktikst\preferences.xml`)
|
|
||||||
- Ab v1.21: Fenstergrößen und Divider-Positionen werden ebenfalls gespeichert.
|
|
||||||
- Bei Problemen: Konfigurationsdatei löschen → KST4Contest erstellt eine neue mit Standardwerten.
|
|
||||||
@@ -1,138 +0,0 @@
|
|||||||
# Log-Synchronisation
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Log-Sync) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
KST4Contest markiert gearbeitete Stationen automatisch in der Chat-Benutzerliste. Dafür gibt es zwei grundlegende Methoden:
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Methode 1: Universal File Based Callsign Interpreter (Simplelogfile)
|
|
||||||
|
|
||||||
KST4Contest liest eine Log-Datei und sucht mittels regulärem Ausdruck nach Rufzeichen-Mustern. Dabei werden auch binäre Logdateien unterstützt – unlesbarer Binärinhalt wird einfach ignoriert.
|
|
||||||
|
|
||||||
**Vorteil**: Funktioniert mit nahezu jedem Logprogramm, das eine Datei schreibt.
|
|
||||||
**Nachteil**: Keine Bandinformation möglich – es wird nur „gearbeitet" markiert, nicht auf welchem Band.
|
|
||||||
|
|
||||||
Pfad der Log-Datei in den Preferences eintragen. Die Datei wird nur gelesen, nie verändert (read-only).
|
|
||||||
|
|
||||||
> **Tipp**: Die Simplelogfile-Funktion kann auch genutzt werden, um Stationen zu markieren, die definitiv nicht erreichbar sind (z. B. eigene Notizen). Das wird in einer späteren Version durch ein besseres Tagging-System ersetzt.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Methode 2: Netzwerk-Listener (UDP-Broadcast) – Empfohlen
|
|
||||||
|
|
||||||
Das Logprogramm sendet beim Speichern eines QSOs ein UDP-Paket an die Broadcast-Adresse des Heimnetzwerks. KST4Contest empfängt dieses Paket und markiert die Station inklusive **Bandinformation** in der internen SQLite-Datenbank.
|
|
||||||
|
|
||||||
> **Wichtig**: KST4Contest muss **parallel zum Logprogramm laufen**. QSOs, die während einer Abwesenheit von KST4Contest geloggt werden, werden nicht erfasst – außer bei QARTest (kann das komplette Log senden).
|
|
||||||
|
|
||||||
**Standard UDP-Port**: 12060 (entspricht dem Standard der meisten Logprogramme)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Unterstützte Logprogramme
|
|
||||||
|
|
||||||
### UCXLog (DL7UCX)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
UCXLog sendet QSO-UDP-Pakete und Transceiver-Frequenzpakete.
|
|
||||||
|
|
||||||
**Einstellungen in UCXLog:**
|
|
||||||
- UDP-Broadcast aktivieren
|
|
||||||
- IP-Adresse des KST4Contest-Computers eintragen (bei lokalem Betrieb: `127.0.0.1`)
|
|
||||||
- Port: 12060 (Standard)
|
|
||||||
|
|
||||||
Grün markierte Felder in den UCXLog-Einstellungen beachten: IP und Port müssen eingetragen werden.
|
|
||||||
|
|
||||||
Hinweis für Multi-Setup (2 Computer, 2 Radios, eine KST4Contest-Instanz): Beide Logprogramme müssen die QSO-Pakete an die IP des KST4Contest-Computers senden. Dann ist mindestens eine IP nicht `127.0.0.1`.
|
|
||||||
|
|
||||||
### QARTest (IK3QAR)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Besonderheit**: QARTest kann das **vollständige Log** an KST4Contest senden (Schaltfläche „Invia log completo" in den QARTest-Einstellungen). Damit werden auch QSOs erfasst, die vor dem Start von KST4Contest geloggt wurden.
|
|
||||||
|
|
||||||
**Einstellungen in QARTest:**
|
|
||||||
- UDP-Broadcast und IP/Port wie UCXLog konfigurieren
|
|
||||||
- „Invia log completo" für den vollständigen Log-Upload verwenden
|
|
||||||
|
|
||||||
*(„Buona funzionalità caro IK3QAR!" – DO5AMF)*
|
|
||||||
|
|
||||||
### N1MM+
|
|
||||||
|
|
||||||
**Einstellungen in N1MM+:**
|
|
||||||
|
|
||||||
In N1MM+ unter `Config → Configure Ports, Mode Control, Winkey, etc. → Broadcast Data`:
|
|
||||||
- `Radio Info` aktivieren (für TRX-Sync/QRG)
|
|
||||||
- `Contact Info` aktivieren (für QSO-Sync)
|
|
||||||
- IP: `127.0.0.1` (oder IP des KST4Contest-Computers)
|
|
||||||
- Port: 12060
|
|
||||||
|
|
||||||
Für den integrierten DX-Cluster-Server: N1MM+ als DX-Cluster-Client konfigurieren (Server: `127.0.0.1`, Port wie in KST4Contest eingestellt).
|
|
||||||
|
|
||||||
### DXLog.net
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Einstellungen in DXLog.net:**
|
|
||||||
- UDP-Broadcast aktivieren
|
|
||||||
- IP des KST4Contest-Computers eintragen (grün markierte Felder)
|
|
||||||
- Port: 12060
|
|
||||||
|
|
||||||
### Win-Test
|
|
||||||
|
|
||||||
Win-Test wird mit einem dedizierten UDP-Netzwerk-Listener unterstützt, der das native Win-Test Netzwerkprotokoll versteht.
|
|
||||||
|
|
||||||
**Vorteile der Win-Test Integration:**
|
|
||||||
- Automatische QSO-Synchronisation zur Markierung gearbeiteter Stationen.
|
|
||||||
- **Sked-Übergabe (ADDSKED):** Über den Button "Create sked" im Stationsinfo-Panel wird nicht nur in KST4Contest ein Sked angelegt, sondern dieses auch *direkt per UDP an das Win-Test Netzwerk als ADDSKED-Paket gesendet*.
|
|
||||||
- Es kann zwischen den Sked-Modi "AUTO", "SSB" oder "CW" gewählt werden.
|
|
||||||
|
|
||||||
**Notwendige Einstellungen in KST4Contest:**
|
|
||||||
- `UDP-Port for Win-Test listener` (Standard: 9871).
|
|
||||||
- `Receive Win-Test network based UDP log messages` aktivieren.
|
|
||||||
- `Win-Test sked transmission (push via ADDSKED to Win-Test network)` aktivieren.
|
|
||||||
- `KST station name in Win-Test network (src of SKED packets)`: Legt fest, unter welchem Stationsnamen KST4Contest im WT-Netzwerk auftritt (z.B. "KST").
|
|
||||||
- `Win-Test station name filter`: Wenn hier ein Name eingetragen wird (z.B. "STN1"), werden nur QSOs von dieser bestimmten Win-Test Instanz verarbeitet. Leer lassen, um alle zu akzeptieren.
|
|
||||||
- `Win-Test network broadcast address`: Wird idR automatisch erkannt und ist erforderlich, um die Sked-Pakete ins Netzwerk zu senden.
|
|
||||||
|
|
||||||
**Einstellungen in Win-Test:**
|
|
||||||
- Das Netzwerk in Win-Test muss aktiv sein.
|
|
||||||
- Win-Test muss so konfiguriert sein, dass es seine Broadcasts an den entsprechenden Port (Standard 9871) sendet bzw. empfängt.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## TRX-Frequenz-Synchronisation
|
|
||||||
|
|
||||||
Neben der QSO-Synchronisation übertragen UCXLog und andere Programme auch die **aktuelle Transceiverfrequenz** via UDP. KST4Contest verarbeitet diese Information und stellt sie als Variable `MYQRG` bereit.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Ergebnis**: Die eigene QRG muss im Chat nie mehr manuell eingegeben werden – ein Klick auf den MYQRG-Button oder die Verwendung der Variable im Beacon genügt.
|
|
||||||
|
|
||||||
> **Hinweis für Multi-Setup**: Bei zwei Logprogrammen an zwei Computern sollte nur **eines** die Frequenzpakete senden. KST4Contest kann nicht zwischen den Quellen unterscheiden und verarbeitet alle eingehenden Pakete.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multi-Setup: 2 Radios, 2 Computer
|
|
||||||
|
|
||||||
Für DM5M-typische Setups (2 Radios, 2 Computer, eine KST4Contest-Instanz oder zwei separate):
|
|
||||||
|
|
||||||
**Variante A – Eine gemeinsame KST4Contest-Instanz:**
|
|
||||||
- Beide Logprogramme senden QSO-Pakete an die IP des KST4Contest-Computers
|
|
||||||
- Nur ein Logprogramm sendet Frequenzpakete (empfohlen: das VHF-Logprogramm)
|
|
||||||
|
|
||||||
**Variante B – Zwei separate KST4Contest-Instanzen (empfohlen):**
|
|
||||||
- Jedes Logprogramm kommuniziert mit seiner eigenen KST4Contest-Instanz via `127.0.0.1`
|
|
||||||
- Zwei separate Chat-Logins
|
|
||||||
- Bessere Trennung und weniger Konflikte
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Interne Datenbank
|
|
||||||
|
|
||||||
KST4Contest speichert die Worked-Information in einer internen **SQLite-Datenbank**. Diese ist von der Logprogramm-Datenbank unabhängig und wird nur über den UDP-Broadcast befüllt.
|
|
||||||
|
|
||||||
Vor jedem neuen Contest: Datenbank zurücksetzen! → [Konfiguration – Worked Station Database Settings](Konfiguration#worked-station-database-settings)
|
|
||||||
@@ -1,162 +0,0 @@
|
|||||||
# Makros und Variablen
|
|
||||||
|
|
||||||
> 🇬🇧 [English version](en-Macros-and-Variables) | 🇩🇪 Du liest gerade die deutsche Version
|
|
||||||
|
|
||||||
KST4Contest bietet ein flexibles System aus Text-Snippets, Shortcuts und eingebauten Variablen, die den Chat-Workflow im Contest erheblich beschleunigen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Überblick
|
|
||||||
|
|
||||||
| Typ | Aufruf | Zweck |
|
|
||||||
|---|---|---|
|
|
||||||
| **Shortcuts** | Button in der Toolbar | Schneller Text-Insert ins Sendfeld |
|
|
||||||
| **Snippets** | Rechtsklick / Ctrl+1..0 | Text-Bausteine, optionaler PM-Versand |
|
|
||||||
| **Variablen** | In allen Text-Feldern verwendbar | Dynamische Werte (QRG, Locator, AP-Daten) |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Shortcuts (Schnellzugriff-Schaltflächen)
|
|
||||||
|
|
||||||
Konfigurierbar in den Preferences → **Shortcut Settings**.
|
|
||||||
|
|
||||||
- Jeder konfigurierte Text erzeugt **einen Button** in der Benutzeroberfläche.
|
|
||||||
- Ein Klick fügt den Text in das **Sendfeld** ein.
|
|
||||||
- **Alle Variablen** können in Shortcuts verwendet werden und werden beim Einfügen sofort aufgelöst.
|
|
||||||
- Auch längere Texte möglich.
|
|
||||||
|
|
||||||
**Tipp**: Häufig verwendete Abkürzungen wie „pse", „rrr", „tnx", „73" als Shortcuts anlegen.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Snippets (Text-Bausteine)
|
|
||||||
|
|
||||||
Konfigurierbar in den Preferences → **Snippet Settings**.
|
|
||||||
|
|
||||||
### Aufruf
|
|
||||||
|
|
||||||
- **Rechtsklick** auf ein Rufzeichen in der Benutzerliste
|
|
||||||
- **Rechtsklick** in der CQ-Nachrichtentabelle
|
|
||||||
- **Rechtsklick** in der PM-Nachrichtentabelle
|
|
||||||
- **Tastaturkürzel**: `Ctrl+1` bis `Ctrl+0` für die ersten 10 Snippets
|
|
||||||
|
|
||||||
### Verhalten mit ausgewähltem Rufzeichen
|
|
||||||
|
|
||||||
Wenn in der Benutzerliste ein Rufzeichen ausgewählt ist, wird der Snippet als **Privatnachricht** adressiert:
|
|
||||||
|
|
||||||
```
|
|
||||||
/CQ RUFZEICHEN <Snippet-Text>
|
|
||||||
```
|
|
||||||
|
|
||||||
Anschließend kann mit **Enter** direkt gesendet werden – auch wenn das Sendfeld nicht den Fokus hat.
|
|
||||||
|
|
||||||
### Hardware-Makro-Tastatur
|
|
||||||
|
|
||||||
*(Idee von IU3OAR, Gianluca Costantino)*
|
|
||||||
|
|
||||||
Die Tastenkombinationen `Ctrl+1` bis `Ctrl+0` können auf einer programmierbaren Makro-Tastatur belegt werden. Ein weiterer Tastendruck (auf eine „Enter"-Taste) sendet den Text sofort. Im Contest-Betrieb spart das erheblich Zeit.
|
|
||||||
|
|
||||||
### Vordefinierte Standard-Snippets
|
|
||||||
|
|
||||||
Beim ersten Start werden einige Snippets vorbelegt, z. B.:
|
|
||||||
|
|
||||||
- `Hi OM, try sked?`
|
|
||||||
- `I am calling cq ur dir, pse lsn to me at MYQRG`
|
|
||||||
- `pse ur qrg?`
|
|
||||||
- `rrr, I move to your qrg nw, pse ant dir me`
|
|
||||||
|
|
||||||
Diese können in den Preferences angepasst oder gelöscht werden.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Variablen
|
|
||||||
|
|
||||||
Variablen werden in geschriebenen Texten (Snippets, Shortcuts, Beacon, Sendfeld) durch ihre aktuellen Werte ersetzt. Einfach den Variablennamen **großgeschrieben** in den Text einfügen.
|
|
||||||
|
|
||||||
### MYQRG
|
|
||||||
|
|
||||||
Wird durch die aktuelle Transceiverfrequenz ersetzt.
|
|
||||||
|
|
||||||
- Quelle: TRX-Sync via UDP vom Logprogramm (wenn aktiviert)
|
|
||||||
- Fallback: Manuell eingetragener Wert im MYQRG-Textfeld rechts neben dem Sendbutton
|
|
||||||
- Format: `144.388.03`
|
|
||||||
|
|
||||||
**Beispiel**: `calling cq at MYQRG` → `calling cq at 144.388.03`
|
|
||||||
|
|
||||||
### MYQRGSHORT
|
|
||||||
|
|
||||||
Wie MYQRG, aber nur die ersten 7 Zeichen.
|
|
||||||
|
|
||||||
- Format: `144.388`
|
|
||||||
|
|
||||||
**Beispiel**: `qrg: MYQRGSHORT` → `qrg: 144.388`
|
|
||||||
|
|
||||||
### MYLOCATOR
|
|
||||||
|
|
||||||
Wird durch den eigenen Maidenhead-Locator (6-stellig) ersetzt.
|
|
||||||
|
|
||||||
- Format: `JO51IJ`
|
|
||||||
|
|
||||||
**Beispiel**: `my loc: MYLOCATOR` → `my loc: JO51IJ`
|
|
||||||
|
|
||||||
### MYLOCATORSHORT
|
|
||||||
|
|
||||||
Wie MYLOCATOR, aber nur die ersten 4 Zeichen.
|
|
||||||
|
|
||||||
- Format: `JO51`
|
|
||||||
|
|
||||||
**Beispiel**: `loc: MYLOCATORSHORT` → `loc: JO51`
|
|
||||||
|
|
||||||
### QRZNAME
|
|
||||||
|
|
||||||
Wird durch den **Namen** der aktuell ausgewählten Station aus dem Chat-Namenfeld ersetzt.
|
|
||||||
|
|
||||||
**Beispiel**: `Hi QRZNAME, sked?` → `Hi Gianluca, sked?`
|
|
||||||
|
|
||||||
### FIRSTAP
|
|
||||||
|
|
||||||
Wird durch Daten des ersten reflektierbaren Flugzeugs zur ausgewählten Station ersetzt (sofern vorhanden).
|
|
||||||
|
|
||||||
- Bedingung: AirScout ist aktiv und ein Flugzeug ist verfügbar.
|
|
||||||
- Format-Beispiel: `a very big AP in 1 min`
|
|
||||||
|
|
||||||
**Beispiel**: `AP info: FIRSTAP` → `AP info: a very big AP in 1 min`
|
|
||||||
|
|
||||||
### SECONDAP
|
|
||||||
|
|
||||||
Wie FIRSTAP, aber für das zweite verfügbare Flugzeug.
|
|
||||||
|
|
||||||
- Format-Beispiel: `Next big AP in 9 min`
|
|
||||||
|
|
||||||
**Beispiel**: `also: SECONDAP` → `also: Next big AP in 9 min`
|
|
||||||
|
|
||||||
### MYQTF *(geplant für v1.3)*
|
|
||||||
|
|
||||||
Wird durch die aktuelle Antennenrichtung in Worten ersetzt (z. B. `north`, `north east`, `east`, …).
|
|
||||||
|
|
||||||
- Quelle: Winkelwert im MYQTF-Eingabefeld (rechts neben dem MYQRG-Feld)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Variablen im Beacon
|
|
||||||
|
|
||||||
Alle Variablen können auch im **automatischen Beacon** (Intervall-Nachrichten) verwendet werden. Empfohlene Beacon-Konfiguration:
|
|
||||||
|
|
||||||
```
|
|
||||||
calling cq at MYQRG, loc MYLOCATOR, GL all!
|
|
||||||
```
|
|
||||||
|
|
||||||
Da KST4Contest QRG-Daten automatisch aus Chat-Nachrichten ausliest: Wenn andere Stationen ebenfalls KST4Contest nutzen, sehen sie die eigene QRG sofort in der QRG-Spalte der Benutzerliste.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Beispiel-Workflow mit Makros im Contest
|
|
||||||
|
|
||||||
1. Station in der Benutzerliste auswählen → Rufzeichen ist nun vorausgewählt.
|
|
||||||
2. `Ctrl+1` drücken → Snippet „Hi OM, try sked?" wird als PM adressiert.
|
|
||||||
3. Enter drücken → Nachricht wird gesendet.
|
|
||||||
4. Station antwortet mit Frequenz → QRG-Spalte wird automatisch befüllt.
|
|
||||||
5. `Ctrl+2` → Snippet „I am calling cq ur dir, pse lsn to me at 144.388" (MYQRG aufgelöst).
|
|
||||||
6. Enter → Gesendet.
|
|
||||||
|
|
||||||
Ohne manuelle Tipparbeit, ohne Fehler, ohne Unterbrechung des CQ-Rufens.
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
@@ -1,116 +0,0 @@
|
|||||||
# AirScout Integration
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-AirScout-Integration)
|
|
||||||
|
|
||||||
AirScout (by DL2ALF) is a program for detecting aircraft for aircraft scatter operation. KST4Contest is tightly integrated with AirScout and shows reflectable aircraft directly in the user list.
|
|
||||||
|
|
||||||
> **Aircraft Scatter** enables very long-distance communication on VHF and higher – even for stations with low altitude above sea level or unfavourable topographic conditions.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Downloading AirScout
|
|
||||||
|
|
||||||
Download AirScout from:
|
|
||||||
- http://airscout.eu/index.php/download
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Aircraft Data Feeds (ADSB)
|
|
||||||
|
|
||||||
Public aircraft data feeds on the internet are often unreliable and limited in use. A recommended alternative is the dedicated ADSB feed service provided by **OV3T (Thomas)**:
|
|
||||||
|
|
||||||
- https://airscatter.dk/
|
|
||||||
- https://www.facebook.com/groups/825093981868542
|
|
||||||
|
|
||||||
An account is required for this service. Please consider donating to Thomas – the server costs are not free!
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Setting Up AirScout
|
|
||||||
|
|
||||||
### Step 1: Configure the ADSB Feed in AirScout
|
|
||||||
|
|
||||||
1. Start AirScout.
|
|
||||||
2. Enter your OV3T feed account details (username, password, URL) in the AirScout settings.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. Test the connection.
|
|
||||||
|
|
||||||
### Step 2: Enable UDP Communication for KST4Contest
|
|
||||||
|
|
||||||
In AirScout, enable the UDP interface:
|
|
||||||
|
|
||||||
- Activate the corresponding checkbox in the AirScout settings (only one checkbox needed).
|
|
||||||
- Do not change the default ports unless there is a specific reason.
|
|
||||||
|
|
||||||
### Step 3: KST4Contest Settings
|
|
||||||
|
|
||||||
In KST4Contest Preferences → **AirScout Settings**:
|
|
||||||
- Enable AirScout communication
|
|
||||||
- Leave IP and port at their default values (unless changed)
|
|
||||||
|
|
||||||
{ width=85% }
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Communication Between KST4Contest and AirScout (from v1.263)
|
|
||||||
|
|
||||||
**Improvement in v1.263**: KST4Contest now only sends stations to AirScout whose QRB (distance) is less than the configured **maximum QRB**. The query interval has been extended from 12 seconds to **60 seconds**.
|
|
||||||
|
|
||||||
**Benefits:**
|
|
||||||
- Significantly less computation load for AirScout
|
|
||||||
- Significantly less message traffic
|
|
||||||
- The tracking issue with the "Show Path in AirScout" button is greatly improved
|
|
||||||
- Less overall CPU usage
|
|
||||||
|
|
||||||
Additionally: The name of the KST4Contest client and AirScout server was previously hardcoded (`KST` and `AS`). From v1.263, the names configured in the Preferences are used.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multiple KST4Contest Instances and AirScout
|
|
||||||
|
|
||||||
> **Note**: If multiple KST4Contest instances are running simultaneously and AirScout communication is enabled on both, AirScout will respond **to both instances**.
|
|
||||||
|
|
||||||
This is not a problem if:
|
|
||||||
- Both instances use the same locator, **or**
|
|
||||||
- Both instances have different login callsigns.
|
|
||||||
|
|
||||||
Otherwise, it may result in incorrect AP data.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AP Column in the User List
|
|
||||||
|
|
||||||
After setup, an **AP column** appears in the user list showing up to two reflectable aircraft per station.
|
|
||||||
|
|
||||||
Example display:
|
|
||||||
|
|
||||||
| Station | AP Info |
|
|
||||||
|---|---|
|
|
||||||
| DF9QX | 2 Planes: 0 min / 0 min, 100% each |
|
|
||||||
| F5DYD | 2 Planes: 14 min / 31 min, 50% each |
|
|
||||||
|
|
||||||
AP information is also available in the **private messages window**.
|
|
||||||
|
|
||||||
The percentage indicates the reflection potential (aircraft size, altitude, distance).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AP Variables in Messages
|
|
||||||
|
|
||||||
Aircraft data can be inserted directly into messages:
|
|
||||||
|
|
||||||
- `FIRSTAP` → e.g. `a very big AP in 1 min`
|
|
||||||
- `SECONDAP` → e.g. `Next big AP in 9 min`
|
|
||||||
|
|
||||||
Details: [Macros and Variables](Macros-and-Variables#variables)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## "Show Path in AirScout" Button
|
|
||||||
|
|
||||||
In the user list there is a button with an arrow showing the direction (QTF) to the selected station. Clicking it maximises AirScout and shows the path with reflectable aircraft to the selected contact.
|
|
||||||
@@ -1,235 +0,0 @@
|
|||||||
# Changelog
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Changelog)
|
|
||||||
|
|
||||||
Version history of KST4Contest / PraktiKST.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
For the latest changelog, please refer to GitHub. The previous changelog is below.
|
|
||||||
|
|
||||||
## v1.40 (2026-02-16)
|
|
||||||
**Major Feature Release: Score System, AP Timeline, Win-Test, PSTRotator**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- **Chatmember Score System**: Every chat member is automatically scored based on antenna direction, activity time, message count, active bands, frequencies, sked direction (degrees), and other factors. Top candidates are highlighted in a dedicated list.
|
|
||||||
- **AP Timeline**: For each minute of possible aircraft arrival, up to 4 highly-scored stations are shown that should be workable. Aircraft with the highest potential are preferred over the fastest arrival. Chat members whose antenna is not pointing towards you are shown transparently.
|
|
||||||
- **Win-Test Support** (Beta since v1.31, now fully configurable): Log synchronisation, frequency parsing and **sked handover via UDP** fully integrated. Can be enabled/disabled in Preferences.
|
|
||||||
- **PSTRotator Interface** (Beta since v1.31, now fully configurable): Rotator position updates directly from KST4Contest. Can be enabled/disabled in Preferences.
|
|
||||||
- **QSO Sniffer**: Messages from configurable callsign lists are automatically forwarded to the PM window.
|
|
||||||
- **Band Alert for logged stations**: When a station is logged, a hint appears if that station has another active band that you are also QRV on.
|
|
||||||
- **Sked Reminder ALERT**: A sked alarm with automatic messages in configurable intervals (2+1 / 5+2+1 / 10+5+2+1 minutes before the sked) can be set up for each chat member, plus acoustic and visual notification.
|
|
||||||
- **Load chat history on startup**: Chat server history is loaded on connect to immediately see active members and recent messages.
|
|
||||||
- **Skedfail button**: In the FurtherInfo panel, a sked failure can be marked for a chat member, which lowers their priority score.
|
|
||||||
|
|
||||||
**Changed:**
|
|
||||||
- AP notes added to internal DX cluster spots.
|
|
||||||
- Chat member table scrolling follows the current message selection automatically.
|
|
||||||
- Generic auto-reply and QRG auto-reply now fire a maximum of once every 45 seconds per callsign (prevents spam and message ping-pong).
|
|
||||||
- New saveable settings: ServerDNS/Port, PSTRotator interface, Win-Test interface, callsign sniffer, Dark Mode on by default.
|
|
||||||
- Date column removed from chat table (time only – saves space).
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- User list now automatically sorted on every new member sign-on.
|
|
||||||
- Posonpill messages now terminate exactly one client instance (no longer affects all instances or wtKST).
|
|
||||||
- wtKST: crash on KST4Contest disconnection fixed.
|
|
||||||
- Multiple issues with callsign suffixes like `/p`, `-2`, etc. fixed throughout.
|
|
||||||
- `QTFDefault` was not saved correctly → fixed.
|
|
||||||
- AirScout watchlist (ASWATCHLIST) was not being updated → fixed.
|
|
||||||
- Dark Mode: QRG fields not displayed at full size → fixed.
|
|
||||||
- Version number display corrected.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.31 (2025-12-13)
|
|
||||||
**Win-Test + PSTRotator Beta, QSO Sniffer, DNS Hotfix**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- **Win-Test support** (Beta, not yet deactivatable): Log synchronisation and frequency parsing.
|
|
||||||
- **PSTRotator support** (Beta, not yet deactivatable).
|
|
||||||
- **QSO Sniffer**: Messages from configurable callsigns are forwarded to the PM window.
|
|
||||||
|
|
||||||
**Changed:**
|
|
||||||
- **DNS server changed**: From `www.on4kst.info` to `www.on4kst.org` (hotfix). The DNS server is now configurable in Preferences.
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Endless loop in error case freezes the client → fixed.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.266 (2025-10-03)
|
|
||||||
**AirScout Fix for Callsigns with Suffix**
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- AirScout interface did not work when the login callsign contained a suffix (e.g. `9A1W-2`). AirScout cannot handle this format – only the base callsign without suffix is now passed to AirScout.
|
|
||||||
|
|
||||||
*(Bug reported and tested by 9A2HM / Kreso – many thanks!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.265 (2025-09-28)
|
|
||||||
**Direction Buttons Stay Coloured When Active**
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Direction buttons (N / NE / E etc.) now keep their highlight colour when activated, making the active state immediately visible.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.264 (2025-08-02)
|
|
||||||
**Simplelogfile: Improved Callsign Recognition**
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Callsigns like `S53CC`, `S51A`, etc. were not being marked as worked in the SimpleLogFile interpreter → recognition pattern improved.
|
|
||||||
|
|
||||||
*(Bug reported by Boris, S53CC – thank you!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.263 (2025-06-08)
|
|
||||||
**AirScout Communication and Login Name**
|
|
||||||
|
|
||||||
**Changed:**
|
|
||||||
- AirScout communication fundamentally revised: Only stations with QRB < max-QRB are now sent to AirScout.
|
|
||||||
- Query interval extended from 12 seconds to **60 seconds**.
|
|
||||||
- Significantly less computation load and message traffic → more stable AirScout tracking.
|
|
||||||
- Name of the AS client and AS server is now configurable from the Preferences (was previously hardcoded to "KST" / "AS").
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- "Track in AirScout" button was very sluggish → greatly improved by new communication logic.
|
|
||||||
- Name in chat is now saveable (bug fixed).
|
|
||||||
- Visual corrections before and after login.
|
|
||||||
- Bug fixed that was reported by 9A2HM (Kreso).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.262 (2025-05-21)
|
|
||||||
**Freeze Fix for Early Message Delivery**
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- ON4KST sometimes delivers messages before login is complete. This caused errors in the message processing engine → now fixed.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.26 (2025-05)
|
|
||||||
**Multi-Channel Login and Dark Mode**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- **Dark Mode**: Toggle via `Window → Use Dark Mode`.
|
|
||||||
- **Multi-channel login**: Simultaneous login to two chat categories.
|
|
||||||
- **Opposite station multi-callsign login tagging**: Support for stations with multiple callsigns.
|
|
||||||
|
|
||||||
**Changed:**
|
|
||||||
- Colouring mechanism revised: Colours can now be customised via CSS.
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Station tagging completely revised and corrected.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.251 (2025-02)
|
|
||||||
**Bugfix for UDP Broadcast Spot Info**
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Problem reading UDP broadcast spot information fixed (reported by Steve Clements – thank you!).
|
|
||||||
- Station tagging (further improved).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.25 (2025-02)
|
|
||||||
**Wishlist Time**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- **New settings tab: Messagehandling**
|
|
||||||
- Auto-reply to incoming messages configurable.
|
|
||||||
- Automatic reply with own CQ QRG when someone asks for it.
|
|
||||||
- Configurable default filter for the userinfo window *(for Gianluca :-) )*.
|
|
||||||
- **Coloured PM rows**: New private messages appear red and fade every 30 seconds from yellow to white *(idea by IU3OAR, Gianluca)*.
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Stations with suffixes like "-2" and "-70" were not being marked as worked → now ignored, station is correctly marked.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.24 (2024-11)
|
|
||||||
**Wishlist + DX Cluster Spots**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- Button to open the **QRZ.com profile** of the selected station.
|
|
||||||
- Button to open the **QRZ-CQ profile** of the selected station.
|
|
||||||
- **DX Cluster Server integration**: Direction warnings are sent as spots to the logging software (when QRG is known).
|
|
||||||
|
|
||||||
*(Coloured PM row feature also added – tnx Gianluca)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.23 (2024-10)
|
|
||||||
**Built-in DX Cluster Server**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- KST4Contest now contains a **built-in DX cluster server**.
|
|
||||||
- Generates DX cluster spots and sends them to the logging software when a direction warning is triggered and a QRG is known.
|
|
||||||
- Spotter callsign must differ from the contest callsign (for correct filtering in the logging software).
|
|
||||||
|
|
||||||
*(Idea by OM0AAO, Viliam Petrik – thank you!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.22 (2024-05)
|
|
||||||
**Usability Improvements and AirScout Button Fix**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- New variables (tnx OM0AAO, Viliam Petrik):
|
|
||||||
- `MYLOCATORSHORT`
|
|
||||||
- `MYQRGSHORT`
|
|
||||||
- `QRZNAME`
|
|
||||||
|
|
||||||
**Changed:**
|
|
||||||
- Send field focus: After clicking a callsign in the user list, the send field immediately receives focus – no double-click needed *(tnx Gianluca)*.
|
|
||||||
|
|
||||||
**Fixed:**
|
|
||||||
- Worked-station filter is now live: Worked stations disappear immediately when the filter is activated *(tnx Gianluca)*.
|
|
||||||
- QRB sorting was lexicographic → now numeric *(tnx Alessandro Murador)*.
|
|
||||||
- AirScout "Show Path" button: Click now maximises AirScout and correctly shows the path.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.21 (2024-04)
|
|
||||||
**Usability Improvements**
|
|
||||||
|
|
||||||
**Changed:**
|
|
||||||
- Window sizes and divider positions are saved in the configuration file when clicking "Save Settings" and restored on startup.
|
|
||||||
- Filter section as flowpane → better display on smaller screens.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## v1.2 (2024-04)
|
|
||||||
**Band Selection and NOT-QRV Tags**
|
|
||||||
|
|
||||||
**New:**
|
|
||||||
- **Band selection**: Selectable in Preferences which bands are active. Only buttons and fields for selected bands appear in the UI. Save and restart required.
|
|
||||||
- **NOT-QRV tags per station and band**: Stations can be marked as "not QRV" for each band. Combinable with the user list filter.
|
|
||||||
- **QTF arrow**: The "Show path in AS" button now shows an arrow with the QTF of the selected station.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Earlier Versions
|
|
||||||
|
|
||||||
### v1.1
|
|
||||||
First publicly released version. Core features:
|
|
||||||
- Worked marking via Simplelogfile and UDP
|
|
||||||
- Sked direction highlighting
|
|
||||||
- QRG detection
|
|
||||||
- Text snippets and shortcuts
|
|
||||||
- AirScout interface (first version)
|
|
||||||
- Interval beacon
|
|
||||||
- PM catching for public messages containing your own callsign
|
|
||||||
- Update notification service
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Planned Features
|
|
||||||
|
|
||||||
- `MYQTF` variable (own antenna direction as text)
|
|
||||||
- ~~Lifetime for worked status (automatic reset)~~ ✅ **Implemented in v1.40** (3-day lifetime, no manual reset needed anymore)
|
|
||||||
- Filtering the "Cluster & QSO of others" window to own QTF
|
|
||||||
- Further topography-based calculations for direction warnings
|
|
||||||
@@ -1,200 +0,0 @@
|
|||||||
# Configuration
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Konfiguration)
|
|
||||||
|
|
||||||
After the first start, the **settings window** opens – this is the central starting point for all configuration. It is recommended to keep the settings window open during operation (e.g. to quickly toggle the beacon on and off).
|
|
||||||
|
|
||||||
> **Important**: Always click **"Save Settings"** after any change! Settings are stored in `~/.praktikst/preferences.xml` on Linux and in `%USERPROFILE%\.praktikst\preferences.xml` (or `C:\Users\<Username>\.praktikst\preferences.xml`) on Windows. From v1.21 onwards, window sizes and divider positions are also saved when you click Save.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Station Settings
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Login and Chat Categories
|
|
||||||
|
|
||||||
Enter your ON4KST chat credentials here (callsign and password).
|
|
||||||
Also, select the **primary chat category** (e.g., IARU Region 1 VHF/Microwave).
|
|
||||||
|
|
||||||
With the option for a **second chat** (Multi-Channel Login), you can log in to another category simultaneously (e.g., UHF/SHF). Both chats will then be monitored in parallel. You can optionally specify a different login name for the second chat (useful for Opposite Station Multi-Callsign Logging).
|
|
||||||
|
|
||||||
### Callsign and Locator
|
|
||||||
|
|
||||||
Enter your own callsign and Maidenhead locator (6 characters, e.g., `JN49IJ`). These values are needed for distance and direction calculations.
|
|
||||||
|
|
||||||
### Active Bands
|
|
||||||
|
|
||||||
Use the **"my station uses band"** checkboxes to select the active bands. Buttons and table rows will only appear in the user interface for selected bands. The software must be restarted after making changes.
|
|
||||||
|
|
||||||
### Antenna Beamwidth
|
|
||||||
|
|
||||||
Enter a realistic value for your antenna's beamwidth (in degrees). This value is used for the [Sked Direction Highlighting](Features#sked-direction-highlighting). A test value of 50° has proven effective; DM5M uses quads with 69°.
|
|
||||||
|
|
||||||
> **Do not** enter fantasy values – the direction calculations will become useless.
|
|
||||||
|
|
||||||
### Default Maximum QRB
|
|
||||||
|
|
||||||
Maximum distance (in km) for which direction warnings should be triggered. A realistic value for DM5M is 900 km. Stations farther away are ignored for highlighting purposes.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Server Settings (from v1.31)
|
|
||||||
|
|
||||||
The chat server DNS and port are configurable in the Preferences:
|
|
||||||
|
|
||||||
- **Server DNS**: Default `www.on4kst.org` (changed from `www.on4kst.info` in v1.31 hotfix).
|
|
||||||
- **Port**: Default port of the ON4KST server.
|
|
||||||
|
|
||||||
A change is only needed if the server moves or an alternative endpoint is used.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Log Sync Settings
|
|
||||||
|
|
||||||
Three methods are available for automatically marking worked stations. Details: [Log Synchronisation](en-Log-Sync).
|
|
||||||
|
|
||||||
### Universal File Based Callsign Interpreter (Simplelogfile)
|
|
||||||
|
|
||||||
Interprets any log file using regex for callsign patterns. No band information is available. Suitable as a fallback or for log programs that are not directly supported.
|
|
||||||
|
|
||||||
### Network Listener for Logger's QSO UDP Broadcast
|
|
||||||
|
|
||||||
**Recommended method.** KST4Contest listens for UDP packets sent by the logging software to the broadcast address when a QSO is saved. Stations are marked with band information. UDP port: default **12060**. (Used by UCXLog, N1MM+, QARTest, DXLog.net, etc.).
|
|
||||||
|
|
||||||
### Win-Test Network Listener (Additional UDP Listener)
|
|
||||||
|
|
||||||
A dedicated network listener for Win-Test. KST4Contest receives and processes Win-Test-specific UDP packets (including sked handovers) on the configured port.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## TRX Sync Settings
|
|
||||||
|
|
||||||
Receives the current transceiver frequency from the logging software via UDP. This enables the automatic population of the `MYQRG` variable. Useful for:
|
|
||||||
|
|
||||||
- Quickly inserting your own QRG into chat messages.
|
|
||||||
- Automatic CQ beacon with current frequency.
|
|
||||||
|
|
||||||
> **Note for multi-setup**: When running two logging programs on two computers but only one KST4Contest instance, only one logging program should send frequency packets. KST4Contest cannot distinguish between sources.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AirScout Settings
|
|
||||||
|
|
||||||
Configuration of the interface to AirScout for aircraft scatter detection. Details: [AirScout Integration](en-AirScout-Integration).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Notification Settings
|
|
||||||
|
|
||||||
Three notification types are available:
|
|
||||||
|
|
||||||
1. **Simple sounds**: TADA sound for incoming messages, tick for sked direction detection, etc.
|
|
||||||
2. **CW announcement**: The callsign of a station sending a private message is output as a CW signal.
|
|
||||||
3. **Phonetic announcement**: The callsign is pronounced phonetically.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Shortcut Settings
|
|
||||||
|
|
||||||
Configuration of quick-access buttons that appear directly in the main window. Clicking a button inserts the configured text into the send field. All [variables](Macros-and-Variables#variables) can be used.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Snippet Settings
|
|
||||||
|
|
||||||
Text snippets are accessible via:
|
|
||||||
|
|
||||||
- **Right-click** on a callsign in the user list
|
|
||||||
- **Right-click** in the CQ message table
|
|
||||||
- **Right-click** in the PM message table
|
|
||||||
- **Keyboard shortcuts**: `Ctrl+1` to `Ctrl+0` for the first 10 snippets
|
|
||||||
|
|
||||||
If a callsign is selected in the user list, the snippet is addressed as a direct message:
|
|
||||||
`/CQ CALLSIGN <snippet text>`
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Beacon Settings
|
|
||||||
|
|
||||||
Configuration of an automatic interval beacon in the public chat channel. Recommended: use the `MYQRG` variable in the text so the current frequency is always up to date. Interval and text are freely configurable.
|
|
||||||
|
|
||||||
> **Tip**: Enable the beacon when calling CQ and quickly disable it in the settings window when not calling.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Messagehandling Settings (from v1.25)
|
|
||||||
|
|
||||||
New settings section with the following options:
|
|
||||||
|
|
||||||
- **Auto-reply to all incoming messages**: Configurable automatic reply to private messages.
|
|
||||||
- **Auto-reply with own CQ QRG**: When someone asks for your QRG, KST4Contest automatically replies with the content of the `MYQRG` variable.
|
|
||||||
- **Default filter for the userinfo window**: Pre-configured message filter for the station info window *(for Gianluca :-) )*.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Win-Test Network Listener (from v1.31)
|
|
||||||
|
|
||||||
A dedicated listener for Win-Test-specific UDP packets. Enables:
|
|
||||||
|
|
||||||
- **Log synchronisation**: Worked stations are retrieved from Win-Test and marked in the user list.
|
|
||||||
- **Frequency parsing**: The current TRX frequency from Win-Test populates the `MYQRG` variable.
|
|
||||||
- **Sked handover (SKED push)**: Skeds from KST4Contest are passed directly to Win-Test via UDP. Win-Test's default UDP broadcast port (9871) is used.
|
|
||||||
|
|
||||||
Settings:
|
|
||||||
- **Enable/Disable**: Checkbox in Preferences (from v1.40).
|
|
||||||
- **Port**: Configurable UDP port for the Win-Test listener.
|
|
||||||
- **Sked UDP address and port**: Target address and port for SKED handover to Win-Test.
|
|
||||||
|
|
||||||
> **Note**: The Win-Test listener is an **additional** listener – the standard QSO UDP broadcast listener on port 12060 remains independent.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## PSTRotator Settings (from v1.31)
|
|
||||||
|
|
||||||
KST4Contest can control antenna direction via PSTRotator.
|
|
||||||
|
|
||||||
Settings:
|
|
||||||
- **Enable/Disable**: Checkbox in Preferences (from v1.40).
|
|
||||||
- **IP address**: IP address of the PSTRotator computer (default: `127.0.0.1` when running on the same PC).
|
|
||||||
- **Port**: Communication port of PSTRotator.
|
|
||||||
|
|
||||||
> **Note**: After clicking a direction button, KST4Contest waits briefly for the rotator response. With slow rotors (e.g. SPID) there may be a small delay.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sniffer Settings (from v1.31)
|
|
||||||
|
|
||||||
The QSO sniffer filters chat messages from configurable callsigns and forwards them to the PM window.
|
|
||||||
|
|
||||||
Settings:
|
|
||||||
- **Callsign list**: Comma-separated list of callsigns whose messages are always forwarded to the PM window.
|
|
||||||
|
|
||||||
Use case: Keep track of important stations (e.g. DX expeditions or trusted contest allies) without constantly monitoring the main chat.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked Station Database Settings
|
|
||||||
|
|
||||||
The internal worked database contains:
|
|
||||||
|
|
||||||
- Worked status of all stations (per band)
|
|
||||||
- NOT-QRV tags (since v1.2)
|
|
||||||
|
|
||||||
**From v1.40**: Entries have an automatic lifetime of **3 days** – manually resetting before each contest is no longer strictly necessary. For a full reset, the **"Reinitialize"** button is still available.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Dark Mode (from v1.26)
|
|
||||||
|
|
||||||
Toggle via the menu: **Window → Use Dark Mode**. The colors can be individually customized via CSS.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Saving Settings
|
|
||||||
|
|
||||||
Click **"Save Settings"** after **every** change! Without saving, all changes will be lost on the next start.
|
|
||||||
|
|
||||||
- Storage location: `~/.praktikst/preferences.xml` on Linux and `%USERPROFILE%\.praktikst\preferences.xml` (or `C:\Users\<Username>\.praktikst\preferences.xml`) on Windows
|
|
||||||
- From v1.21: Window sizes and divider positions are also saved.
|
|
||||||
- If you encounter problems: delete the configuration file → KST4Contest will create a new one with default values.
|
|
||||||
@@ -1,76 +0,0 @@
|
|||||||
# Built-in DX Cluster Server
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-DX-Cluster-Server)
|
|
||||||
|
|
||||||
From **version 1.23**, KST4Contest includes a built-in DX cluster server. It sends spots directly to the logging software whenever a direction warning is triggered.
|
|
||||||
|
|
||||||
*(Idea by OM0AAO, Viliam Petrik – thank you!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## What is the Built-in DX Cluster Server For?
|
|
||||||
|
|
||||||
When KST4Contest detects that a station is requesting a sked from your direction and a QRG is known, it **automatically generates a DX cluster spot** and feeds it directly to the logging software's cluster client / band map.
|
|
||||||
|
|
||||||
The logging software then displays the spot in the band map. Clicking the spot sets the transceiver's frequency and mode directly – without any manual typing.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Setup
|
|
||||||
|
|
||||||
### In KST4Contest
|
|
||||||
|
|
||||||
In Preferences → **DX Cluster Server Settings**:
|
|
||||||
|
|
||||||
1. Enter the **port** of the internal server (e.g. 7300 or 8000 – must match the logging software).
|
|
||||||
2. Enter a **spotter callsign** – **this must be a different callsign than your contest callsign!**
|
|
||||||
- Reason: Logging programs filter spots from your own callsign as "already worked". If the spotter uses the same callsign, the spots will not be displayed.
|
|
||||||
3. Enter the **assumed MHz**: For frequency references like ".205" in the chat, KST4Contest needs to decide whether 144.205, 432.205 or 1296.205 is meant. For single-band contests, simply enter the corresponding band centre. Full frequency references like "144.205" or "1296.338" in the chat are always correctly identified.
|
|
||||||
|
|
||||||
### In UCXLog
|
|
||||||
|
|
||||||
- Configure a DX cluster server connection:
|
|
||||||
- Host: `127.0.0.1` (or IP of the KST4Contest computer)
|
|
||||||
- Port: As configured in KST4Contest
|
|
||||||
- Password: can be left empty
|
|
||||||
- Use the **"Send a test message to your log"** button to test the connection.
|
|
||||||
|
|
||||||
### In N1MM+
|
|
||||||
|
|
||||||
Similar settings:
|
|
||||||
- Host: `127.0.0.1` (or IP of the KST4Contest computer)
|
|
||||||
- Port: As configured in KST4Contest
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## How It Works
|
|
||||||
|
|
||||||
A spot is generated when **both** conditions are met:
|
|
||||||
|
|
||||||
1. A **direction warning** has been triggered (station is making a sked in your direction).
|
|
||||||
2. The **station's QRG is known** (read from the chat or manually entered).
|
|
||||||
|
|
||||||
The generated spot contains:
|
|
||||||
- Station's callsign
|
|
||||||
- Frequency
|
|
||||||
- Spot time
|
|
||||||
|
|
||||||
The logging software can then display the spot in the band map and tune the TRX to that frequency with a mouse click.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multi-Computer Setup
|
|
||||||
|
|
||||||
If KST4Contest runs on a separate computer (not the logging computer):
|
|
||||||
|
|
||||||
- Host in the logging software: IP of the KST4Contest computer (not `127.0.0.1`)
|
|
||||||
- Same configuration as for the QSO UDP broadcast packets (see [Log Synchronisation](en-Log-Sync))
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Tested Logging Software
|
|
||||||
|
|
||||||
- **UCXLog** ✓
|
|
||||||
- **N1MM+** ✓
|
|
||||||
|
|
||||||
Further test reports are welcome – please send by email to DO5AMF.
|
|
||||||
@@ -1,235 +0,0 @@
|
|||||||
# Features
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Funktionen)
|
|
||||||
|
|
||||||
Overview of all main features of KST4Contest.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sked Direction Highlighting
|
|
||||||
|
|
||||||
One of the core features: when a station makes a sked request **towards your direction**, it is highlighted **green and bold** in the user list.
|
|
||||||
|
|
||||||
### How does it work?
|
|
||||||
|
|
||||||
The calculation is based on the following logic:
|
|
||||||
|
|
||||||
- When station A sends a sked request to station B, it is assumed that A is pointing its antenna towards B.
|
|
||||||
- If the resulting direction from A to your own station is within half the beamwidth of your own antenna, A is highlighted.
|
|
||||||
|
|
||||||
**Example** (beamwidth 69°, half-angle 34.5°):
|
|
||||||
|
|
||||||
| Situation | Result for DO5AMF in JN49 |
|
|
||||||
|---|---|
|
|
||||||
| Sked from F5FEN → DM5M | ✅ Highlighted (F5FEN points towards DM5M, close to JN49) |
|
|
||||||
| Sked from DM5M → F5FEN | ✅ Highlighted (DM5M replies towards F5FEN) |
|
|
||||||
| F1DBN is uninvolved | ❌ No highlighting |
|
|
||||||
| DO5AMF/P (different location) | ❌ No highlighting for sked reply |
|
|
||||||
|
|
||||||
The calculation does not include topographic path calculations – this is a deliberate simplification. It may be added in a future version.
|
|
||||||
|
|
||||||
> Configuration: [Configuration – Antenna Beamwidth](Configuration#antenna-beamwidth)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sked Direction Spots (Built-in DX Cluster)
|
|
||||||
|
|
||||||
From **v1.23**: Direction warnings are forwarded as DX cluster spots to the logging software when a QRG is known. Details: [DX Cluster Server](en-DX-Cluster-Server).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## QRG Detection (QRG Reading)
|
|
||||||
|
|
||||||
KST4Contest processes every line of text flowing through the channel and automatically extracts **frequency references**. These are displayed in the user list in the **QRG column**.
|
|
||||||
|
|
||||||
Recognised formats: `144.205`, `432.088`, `.205` (with configured band assumption), etc.
|
|
||||||
|
|
||||||
**Benefit**: Without asking, you can directly look up a station's calling frequency and decide whether a contact is possible.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked Marking
|
|
||||||
|
|
||||||
Worked stations are visually marked in the user list – per band. Based on [Log Synchronisation](en-Log-Sync) via UDP or Simplelogfile.
|
|
||||||
|
|
||||||
Reset the database before each contest: [Configuration – Worked Station Database Settings](Configuration#worked-station-database-settings).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## NOT-QRV Tags (from v1.2)
|
|
||||||
|
|
||||||
When a station indicates it is not QRV on a specific band, this can be manually marked:
|
|
||||||
|
|
||||||
1. Select the station in the user list.
|
|
||||||
2. Right-click → Set NOT-QRV for the appropriate band.
|
|
||||||
|
|
||||||
These tags are stored in the internal database and persist after a KST4Contest restart. Can be reset via the settings.
|
|
||||||
|
|
||||||
**Benefit**: Prevents repeated sked requests on bands where the station is not active – saves time for both sides.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Direction Filter
|
|
||||||
|
|
||||||
Shows only stations in the user list that are located in a specific direction. Toggle using the N / NE / E / SE / S / SW / W / NW buttons or by entering degrees manually.
|
|
||||||
|
|
||||||
Useful: While calling CQ in a specific direction, only show stations in that direction.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Distance Filter
|
|
||||||
|
|
||||||
Hide stations beyond a maximum distance. The **"Show only QRB [km] <="** button is a toggle.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked and NOT-QRV Filter
|
|
||||||
|
|
||||||
Toggle buttons (one per band) to hide already-worked stations and/or NOT-QRV-tagged stations. The filter takes effect **immediately** without manually reactivating (live since v1.22).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Coloured PM Rows (from v1.25)
|
|
||||||
|
|
||||||
New private messages appear in **red**. The colour fades every 30 seconds from yellow to white – like a rainbow fade. This makes it immediately clear how recent a message is.
|
|
||||||
|
|
||||||
*(Idea by IU3OAR, Gianluca Costantino – thank you!)*
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## PM Catching
|
|
||||||
|
|
||||||
Some users accidentally post direct messages publicly, e.g.:
|
|
||||||
|
|
||||||
```
|
|
||||||
(DM5M) pse ur qrg
|
|
||||||
```
|
|
||||||
|
|
||||||
KST4Contest detects such messages that contain your own callsign and automatically sorts them into the **private messages table**. No messages are missed this way.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multi-Channel Login (from v1.26)
|
|
||||||
|
|
||||||
Simultaneous login to **two chat categories** (e.g. 144 MHz and 432 MHz). Both chats are monitored in parallel.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Dark Mode (from v1.26)
|
|
||||||
|
|
||||||
Toggle via: **Window → Use Dark Mode**
|
|
||||||
|
|
||||||
For individual colour adjustments: edit the CSS file (path in the program settings).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Opposite Station Multi-Callsign Login Tagging (from v1.26)
|
|
||||||
|
|
||||||
Support for stations that are active in the chat with multiple callsigns simultaneously (e.g. expedition setups).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## QRZ.com and QRZ-CQ Profile Buttons (from v1.24)
|
|
||||||
|
|
||||||
For selected stations in the user list, there are direct buttons to open the **QRZ.com profile** and the **QRZ-CQ profile** in the browser.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Sked Reminders with ALERT (from v1.40)
|
|
||||||
|
|
||||||
A sked reminder service with automatic messages can be activated for each chat member. Configurable interval patterns:
|
|
||||||
|
|
||||||
- **2+1 minutes**: Messages at 2 min and 1 min before the sked.
|
|
||||||
- **5+2+1 minutes**: Messages at 5, 2 and 1 min before the sked.
|
|
||||||
- **10+5+2+1 minutes**: Messages at 10, 5, 2 and 1 min before the sked.
|
|
||||||
|
|
||||||
In addition to the automated messages to the remote station, there is an **acoustic and visual notification** for your own operator so no sked is ever missed.
|
|
||||||
|
|
||||||
Activate from the FurtherInfo panel of the corresponding station.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## QSO Sniffer (from v1.31)
|
|
||||||
|
|
||||||
The QSO sniffer monitors the chat for messages from a configurable callsign list and automatically forwards them to the **PM window**. This prevents relevant messages from being lost in the general chat traffic.
|
|
||||||
|
|
||||||
Configuration: [Configuration – Sniffer Settings](en-Configuration#sniffer-settings-from-v131)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Win-Test Integration (from v1.31, fully configurable from v1.40)
|
|
||||||
|
|
||||||
KST4Contest fully supports [Win-Test](https://www.win-test.com/) as a logging programme:
|
|
||||||
|
|
||||||
- **Log synchronisation**: Worked stations are automatically retrieved from Win-Test and marked in the user list.
|
|
||||||
- **Frequency parsing**: The current TRX frequency is read from Win-Test UDP packets and populates the `MYQRG` variable.
|
|
||||||
- **Sked handover (SKED push via UDP)**: Agreed skeds from KST4Contest can be pushed directly to Win-Test, so the remote callsign appears in Win-Test's sked window.
|
|
||||||
|
|
||||||
Details: [Configuration – Win-Test Network Listener](en-Configuration#win-test-network-listener)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## PSTRotator Interface (from v1.31, fully configurable from v1.40)
|
|
||||||
|
|
||||||
KST4Contest can control antenna direction directly via **PSTRotator**. When a station is selected in the user list, the rotator can automatically be turned to the QTF of the selected station.
|
|
||||||
|
|
||||||
Configuration: [Configuration – PSTRotator Settings](en-Configuration#pstrotator-settings-from-v131)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Band Alert for New QSOs (from v1.40)
|
|
||||||
|
|
||||||
When a station is logged, KST4Contest automatically checks whether that station has shown any other active bands in the chat that you are also QRV on. If so, a **hint alert** appears so no multi-band opportunity is missed.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Worked Tag Lifetime (from v1.40)
|
|
||||||
|
|
||||||
Worked stations are automatically removed from the database after **3 days**. Manually resetting the worked database before each contest is therefore no longer strictly necessary – the database keeps itself up to date.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Chatmember Score System / Priority List (from v1.40)
|
|
||||||
|
|
||||||
KST4Contest automatically calculates a **priority score** for each active chat member. The score is derived from:
|
|
||||||
|
|
||||||
- Antenna direction of the remote station (is it pointing towards me?)
|
|
||||||
- QRB (distance)
|
|
||||||
- Activity time and message count
|
|
||||||
- Active bands and frequencies
|
|
||||||
- AP availability (AirScout)
|
|
||||||
- Sked direction (degrees)
|
|
||||||
- Sked success rate and skedfail markings
|
|
||||||
|
|
||||||
The top candidates are highlighted in a dedicated priority list, helping you not to miss the most important contacts during contest stress.
|
|
||||||
|
|
||||||
Stations with a failed sked can be marked using the **Skedfail button** in the FurtherInfo panel – this temporarily lowers their score.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## AP Timeline (from v1.40)
|
|
||||||
|
|
||||||
A visual timeline shows up to 4 highly-scored stations per minute slot that should be workable via aircraft scatter. Prioritisation criteria:
|
|
||||||
|
|
||||||
- **Highest reflection potential** is preferred (not necessarily the fastest arrival).
|
|
||||||
- Stations towards which your antenna is not pointing are shown **transparently**.
|
|
||||||
|
|
||||||
This gives the contest operator a quick overview of which stations will be reachable via which aircraft and at what time.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Interval Beacon
|
|
||||||
|
|
||||||
Automatic CQ messages in the public channel at a configurable interval. Recommended: use the `MYQRG` variable so the current frequency is always accurate. Details: [Configuration – Beacon Settings](Configuration#beacon-settings).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Simplelogfile
|
|
||||||
|
|
||||||
File-based log evaluation using regex. Details: [Log Synchronisation](Log-Sync#method-1-universal-file-based-callsign-interpreter-simplelogfile).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Cluster & QSO of Others
|
|
||||||
|
|
||||||
A separate window showing the QSO flow between other stations. Particularly interesting during quieter night-time hours of a contest. This window can be minimised when not needed. Future plan: filtering to stations in your selected QTF.
|
|
||||||
@@ -1,51 +0,0 @@
|
|||||||
# KST4Contest – Wiki
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Home)
|
|
||||||
|
|
||||||
**KST4Contest** (also known as *PraktiKST*) is a Java-based chat client for the [ON4KST Chat](http://www.on4kst.info/chat/), specifically designed for contest operation on the VHF/UHF/SHF bands (144 MHz and above).
|
|
||||||
|
|
||||||
Developed by **DO5AMF (Marc Fröhlich)**, operator at DM5M.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Quick Navigation
|
|
||||||
|
|
||||||
| Page | Contents |
|
|
||||||
|---|---|
|
|
||||||
| [Installation](en-Installation) | Download, Java requirements, update |
|
|
||||||
| [Configuration](en-Configuration) | All settings in detail |
|
|
||||||
| [Log Synchronisation](en-Log-Sync) | UCXLog, N1MM+, QARTest, DXLog.net, WinTest |
|
|
||||||
| [AirScout Integration](en-AirScout-Integration) | Aircraft scatter detection |
|
|
||||||
| [DX Cluster Server](en-DX-Cluster-Server) | Built-in DX cluster for your logging software |
|
|
||||||
| [Features](en-Features) | All features at a glance |
|
|
||||||
| [Macros and Variables](en-Macros-and-Variables) | Text snippets, shortcuts, variables |
|
|
||||||
| [User Interface](en-User-Interface) | UI explanation and operation |
|
|
||||||
| [Changelog](en-Changelog) | Version history |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## What is KST4Contest?
|
|
||||||
|
|
||||||
The ON4KST Chat is the de-facto standard for skeds on the 144 MHz and higher bands. KST4Contest enhances the chat experience with contest-specific features:
|
|
||||||
|
|
||||||
- **Worked marking**: Stations already worked are highlighted visually, synchronised directly from your logging software via UDP.
|
|
||||||
- **Sked direction detection**: When a station calls another one from your direction, it is highlighted green and bold.
|
|
||||||
- **QRG detection**: KST4Contest automatically reads frequencies from the chat traffic and shows them in the user list.
|
|
||||||
- **AirScout interface**: Reflectable aircraft are shown directly in the user list.
|
|
||||||
- **Built-in DX cluster server**: Spots are sent directly to your logging software.
|
|
||||||
- **Dark mode** (from v1.26): Easy on the eyes during night-time operation.
|
|
||||||
- **Multi-channel login** (from v1.26): Simultaneously logged into two chat categories.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Contact & Support
|
|
||||||
|
|
||||||
- **Email**: praktimarc+kst4contest@gmail.com *(for kst4contest topics only)*
|
|
||||||
- **GitHub**: https://github.com/praktimarc/kst4contest
|
|
||||||
- **Download**: https://github.com/praktimarc/kst4contest/releases/latest
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Acknowledgements
|
|
||||||
|
|
||||||
Special thanks to: Gianluca Costantino (IU3OAR), Alessandro Murador (IZ3VTH), Reczetár István (HA1FV), OM0AAO (Viliam Petrik, DX cluster idea), DC9DJ (Konrad Neitzel, project structure), DO5ALF (Andreas, webmaster funkerportal.de), PE0WGA (Franz van Velzen, tester) and all other testers and contributors.
|
|
||||||
@@ -1,114 +0,0 @@
|
|||||||
# Installation
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Installation)
|
|
||||||
|
|
||||||
## Prerequisites
|
|
||||||
|
|
||||||
An resolution of 1200px by 720px is recommended
|
|
||||||
|
|
||||||
### ON4KST Account
|
|
||||||
|
|
||||||
To use the chat, a registered account with the ON4KST chat service is required:
|
|
||||||
|
|
||||||
- Register at: http://www.on4kst.info/chat/register.php
|
|
||||||
|
|
||||||
### Chat Etiquette
|
|
||||||
|
|
||||||
The official language in the ON4KST Chat is **English**. Please use English even when communicating with stations from your own country. Common HAM abbreviations (agn, dir, pse, rrr, tnx, 73 …) are widely used and understood.
|
|
||||||
|
|
||||||
### Personal Messages
|
|
||||||
|
|
||||||
To send a private message to another station, always use the following format:
|
|
||||||
|
|
||||||
```
|
|
||||||
/CQ CALLSIGN message text
|
|
||||||
```
|
|
||||||
|
|
||||||
Example: `/CQ DL5ASG pse sked 144.205?`
|
|
||||||
|
|
||||||
During heavy chat traffic (5–6 messages per second in a contest), public messages directed at a specific callsign are easily missed. However, KST4Contest also catches such messages if they are accidentally posted publicly (see [Features – PM Catching](Features#catching-personal-messages)).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Download
|
|
||||||
|
|
||||||
### Windows
|
|
||||||
|
|
||||||
The latest version can be downloaded as a ZIP file:
|
|
||||||
|
|
||||||
**https://github.com/praktimarc/kst4contest/releases/latest**
|
|
||||||
|
|
||||||
The filename has the format `praktiKST-v<version_number>-windows-x64.zip`.
|
|
||||||
|
|
||||||
### Linux
|
|
||||||
|
|
||||||
The latest version can be downloaded as an AppImage:
|
|
||||||
|
|
||||||
**https://github.com/praktimarc/kst4contest/releases/latest**
|
|
||||||
|
|
||||||
The filename has the format `praktiKST-v<version_number>-linux-x86_64.AppImage`.
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Installation
|
|
||||||
|
|
||||||
### Windows
|
|
||||||
|
|
||||||
1. Download the ZIP file.
|
|
||||||
2. Unzip the ZIP file into a folder of your choice.
|
|
||||||
3. Run `praktiKST.exe`.
|
|
||||||
|
|
||||||
Settings are stored at `%USERPROFILE%\.praktikst\preferences.xml`.
|
|
||||||
|
|
||||||
### Linux
|
|
||||||
1. Download the AppImage.
|
|
||||||
2. Unzip the AppImage into a folder of your choice.
|
|
||||||
3. Make the AppImage executable (in the terminal with `chmod +x praktiKST-v<version_number>-linux-x86_64.AppImage`)
|
|
||||||
4. Run the AppImage.
|
|
||||||
|
|
||||||
Settings are stored at `~/.praktikst/preferences.xml`.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Updating
|
|
||||||
|
|
||||||
KST4Contest includes an **automatic update notification service**: as soon as a new version is available, a window will appear at startup with:
|
|
||||||
- information that a new version is available,
|
|
||||||
- a changelog,
|
|
||||||
- the download link for the new version.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
### Update Process
|
|
||||||
|
|
||||||
#### Windows
|
|
||||||
|
|
||||||
Currently, there is only one way to update:
|
|
||||||
|
|
||||||
1. Delete the old folder.
|
|
||||||
2. Unzip the new ZIP file.
|
|
||||||
|
|
||||||
The settings file (`preferences.xml`) is preserved because it is stored in the user folder, not the program folder.
|
|
||||||
|
|
||||||
#### Linux
|
|
||||||
|
|
||||||
Currently as follows:
|
|
||||||
1. Download the new AppImage
|
|
||||||
2. Mark the new AppImage as executable
|
|
||||||
3. (optional) Delete the old AppImage.
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Known Issues at Startup
|
|
||||||
|
|
||||||
### Norton 360
|
|
||||||
|
|
||||||
Norton 360 classifies `praktiKST.exe` as dangerous (false positive). An exception must be created for the file:
|
|
||||||
|
|
||||||
1. Open Norton 360.
|
|
||||||
2. Security → History → Find the corresponding event.
|
|
||||||
3. Select "Restore & Add Exception".
|
|
||||||
|
|
||||||
*(Reported by PE0WGA, Franz van Velzen – thank you!)*
|
|
||||||
@@ -1,138 +0,0 @@
|
|||||||
# Log Synchronisation
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Log-Synchronisation)
|
|
||||||
|
|
||||||
KST4Contest automatically marks worked stations in the chat user list. Two basic methods are available:
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Method 1: Universal File Based Callsign Interpreter (Simplelogfile)
|
|
||||||
|
|
||||||
KST4Contest reads a log file and searches for callsign patterns using a regular expression. Binary log files are also supported – unreadable binary content is simply ignored.
|
|
||||||
|
|
||||||
**Advantage**: Works with almost any logging program that writes a file.
|
|
||||||
**Disadvantage**: No band information available – stations are only marked as "worked", not on which band.
|
|
||||||
|
|
||||||
Enter the path to the log file in the Preferences. The file is only read, never modified (read-only).
|
|
||||||
|
|
||||||
> **Tip**: The Simplelogfile function can also be used to mark stations that are definitely unreachable (e.g. personal notes). This will be replaced in a later version by a better tagging system.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Method 2: Network Listener (UDP Broadcast) – Recommended
|
|
||||||
|
|
||||||
When saving a QSO, the logging software sends a UDP packet to the broadcast address of the home network. KST4Contest receives this packet and marks the station including **band information** in its internal SQLite database.
|
|
||||||
|
|
||||||
> **Important**: KST4Contest must be **running in parallel with the logging software**. QSOs logged while KST4Contest is not running will not be captured – except with QARTest (which can send the complete log).
|
|
||||||
|
|
||||||
**Default UDP port**: 12060 (matches the default of most logging programs)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Supported Logging Software
|
|
||||||
|
|
||||||
### UCXLog (DL7UCX)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
UCXLog sends QSO UDP packets and transceiver frequency packets.
|
|
||||||
|
|
||||||
**Settings in UCXLog:**
|
|
||||||
- Enable UDP broadcast
|
|
||||||
- Enter the IP address of the KST4Contest computer (for local operation: `127.0.0.1`)
|
|
||||||
- Port: 12060 (default)
|
|
||||||
|
|
||||||
Note the green-highlighted fields in the UCXLog settings: IP and port must be filled in.
|
|
||||||
|
|
||||||
Note for multi-setup (2 computers, 2 radios, one KST4Contest instance): Both logging programs must send QSO packets to the IP of the KST4Contest computer. In this case, at least one IP is not `127.0.0.1`.
|
|
||||||
|
|
||||||
### QARTest (IK3QAR)
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Special feature**: QARTest can send the **complete log** to KST4Contest (button "Invia log completo" in the QARTest settings). This means QSOs logged before KST4Contest was started are also captured.
|
|
||||||
|
|
||||||
**Settings in QARTest:**
|
|
||||||
- Configure UDP broadcast and IP/port as with UCXLog
|
|
||||||
- Use "Invia log completo" for a full log upload
|
|
||||||
|
|
||||||
*(„Buona funzionalità caro IK3QAR!" – DO5AMF)*
|
|
||||||
|
|
||||||
### N1MM+
|
|
||||||
|
|
||||||
**Settings in N1MM+:**
|
|
||||||
|
|
||||||
In N1MM+ under `Config → Configure Ports, Mode Control, Winkey, etc. → Broadcast Data`:
|
|
||||||
- Enable `Radio Info` (for TRX sync / QRG)
|
|
||||||
- Enable `Contact Info` (for QSO sync)
|
|
||||||
- IP: `127.0.0.1` (or IP of the KST4Contest computer)
|
|
||||||
- Port: 12060
|
|
||||||
|
|
||||||
For the built-in DX cluster server: configure N1MM+ as a DX cluster client (server: `127.0.0.1`, port as set in KST4Contest).
|
|
||||||
|
|
||||||
### DXLog.net
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Settings in DXLog.net:**
|
|
||||||
- Enable UDP broadcast
|
|
||||||
- Enter the IP of the KST4Contest computer (green-highlighted fields)
|
|
||||||
- Port: 12060
|
|
||||||
|
|
||||||
### Win-Test
|
|
||||||
|
|
||||||
Win-Test is supported with a dedicated UDP network listener that understands the native Win-Test network protocol.
|
|
||||||
|
|
||||||
**Advantages of Win-Test Integration:**
|
|
||||||
- Automatic QSO synchronization to mark worked stations.
|
|
||||||
- **Sked Handover (ADDSKED):** Using the "Create sked" button in the station info panel not only creates a sked in KST4Contest but also *sends it directly via UDP to the Win-Test network as an ADDSKED packet*.
|
|
||||||
- You can choose between "AUTO", "SSB", or "CW" sked modes.
|
|
||||||
|
|
||||||
**Required Settings in KST4Contest:**
|
|
||||||
- `UDP-Port for Win-Test listener` (Default: 9871).
|
|
||||||
- Enable `Receive Win-Test network based UDP log messages`.
|
|
||||||
- Enable `Win-Test sked transmission (push via ADDSKED to Win-Test network)`.
|
|
||||||
- `KST station name in Win-Test network (src of SKED packets)`: Defines the station name KST4Contest uses in the WT network (e.g., "KST").
|
|
||||||
- `Win-Test station name filter`: If a name is entered here (e.g., "STN1"), only QSOs from that specific Win-Test instance will be processed. Leave empty to accept all.
|
|
||||||
- `Win-Test network broadcast address`: Is usually detected automatically and is required to send sked packets to the network.
|
|
||||||
|
|
||||||
**Settings in Win-Test:**
|
|
||||||
- The network in Win-Test must be active.
|
|
||||||
- Win-Test must be configured to send/receive its broadcasts on the corresponding port (default 9871).
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## TRX Frequency Synchronisation
|
|
||||||
|
|
||||||
In addition to QSO synchronisation, UCXLog and other programs also transmit the **current transceiver frequency** via UDP. KST4Contest processes this information and makes it available as the `MYQRG` variable.
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Result**: Your own QRG never needs to be typed manually in the chat – clicking the MYQRG button or using the variable in the beacon is sufficient.
|
|
||||||
|
|
||||||
> **Note for multi-setup**: With two logging programs on two computers, only **one** should send frequency packets. KST4Contest cannot distinguish between sources and processes all incoming packets.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Multi-Setup: 2 Radios, 2 Computers
|
|
||||||
|
|
||||||
For DM5M-style setups (2 radios, 2 computers, one KST4Contest instance or two separate):
|
|
||||||
|
|
||||||
**Option A – One shared KST4Contest instance:**
|
|
||||||
- Both logging programs send QSO packets to the IP of the KST4Contest computer
|
|
||||||
- Only one logging program sends frequency packets (recommended: the VHF logging program)
|
|
||||||
|
|
||||||
**Option B – Two separate KST4Contest instances (recommended):**
|
|
||||||
- Each logging program communicates with its own KST4Contest instance via `127.0.0.1`
|
|
||||||
- Two separate chat logins
|
|
||||||
- Better separation and fewer conflicts
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Internal Database
|
|
||||||
|
|
||||||
KST4Contest stores worked information in an internal **SQLite database**. This is independent of the logging program's database and is only populated via the UDP broadcast.
|
|
||||||
|
|
||||||
Before each new contest: reset the database! → [Configuration – Worked Station Database Settings](Configuration#worked-station-database-settings)
|
|
||||||
@@ -1,162 +0,0 @@
|
|||||||
# Macros and Variables
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Makros-und-Variablen)
|
|
||||||
|
|
||||||
KST4Contest offers a flexible system of text snippets, shortcuts and built-in variables that significantly speed up the chat workflow during contests.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Overview
|
|
||||||
|
|
||||||
| Type | Access | Purpose |
|
|
||||||
|---|---|---|
|
|
||||||
| **Shortcuts** | Button in the toolbar | Quick text insert into the send field |
|
|
||||||
| **Snippets** | Right-click / Ctrl+1..0 | Text building blocks, optional PM sending |
|
|
||||||
| **Variables** | Usable in all text fields | Dynamic values (QRG, locator, AP data) |
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Shortcuts (Quick-Access Buttons)
|
|
||||||
|
|
||||||
Configurable in Preferences → **Shortcut Settings**.
|
|
||||||
|
|
||||||
- Each configured text creates **one button** in the user interface.
|
|
||||||
- Clicking a button inserts the text into the **send field**.
|
|
||||||
- **All variables** can be used in shortcuts and are resolved immediately when inserted.
|
|
||||||
- Longer texts are also possible.
|
|
||||||
|
|
||||||
**Tip**: Set up frequently used abbreviations like "pse", "rrr", "tnx", "73" as shortcuts.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Snippets (Text Building Blocks)
|
|
||||||
|
|
||||||
Configurable in Preferences → **Snippet Settings**.
|
|
||||||
|
|
||||||
### Access
|
|
||||||
|
|
||||||
- **Right-click** on a callsign in the user list
|
|
||||||
- **Right-click** in the CQ message table
|
|
||||||
- **Right-click** in the PM message table
|
|
||||||
- **Keyboard shortcuts**: `Ctrl+1` to `Ctrl+0` for the first 10 snippets
|
|
||||||
|
|
||||||
### Behaviour with a Selected Callsign
|
|
||||||
|
|
||||||
When a callsign is selected in the user list, the snippet is addressed as a **private message**:
|
|
||||||
|
|
||||||
```
|
|
||||||
/CQ CALLSIGN <snippet text>
|
|
||||||
```
|
|
||||||
|
|
||||||
Then **Enter** can be pressed to send directly – even if the send field does not have focus.
|
|
||||||
|
|
||||||
### Hardware Macro Keyboard
|
|
||||||
|
|
||||||
*(Idea by IU3OAR, Gianluca Costantino)*
|
|
||||||
|
|
||||||
The key combinations `Ctrl+1` to `Ctrl+0` can be assigned to a programmable macro keyboard. One key press triggers the snippet, another press (mapped to Enter) sends it immediately. In contest operation this saves considerable time.
|
|
||||||
|
|
||||||
### Predefined Default Snippets
|
|
||||||
|
|
||||||
On first start, some snippets are pre-configured, e.g.:
|
|
||||||
|
|
||||||
- `Hi OM, try sked?`
|
|
||||||
- `I am calling cq ur dir, pse lsn to me at MYQRG`
|
|
||||||
- `pse ur qrg?`
|
|
||||||
- `rrr, I move to your qrg nw, pse ant dir me`
|
|
||||||
|
|
||||||
These can be customised or deleted in the Preferences.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Variables
|
|
||||||
|
|
||||||
Variables in written texts (snippets, shortcuts, beacon, send field) are replaced by their current values at runtime. Simply type the variable name in **uppercase** in the text.
|
|
||||||
|
|
||||||
### MYQRG
|
|
||||||
|
|
||||||
Replaced by the current transceiver frequency.
|
|
||||||
|
|
||||||
- Source: TRX sync via UDP from the logging software (if enabled)
|
|
||||||
- Fallback: Manually entered value in the MYQRG text field to the right of the send button
|
|
||||||
- Format: `144.388.03`
|
|
||||||
|
|
||||||
**Example**: `calling cq at MYQRG` → `calling cq at 144.388.03`
|
|
||||||
|
|
||||||
### MYQRGSHORT
|
|
||||||
|
|
||||||
Like MYQRG, but only the first 7 characters.
|
|
||||||
|
|
||||||
- Format: `144.388`
|
|
||||||
|
|
||||||
**Example**: `qrg: MYQRGSHORT` → `qrg: 144.388`
|
|
||||||
|
|
||||||
### MYLOCATOR
|
|
||||||
|
|
||||||
Replaced by your own Maidenhead locator (6 characters).
|
|
||||||
|
|
||||||
- Format: `JO51IJ`
|
|
||||||
|
|
||||||
**Example**: `my loc: MYLOCATOR` → `my loc: JO51IJ`
|
|
||||||
|
|
||||||
### MYLOCATORSHORT
|
|
||||||
|
|
||||||
Like MYLOCATOR, but only the first 4 characters.
|
|
||||||
|
|
||||||
- Format: `JO51`
|
|
||||||
|
|
||||||
**Example**: `loc: MYLOCATORSHORT` → `loc: JO51`
|
|
||||||
|
|
||||||
### QRZNAME
|
|
||||||
|
|
||||||
Replaced by the **name** of the currently selected station from the chat name field.
|
|
||||||
|
|
||||||
**Example**: `Hi QRZNAME, sked?` → `Hi Gianluca, sked?`
|
|
||||||
|
|
||||||
### FIRSTAP
|
|
||||||
|
|
||||||
Replaced by data of the first reflectable aircraft to the selected station (if available).
|
|
||||||
|
|
||||||
- Condition: AirScout is active and an aircraft is available.
|
|
||||||
- Example format: `a very big AP in 1 min`
|
|
||||||
|
|
||||||
**Example**: `AP info: FIRSTAP` → `AP info: a very big AP in 1 min`
|
|
||||||
|
|
||||||
### SECONDAP
|
|
||||||
|
|
||||||
Like FIRSTAP, but for the second available aircraft.
|
|
||||||
|
|
||||||
- Example format: `Next big AP in 9 min`
|
|
||||||
|
|
||||||
**Example**: `also: SECONDAP` → `also: Next big AP in 9 min`
|
|
||||||
|
|
||||||
### MYQTF *(planned for v1.3)*
|
|
||||||
|
|
||||||
Replaced by the current antenna direction in words (e.g. `north`, `north east`, `east`, …).
|
|
||||||
|
|
||||||
- Source: Degree value in the MYQTF input field (to the right of the MYQRG field)
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Variables in the Beacon
|
|
||||||
|
|
||||||
All variables can also be used in the **automatic beacon** (interval messages). Recommended beacon configuration:
|
|
||||||
|
|
||||||
```
|
|
||||||
calling cq at MYQRG, loc MYLOCATOR, GL all!
|
|
||||||
```
|
|
||||||
|
|
||||||
Since KST4Contest automatically reads QRG data from chat messages: if other stations also use KST4Contest, they will immediately see your QRG in the QRG column of their user list.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Example Contest Workflow with Macros
|
|
||||||
|
|
||||||
1. Select a station in the user list → callsign is now pre-selected.
|
|
||||||
2. Press `Ctrl+1` → Snippet "Hi OM, try sked?" is addressed as a PM.
|
|
||||||
3. Press Enter → Message sent.
|
|
||||||
4. Station replies with frequency → QRG column is automatically filled.
|
|
||||||
5. Press `Ctrl+2` → Snippet "I am calling cq ur dir, pse lsn to me at 144.388" (MYQRG resolved).
|
|
||||||
6. Press Enter → Sent.
|
|
||||||
|
|
||||||
No manual typing, no errors, no interruption to CQ calling.
|
|
||||||
@@ -1,105 +0,0 @@
|
|||||||
# User Interface
|
|
||||||
|
|
||||||
> 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Benutzeroberflaeche)
|
|
||||||
|
|
||||||
## Connecting to the Chat
|
|
||||||
|
|
||||||
1. Select a **chat category** in the settings window (e.g. 144 MHz VHF, 432 MHz UHF, …).
|
|
||||||
2. Click the **Connect** button.
|
|
||||||
3. Wait for the connection to be established.
|
|
||||||
|
|
||||||
> Disconnecting and reconnecting is only possible via the settings window. It is therefore recommended to keep the settings window open.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Main Window Overview
|
|
||||||
|
|
||||||
The main window consists of several areas:
|
|
||||||
|
|
||||||
### PM Window (top left)
|
|
||||||
|
|
||||||
Shows all received **private messages** as well as intercepted public messages containing your own callsign. New messages appear in **red** and fade every 30 seconds from yellow to white.
|
|
||||||
|
|
||||||
### User List (Chat Members)
|
|
||||||
|
|
||||||
The central table of all currently active chat users. Columns (depending on configuration):
|
|
||||||
|
|
||||||
| Column | Content |
|
|
||||||
|---|---|
|
|
||||||
| Call | Station's callsign |
|
|
||||||
| Name | Name from the chat name field |
|
|
||||||
| Loc | Maidenhead locator |
|
|
||||||
| QRB | Distance in km |
|
|
||||||
| QTF | Direction in degrees |
|
|
||||||
| QRG | Automatically detected frequency |
|
|
||||||
| AP | AirScout aircraft data (when active) |
|
|
||||||
| Band colours | Worked / NOT-QRV status per band |
|
|
||||||
|
|
||||||
**Sorting**: Click column headers. QRB sorting is numerical (corrected in v1.22).
|
|
||||||
|
|
||||||
### Send Field
|
|
||||||
|
|
||||||
Text input for outgoing messages. After clicking a callsign in the user list, the send field automatically receives focus – start typing immediately without double-clicking (from v1.22).
|
|
||||||
|
|
||||||
### MYQRG Field
|
|
||||||
|
|
||||||
To the right of the send button. Shows the current own QRG, can also be entered manually.
|
|
||||||
|
|
||||||
### MYQTF Field *(for v1.3)*
|
|
||||||
|
|
||||||
Input field for the current antenna direction. Used for the planned `MYQTF` variable.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Filters
|
|
||||||
|
|
||||||
The filter bar (from v1.21 as a flowpane for small screens):
|
|
||||||
|
|
||||||
- **Show only QTF**: Activate direction filter (N/NE/E/… buttons or degree input)
|
|
||||||
- **Show only QRB [km] <=**: Activate distance filter (toggle button)
|
|
||||||
- **Hide Worked [Band]**: Hide worked stations per band (one toggle per band)
|
|
||||||
- **Hide NOT-QRV [Band]**: Hide NOT-QRV-tagged stations per band
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Station Info Panel (Further Info)
|
|
||||||
|
|
||||||
Bottom right: Shows all messages of a selected station (CQ messages and PMs in one panel). A message filter can be pre-configured via the default filter in the Preferences.
|
|
||||||
|
|
||||||
**Sked reminders** can also be activated here.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Priority List
|
|
||||||
|
|
||||||
Shows the top candidates calculated by the Score Service. Updates automatically in the background based on direction, distance and AP availability.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Cluster & QSO of Others
|
|
||||||
|
|
||||||
Separate window (can be minimised). Shows the communication flow between other stations – interesting during quieter contest periods.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Menu
|
|
||||||
|
|
||||||
### Window
|
|
||||||
- **Use Dark Mode** (from v1.26): Toggle dark colour scheme on/off.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Window Sizes and Dividers
|
|
||||||
|
|
||||||
From **v1.21**, clicking **"Save Settings"** also saves window sizes and divider positions of all panels in the configuration file, which are restored on the next start.
|
|
||||||
|
|
||||||
If you encounter display problems: delete the configuration file → KST4Contest creates new default values.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## Operating Tips
|
|
||||||
|
|
||||||
- **Keep the settings window open**: Quick access to enable/disable the beacon.
|
|
||||||
- **Right-click in the user list**: Opens the snippet menu and further actions (QRZ.com profile, set NOT-QRV tags).
|
|
||||||
- **Enter from anywhere**: When text is in the send field, Enter sends directly – even if the focus is elsewhere.
|
|
||||||
- **Stop the beacon**: Switch off the beacon while scanning frequencies to avoid flooding the chat with messages.
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 1.5 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 250 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 63 KiB |
@@ -1,3 +0,0 @@
|
|||||||
@echo off
|
|
||||||
SET JAVA_HOME=C:\Program Files\Java\jdk-17
|
|
||||||
SET PATH=%JAVA_HOME%\bin,%PATH%
|
|
||||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -1,3 +0,0 @@
|
|||||||
javafx.version=19
|
|
||||||
javafx.runtime.version=19+11
|
|
||||||
javafx.runtime.build=11
|
|
||||||
Binary file not shown.
Binary file not shown.
@@ -1,308 +0,0 @@
|
|||||||
#!/bin/sh
|
|
||||||
# ----------------------------------------------------------------------------
|
|
||||||
# Licensed to the Apache Software Foundation (ASF) under one
|
|
||||||
# or more contributor license agreements. See the NOTICE file
|
|
||||||
# distributed with this work for additional information
|
|
||||||
# regarding copyright ownership. The ASF licenses this file
|
|
||||||
# to you under the Apache License, Version 2.0 (the
|
|
||||||
# "License"); you may not use this file except in compliance
|
|
||||||
# with the License. You may obtain a copy of the License at
|
|
||||||
#
|
|
||||||
# http://www.apache.org/licenses/LICENSE-2.0
|
|
||||||
#
|
|
||||||
# Unless required by applicable law or agreed to in writing,
|
|
||||||
# software distributed under the License is distributed on an
|
|
||||||
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
||||||
# KIND, either express or implied. See the License for the
|
|
||||||
# specific language governing permissions and limitations
|
|
||||||
# under the License.
|
|
||||||
# ----------------------------------------------------------------------------
|
|
||||||
|
|
||||||
# ----------------------------------------------------------------------------
|
|
||||||
# Apache Maven Wrapper startup batch script, version 3.2.0
|
|
||||||
#
|
|
||||||
# Required ENV vars:
|
|
||||||
# ------------------
|
|
||||||
# JAVA_HOME - location of a JDK home dir
|
|
||||||
#
|
|
||||||
# Optional ENV vars
|
|
||||||
# -----------------
|
|
||||||
# MAVEN_OPTS - parameters passed to the Java VM when running Maven
|
|
||||||
# e.g. to debug Maven itself, use
|
|
||||||
# set MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
|
|
||||||
# MAVEN_SKIP_RC - flag to disable loading of mavenrc files
|
|
||||||
# ----------------------------------------------------------------------------
|
|
||||||
|
|
||||||
if [ -z "$MAVEN_SKIP_RC" ] ; then
|
|
||||||
|
|
||||||
if [ -f /usr/local/etc/mavenrc ] ; then
|
|
||||||
. /usr/local/etc/mavenrc
|
|
||||||
fi
|
|
||||||
|
|
||||||
if [ -f /etc/mavenrc ] ; then
|
|
||||||
. /etc/mavenrc
|
|
||||||
fi
|
|
||||||
|
|
||||||
if [ -f "$HOME/.mavenrc" ] ; then
|
|
||||||
. "$HOME/.mavenrc"
|
|
||||||
fi
|
|
||||||
|
|
||||||
fi
|
|
||||||
|
|
||||||
# OS specific support. $var _must_ be set to either true or false.
|
|
||||||
cygwin=false;
|
|
||||||
darwin=false;
|
|
||||||
mingw=false
|
|
||||||
case "$(uname)" in
|
|
||||||
CYGWIN*) cygwin=true ;;
|
|
||||||
MINGW*) mingw=true;;
|
|
||||||
Darwin*) darwin=true
|
|
||||||
# Use /usr/libexec/java_home if available, otherwise fall back to /Library/Java/Home
|
|
||||||
# See https://developer.apple.com/library/mac/qa/qa1170/_index.html
|
|
||||||
if [ -z "$JAVA_HOME" ]; then
|
|
||||||
if [ -x "/usr/libexec/java_home" ]; then
|
|
||||||
JAVA_HOME="$(/usr/libexec/java_home)"; export JAVA_HOME
|
|
||||||
else
|
|
||||||
JAVA_HOME="/Library/Java/Home"; export JAVA_HOME
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
;;
|
|
||||||
esac
|
|
||||||
|
|
||||||
if [ -z "$JAVA_HOME" ] ; then
|
|
||||||
if [ -r /etc/gentoo-release ] ; then
|
|
||||||
JAVA_HOME=$(java-config --jre-home)
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
|
|
||||||
# For Cygwin, ensure paths are in UNIX format before anything is touched
|
|
||||||
if $cygwin ; then
|
|
||||||
[ -n "$JAVA_HOME" ] &&
|
|
||||||
JAVA_HOME=$(cygpath --unix "$JAVA_HOME")
|
|
||||||
[ -n "$CLASSPATH" ] &&
|
|
||||||
CLASSPATH=$(cygpath --path --unix "$CLASSPATH")
|
|
||||||
fi
|
|
||||||
|
|
||||||
# For Mingw, ensure paths are in UNIX format before anything is touched
|
|
||||||
if $mingw ; then
|
|
||||||
[ -n "$JAVA_HOME" ] && [ -d "$JAVA_HOME" ] &&
|
|
||||||
JAVA_HOME="$(cd "$JAVA_HOME" || (echo "cannot cd into $JAVA_HOME."; exit 1); pwd)"
|
|
||||||
fi
|
|
||||||
|
|
||||||
if [ -z "$JAVA_HOME" ]; then
|
|
||||||
javaExecutable="$(which javac)"
|
|
||||||
if [ -n "$javaExecutable" ] && ! [ "$(expr "\"$javaExecutable\"" : '\([^ ]*\)')" = "no" ]; then
|
|
||||||
# readlink(1) is not available as standard on Solaris 10.
|
|
||||||
readLink=$(which readlink)
|
|
||||||
if [ ! "$(expr "$readLink" : '\([^ ]*\)')" = "no" ]; then
|
|
||||||
if $darwin ; then
|
|
||||||
javaHome="$(dirname "\"$javaExecutable\"")"
|
|
||||||
javaExecutable="$(cd "\"$javaHome\"" && pwd -P)/javac"
|
|
||||||
else
|
|
||||||
javaExecutable="$(readlink -f "\"$javaExecutable\"")"
|
|
||||||
fi
|
|
||||||
javaHome="$(dirname "\"$javaExecutable\"")"
|
|
||||||
javaHome=$(expr "$javaHome" : '\(.*\)/bin')
|
|
||||||
JAVA_HOME="$javaHome"
|
|
||||||
export JAVA_HOME
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
|
|
||||||
if [ -z "$JAVACMD" ] ; then
|
|
||||||
if [ -n "$JAVA_HOME" ] ; then
|
|
||||||
if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
|
|
||||||
# IBM's JDK on AIX uses strange locations for the executables
|
|
||||||
JAVACMD="$JAVA_HOME/jre/sh/java"
|
|
||||||
else
|
|
||||||
JAVACMD="$JAVA_HOME/bin/java"
|
|
||||||
fi
|
|
||||||
else
|
|
||||||
JAVACMD="$(\unset -f command 2>/dev/null; \command -v java)"
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
|
|
||||||
if [ ! -x "$JAVACMD" ] ; then
|
|
||||||
echo "Error: JAVA_HOME is not defined correctly." >&2
|
|
||||||
echo " We cannot execute $JAVACMD" >&2
|
|
||||||
exit 1
|
|
||||||
fi
|
|
||||||
|
|
||||||
if [ -z "$JAVA_HOME" ] ; then
|
|
||||||
echo "Warning: JAVA_HOME environment variable is not set."
|
|
||||||
fi
|
|
||||||
|
|
||||||
# traverses directory structure from process work directory to filesystem root
|
|
||||||
# first directory with .mvn subdirectory is considered project base directory
|
|
||||||
find_maven_basedir() {
|
|
||||||
if [ -z "$1" ]
|
|
||||||
then
|
|
||||||
echo "Path not specified to find_maven_basedir"
|
|
||||||
return 1
|
|
||||||
fi
|
|
||||||
|
|
||||||
basedir="$1"
|
|
||||||
wdir="$1"
|
|
||||||
while [ "$wdir" != '/' ] ; do
|
|
||||||
if [ -d "$wdir"/.mvn ] ; then
|
|
||||||
basedir=$wdir
|
|
||||||
break
|
|
||||||
fi
|
|
||||||
# workaround for JBEAP-8937 (on Solaris 10/Sparc)
|
|
||||||
if [ -d "${wdir}" ]; then
|
|
||||||
wdir=$(cd "$wdir/.." || exit 1; pwd)
|
|
||||||
fi
|
|
||||||
# end of workaround
|
|
||||||
done
|
|
||||||
printf '%s' "$(cd "$basedir" || exit 1; pwd)"
|
|
||||||
}
|
|
||||||
|
|
||||||
# concatenates all lines of a file
|
|
||||||
concat_lines() {
|
|
||||||
if [ -f "$1" ]; then
|
|
||||||
# Remove \r in case we run on Windows within Git Bash
|
|
||||||
# and check out the repository with auto CRLF management
|
|
||||||
# enabled. Otherwise, we may read lines that are delimited with
|
|
||||||
# \r\n and produce $'-Xarg\r' rather than -Xarg due to word
|
|
||||||
# splitting rules.
|
|
||||||
tr -s '\r\n' ' ' < "$1"
|
|
||||||
fi
|
|
||||||
}
|
|
||||||
|
|
||||||
log() {
|
|
||||||
if [ "$MVNW_VERBOSE" = true ]; then
|
|
||||||
printf '%s\n' "$1"
|
|
||||||
fi
|
|
||||||
}
|
|
||||||
|
|
||||||
BASE_DIR=$(find_maven_basedir "$(dirname "$0")")
|
|
||||||
if [ -z "$BASE_DIR" ]; then
|
|
||||||
exit 1;
|
|
||||||
fi
|
|
||||||
|
|
||||||
MAVEN_PROJECTBASEDIR=${MAVEN_BASEDIR:-"$BASE_DIR"}; export MAVEN_PROJECTBASEDIR
|
|
||||||
log "$MAVEN_PROJECTBASEDIR"
|
|
||||||
|
|
||||||
##########################################################################################
|
|
||||||
# Extension to allow automatically downloading the maven-wrapper.jar from Maven-central
|
|
||||||
# This allows using the maven wrapper in projects that prohibit checking in binary data.
|
|
||||||
##########################################################################################
|
|
||||||
wrapperJarPath="$MAVEN_PROJECTBASEDIR/.mvn/wrapper/maven-wrapper.jar"
|
|
||||||
if [ -r "$wrapperJarPath" ]; then
|
|
||||||
log "Found $wrapperJarPath"
|
|
||||||
else
|
|
||||||
log "Couldn't find $wrapperJarPath, downloading it ..."
|
|
||||||
|
|
||||||
if [ -n "$MVNW_REPOURL" ]; then
|
|
||||||
wrapperUrl="$MVNW_REPOURL/org/apache/maven/wrapper/maven-wrapper/3.2.0/maven-wrapper-3.2.0.jar"
|
|
||||||
else
|
|
||||||
wrapperUrl="https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.2.0/maven-wrapper-3.2.0.jar"
|
|
||||||
fi
|
|
||||||
while IFS="=" read -r key value; do
|
|
||||||
# Remove '\r' from value to allow usage on windows as IFS does not consider '\r' as a separator ( considers space, tab, new line ('\n'), and custom '=' )
|
|
||||||
safeValue=$(echo "$value" | tr -d '\r')
|
|
||||||
case "$key" in (wrapperUrl) wrapperUrl="$safeValue"; break ;;
|
|
||||||
esac
|
|
||||||
done < "$MAVEN_PROJECTBASEDIR/.mvn/wrapper/maven-wrapper.properties"
|
|
||||||
log "Downloading from: $wrapperUrl"
|
|
||||||
|
|
||||||
if $cygwin; then
|
|
||||||
wrapperJarPath=$(cygpath --path --windows "$wrapperJarPath")
|
|
||||||
fi
|
|
||||||
|
|
||||||
if command -v wget > /dev/null; then
|
|
||||||
log "Found wget ... using wget"
|
|
||||||
[ "$MVNW_VERBOSE" = true ] && QUIET="" || QUIET="--quiet"
|
|
||||||
if [ -z "$MVNW_USERNAME" ] || [ -z "$MVNW_PASSWORD" ]; then
|
|
||||||
wget $QUIET "$wrapperUrl" -O "$wrapperJarPath" || rm -f "$wrapperJarPath"
|
|
||||||
else
|
|
||||||
wget $QUIET --http-user="$MVNW_USERNAME" --http-password="$MVNW_PASSWORD" "$wrapperUrl" -O "$wrapperJarPath" || rm -f "$wrapperJarPath"
|
|
||||||
fi
|
|
||||||
elif command -v curl > /dev/null; then
|
|
||||||
log "Found curl ... using curl"
|
|
||||||
[ "$MVNW_VERBOSE" = true ] && QUIET="" || QUIET="--silent"
|
|
||||||
if [ -z "$MVNW_USERNAME" ] || [ -z "$MVNW_PASSWORD" ]; then
|
|
||||||
curl $QUIET -o "$wrapperJarPath" "$wrapperUrl" -f -L || rm -f "$wrapperJarPath"
|
|
||||||
else
|
|
||||||
curl $QUIET --user "$MVNW_USERNAME:$MVNW_PASSWORD" -o "$wrapperJarPath" "$wrapperUrl" -f -L || rm -f "$wrapperJarPath"
|
|
||||||
fi
|
|
||||||
else
|
|
||||||
log "Falling back to using Java to download"
|
|
||||||
javaSource="$MAVEN_PROJECTBASEDIR/.mvn/wrapper/MavenWrapperDownloader.java"
|
|
||||||
javaClass="$MAVEN_PROJECTBASEDIR/.mvn/wrapper/MavenWrapperDownloader.class"
|
|
||||||
# For Cygwin, switch paths to Windows format before running javac
|
|
||||||
if $cygwin; then
|
|
||||||
javaSource=$(cygpath --path --windows "$javaSource")
|
|
||||||
javaClass=$(cygpath --path --windows "$javaClass")
|
|
||||||
fi
|
|
||||||
if [ -e "$javaSource" ]; then
|
|
||||||
if [ ! -e "$javaClass" ]; then
|
|
||||||
log " - Compiling MavenWrapperDownloader.java ..."
|
|
||||||
("$JAVA_HOME/bin/javac" "$javaSource")
|
|
||||||
fi
|
|
||||||
if [ -e "$javaClass" ]; then
|
|
||||||
log " - Running MavenWrapperDownloader.java ..."
|
|
||||||
("$JAVA_HOME/bin/java" -cp .mvn/wrapper MavenWrapperDownloader "$wrapperUrl" "$wrapperJarPath") || rm -f "$wrapperJarPath"
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
##########################################################################################
|
|
||||||
# End of extension
|
|
||||||
##########################################################################################
|
|
||||||
|
|
||||||
# If specified, validate the SHA-256 sum of the Maven wrapper jar file
|
|
||||||
wrapperSha256Sum=""
|
|
||||||
while IFS="=" read -r key value; do
|
|
||||||
case "$key" in (wrapperSha256Sum) wrapperSha256Sum=$value; break ;;
|
|
||||||
esac
|
|
||||||
done < "$MAVEN_PROJECTBASEDIR/.mvn/wrapper/maven-wrapper.properties"
|
|
||||||
if [ -n "$wrapperSha256Sum" ]; then
|
|
||||||
wrapperSha256Result=false
|
|
||||||
if command -v sha256sum > /dev/null; then
|
|
||||||
if echo "$wrapperSha256Sum $wrapperJarPath" | sha256sum -c > /dev/null 2>&1; then
|
|
||||||
wrapperSha256Result=true
|
|
||||||
fi
|
|
||||||
elif command -v shasum > /dev/null; then
|
|
||||||
if echo "$wrapperSha256Sum $wrapperJarPath" | shasum -a 256 -c > /dev/null 2>&1; then
|
|
||||||
wrapperSha256Result=true
|
|
||||||
fi
|
|
||||||
else
|
|
||||||
echo "Checksum validation was requested but neither 'sha256sum' or 'shasum' are available."
|
|
||||||
echo "Please install either command, or disable validation by removing 'wrapperSha256Sum' from your maven-wrapper.properties."
|
|
||||||
exit 1
|
|
||||||
fi
|
|
||||||
if [ $wrapperSha256Result = false ]; then
|
|
||||||
echo "Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper might be compromised." >&2
|
|
||||||
echo "Investigate or delete $wrapperJarPath to attempt a clean download." >&2
|
|
||||||
echo "If you updated your Maven version, you need to update the specified wrapperSha256Sum property." >&2
|
|
||||||
exit 1
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
|
|
||||||
MAVEN_OPTS="$(concat_lines "$MAVEN_PROJECTBASEDIR/.mvn/jvm.config") $MAVEN_OPTS"
|
|
||||||
|
|
||||||
# For Cygwin, switch paths to Windows format before running java
|
|
||||||
if $cygwin; then
|
|
||||||
[ -n "$JAVA_HOME" ] &&
|
|
||||||
JAVA_HOME=$(cygpath --path --windows "$JAVA_HOME")
|
|
||||||
[ -n "$CLASSPATH" ] &&
|
|
||||||
CLASSPATH=$(cygpath --path --windows "$CLASSPATH")
|
|
||||||
[ -n "$MAVEN_PROJECTBASEDIR" ] &&
|
|
||||||
MAVEN_PROJECTBASEDIR=$(cygpath --path --windows "$MAVEN_PROJECTBASEDIR")
|
|
||||||
fi
|
|
||||||
|
|
||||||
# Provide a "standardized" way to retrieve the CLI args that will
|
|
||||||
# work with both Windows and non-Windows executions.
|
|
||||||
MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*"
|
|
||||||
export MAVEN_CMD_LINE_ARGS
|
|
||||||
|
|
||||||
WRAPPER_LAUNCHER=org.apache.maven.wrapper.MavenWrapperMain
|
|
||||||
|
|
||||||
# shellcheck disable=SC2086 # safe args
|
|
||||||
exec "$JAVACMD" \
|
|
||||||
$MAVEN_OPTS \
|
|
||||||
$MAVEN_DEBUG_OPTS \
|
|
||||||
-classpath "$MAVEN_PROJECTBASEDIR/.mvn/wrapper/maven-wrapper.jar" \
|
|
||||||
"-Dmaven.multiModuleProjectDirectory=${MAVEN_PROJECTBASEDIR}" \
|
|
||||||
${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@"
|
|
||||||
@@ -1,205 +0,0 @@
|
|||||||
@REM ----------------------------------------------------------------------------
|
|
||||||
@REM Licensed to the Apache Software Foundation (ASF) under one
|
|
||||||
@REM or more contributor license agreements. See the NOTICE file
|
|
||||||
@REM distributed with this work for additional information
|
|
||||||
@REM regarding copyright ownership. The ASF licenses this file
|
|
||||||
@REM to you under the Apache License, Version 2.0 (the
|
|
||||||
@REM "License"); you may not use this file except in compliance
|
|
||||||
@REM with the License. You may obtain a copy of the License at
|
|
||||||
@REM
|
|
||||||
@REM http://www.apache.org/licenses/LICENSE-2.0
|
|
||||||
@REM
|
|
||||||
@REM Unless required by applicable law or agreed to in writing,
|
|
||||||
@REM software distributed under the License is distributed on an
|
|
||||||
@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
||||||
@REM KIND, either express or implied. See the License for the
|
|
||||||
@REM specific language governing permissions and limitations
|
|
||||||
@REM under the License.
|
|
||||||
@REM ----------------------------------------------------------------------------
|
|
||||||
|
|
||||||
@REM ----------------------------------------------------------------------------
|
|
||||||
@REM Apache Maven Wrapper startup batch script, version 3.2.0
|
|
||||||
@REM
|
|
||||||
@REM Required ENV vars:
|
|
||||||
@REM JAVA_HOME - location of a JDK home dir
|
|
||||||
@REM
|
|
||||||
@REM Optional ENV vars
|
|
||||||
@REM MAVEN_BATCH_ECHO - set to 'on' to enable the echoing of the batch commands
|
|
||||||
@REM MAVEN_BATCH_PAUSE - set to 'on' to wait for a keystroke before ending
|
|
||||||
@REM MAVEN_OPTS - parameters passed to the Java VM when running Maven
|
|
||||||
@REM e.g. to debug Maven itself, use
|
|
||||||
@REM set MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
|
|
||||||
@REM MAVEN_SKIP_RC - flag to disable loading of mavenrc files
|
|
||||||
@REM ----------------------------------------------------------------------------
|
|
||||||
|
|
||||||
@REM Begin all REM lines with '@' in case MAVEN_BATCH_ECHO is 'on'
|
|
||||||
@echo off
|
|
||||||
@REM set title of command window
|
|
||||||
title %0
|
|
||||||
@REM enable echoing by setting MAVEN_BATCH_ECHO to 'on'
|
|
||||||
@if "%MAVEN_BATCH_ECHO%" == "on" echo %MAVEN_BATCH_ECHO%
|
|
||||||
|
|
||||||
@REM set %HOME% to equivalent of $HOME
|
|
||||||
if "%HOME%" == "" (set "HOME=%HOMEDRIVE%%HOMEPATH%")
|
|
||||||
|
|
||||||
@REM Execute a user defined script before this one
|
|
||||||
if not "%MAVEN_SKIP_RC%" == "" goto skipRcPre
|
|
||||||
@REM check for pre script, once with legacy .bat ending and once with .cmd ending
|
|
||||||
if exist "%USERPROFILE%\mavenrc_pre.bat" call "%USERPROFILE%\mavenrc_pre.bat" %*
|
|
||||||
if exist "%USERPROFILE%\mavenrc_pre.cmd" call "%USERPROFILE%\mavenrc_pre.cmd" %*
|
|
||||||
:skipRcPre
|
|
||||||
|
|
||||||
@setlocal
|
|
||||||
|
|
||||||
set ERROR_CODE=0
|
|
||||||
|
|
||||||
@REM To isolate internal variables from possible post scripts, we use another setlocal
|
|
||||||
@setlocal
|
|
||||||
|
|
||||||
@REM ==== START VALIDATION ====
|
|
||||||
if not "%JAVA_HOME%" == "" goto OkJHome
|
|
||||||
|
|
||||||
echo.
|
|
||||||
echo Error: JAVA_HOME not found in your environment. >&2
|
|
||||||
echo Please set the JAVA_HOME variable in your environment to match the >&2
|
|
||||||
echo location of your Java installation. >&2
|
|
||||||
echo.
|
|
||||||
goto error
|
|
||||||
|
|
||||||
:OkJHome
|
|
||||||
if exist "%JAVA_HOME%\bin\java.exe" goto init
|
|
||||||
|
|
||||||
echo.
|
|
||||||
echo Error: JAVA_HOME is set to an invalid directory. >&2
|
|
||||||
echo JAVA_HOME = "%JAVA_HOME%" >&2
|
|
||||||
echo Please set the JAVA_HOME variable in your environment to match the >&2
|
|
||||||
echo location of your Java installation. >&2
|
|
||||||
echo.
|
|
||||||
goto error
|
|
||||||
|
|
||||||
@REM ==== END VALIDATION ====
|
|
||||||
|
|
||||||
:init
|
|
||||||
|
|
||||||
@REM Find the project base dir, i.e. the directory that contains the folder ".mvn".
|
|
||||||
@REM Fallback to current working directory if not found.
|
|
||||||
|
|
||||||
set MAVEN_PROJECTBASEDIR=%MAVEN_BASEDIR%
|
|
||||||
IF NOT "%MAVEN_PROJECTBASEDIR%"=="" goto endDetectBaseDir
|
|
||||||
|
|
||||||
set EXEC_DIR=%CD%
|
|
||||||
set WDIR=%EXEC_DIR%
|
|
||||||
:findBaseDir
|
|
||||||
IF EXIST "%WDIR%"\.mvn goto baseDirFound
|
|
||||||
cd ..
|
|
||||||
IF "%WDIR%"=="%CD%" goto baseDirNotFound
|
|
||||||
set WDIR=%CD%
|
|
||||||
goto findBaseDir
|
|
||||||
|
|
||||||
:baseDirFound
|
|
||||||
set MAVEN_PROJECTBASEDIR=%WDIR%
|
|
||||||
cd "%EXEC_DIR%"
|
|
||||||
goto endDetectBaseDir
|
|
||||||
|
|
||||||
:baseDirNotFound
|
|
||||||
set MAVEN_PROJECTBASEDIR=%EXEC_DIR%
|
|
||||||
cd "%EXEC_DIR%"
|
|
||||||
|
|
||||||
:endDetectBaseDir
|
|
||||||
|
|
||||||
IF NOT EXIST "%MAVEN_PROJECTBASEDIR%\.mvn\jvm.config" goto endReadAdditionalConfig
|
|
||||||
|
|
||||||
@setlocal EnableExtensions EnableDelayedExpansion
|
|
||||||
for /F "usebackq delims=" %%a in ("%MAVEN_PROJECTBASEDIR%\.mvn\jvm.config") do set JVM_CONFIG_MAVEN_PROPS=!JVM_CONFIG_MAVEN_PROPS! %%a
|
|
||||||
@endlocal & set JVM_CONFIG_MAVEN_PROPS=%JVM_CONFIG_MAVEN_PROPS%
|
|
||||||
|
|
||||||
:endReadAdditionalConfig
|
|
||||||
|
|
||||||
SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe"
|
|
||||||
set WRAPPER_JAR="%MAVEN_PROJECTBASEDIR%\.mvn\wrapper\maven-wrapper.jar"
|
|
||||||
set WRAPPER_LAUNCHER=org.apache.maven.wrapper.MavenWrapperMain
|
|
||||||
|
|
||||||
set WRAPPER_URL="https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.2.0/maven-wrapper-3.2.0.jar"
|
|
||||||
|
|
||||||
FOR /F "usebackq tokens=1,2 delims==" %%A IN ("%MAVEN_PROJECTBASEDIR%\.mvn\wrapper\maven-wrapper.properties") DO (
|
|
||||||
IF "%%A"=="wrapperUrl" SET WRAPPER_URL=%%B
|
|
||||||
)
|
|
||||||
|
|
||||||
@REM Extension to allow automatically downloading the maven-wrapper.jar from Maven-central
|
|
||||||
@REM This allows using the maven wrapper in projects that prohibit checking in binary data.
|
|
||||||
if exist %WRAPPER_JAR% (
|
|
||||||
if "%MVNW_VERBOSE%" == "true" (
|
|
||||||
echo Found %WRAPPER_JAR%
|
|
||||||
)
|
|
||||||
) else (
|
|
||||||
if not "%MVNW_REPOURL%" == "" (
|
|
||||||
SET WRAPPER_URL="%MVNW_REPOURL%/org/apache/maven/wrapper/maven-wrapper/3.2.0/maven-wrapper-3.2.0.jar"
|
|
||||||
)
|
|
||||||
if "%MVNW_VERBOSE%" == "true" (
|
|
||||||
echo Couldn't find %WRAPPER_JAR%, downloading it ...
|
|
||||||
echo Downloading from: %WRAPPER_URL%
|
|
||||||
)
|
|
||||||
|
|
||||||
powershell -Command "&{"^
|
|
||||||
"$webclient = new-object System.Net.WebClient;"^
|
|
||||||
"if (-not ([string]::IsNullOrEmpty('%MVNW_USERNAME%') -and [string]::IsNullOrEmpty('%MVNW_PASSWORD%'))) {"^
|
|
||||||
"$webclient.Credentials = new-object System.Net.NetworkCredential('%MVNW_USERNAME%', '%MVNW_PASSWORD%');"^
|
|
||||||
"}"^
|
|
||||||
"[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; $webclient.DownloadFile('%WRAPPER_URL%', '%WRAPPER_JAR%')"^
|
|
||||||
"}"
|
|
||||||
if "%MVNW_VERBOSE%" == "true" (
|
|
||||||
echo Finished downloading %WRAPPER_JAR%
|
|
||||||
)
|
|
||||||
)
|
|
||||||
@REM End of extension
|
|
||||||
|
|
||||||
@REM If specified, validate the SHA-256 sum of the Maven wrapper jar file
|
|
||||||
SET WRAPPER_SHA_256_SUM=""
|
|
||||||
FOR /F "usebackq tokens=1,2 delims==" %%A IN ("%MAVEN_PROJECTBASEDIR%\.mvn\wrapper\maven-wrapper.properties") DO (
|
|
||||||
IF "%%A"=="wrapperSha256Sum" SET WRAPPER_SHA_256_SUM=%%B
|
|
||||||
)
|
|
||||||
IF NOT %WRAPPER_SHA_256_SUM%=="" (
|
|
||||||
powershell -Command "&{"^
|
|
||||||
"$hash = (Get-FileHash \"%WRAPPER_JAR%\" -Algorithm SHA256).Hash.ToLower();"^
|
|
||||||
"If('%WRAPPER_SHA_256_SUM%' -ne $hash){"^
|
|
||||||
" Write-Output 'Error: Failed to validate Maven wrapper SHA-256, your Maven wrapper might be compromised.';"^
|
|
||||||
" Write-Output 'Investigate or delete %WRAPPER_JAR% to attempt a clean download.';"^
|
|
||||||
" Write-Output 'If you updated your Maven version, you need to update the specified wrapperSha256Sum property.';"^
|
|
||||||
" exit 1;"^
|
|
||||||
"}"^
|
|
||||||
"}"
|
|
||||||
if ERRORLEVEL 1 goto error
|
|
||||||
)
|
|
||||||
|
|
||||||
@REM Provide a "standardized" way to retrieve the CLI args that will
|
|
||||||
@REM work with both Windows and non-Windows executions.
|
|
||||||
set MAVEN_CMD_LINE_ARGS=%*
|
|
||||||
|
|
||||||
%MAVEN_JAVA_EXE% ^
|
|
||||||
%JVM_CONFIG_MAVEN_PROPS% ^
|
|
||||||
%MAVEN_OPTS% ^
|
|
||||||
%MAVEN_DEBUG_OPTS% ^
|
|
||||||
-classpath %WRAPPER_JAR% ^
|
|
||||||
"-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" ^
|
|
||||||
%WRAPPER_LAUNCHER% %MAVEN_CONFIG% %*
|
|
||||||
if ERRORLEVEL 1 goto error
|
|
||||||
goto end
|
|
||||||
|
|
||||||
:error
|
|
||||||
set ERROR_CODE=1
|
|
||||||
|
|
||||||
:end
|
|
||||||
@endlocal & set ERROR_CODE=%ERROR_CODE%
|
|
||||||
|
|
||||||
if not "%MAVEN_SKIP_RC%"=="" goto skipRcPost
|
|
||||||
@REM check for post script, once with legacy .bat ending and once with .cmd ending
|
|
||||||
if exist "%USERPROFILE%\mavenrc_post.bat" call "%USERPROFILE%\mavenrc_post.bat"
|
|
||||||
if exist "%USERPROFILE%\mavenrc_post.cmd" call "%USERPROFILE%\mavenrc_post.cmd"
|
|
||||||
:skipRcPost
|
|
||||||
|
|
||||||
@REM pause the script if MAVEN_BATCH_PAUSE is set to 'on'
|
|
||||||
if "%MAVEN_BATCH_PAUSE%"=="on" pause
|
|
||||||
|
|
||||||
if "%MAVEN_TERMINATE_CMD%"=="on" exit %ERROR_CODE%
|
|
||||||
|
|
||||||
cmd /C exit /B %ERROR_CODE%
|
|
||||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user