TR4W

Tr4w D12 — Git skill for Claude Code

Git community

FreePascal / UnicodeString modernization of TR4W.

How to install Tr4w D12

This entry records only its repository, not the path inside it, so there is no exact command to give. Open TR4W/TR4W-D12 and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Tr4w D12 does

FreePascal / UnicodeString modernization of TR4W. Isolated from TR4W/TR4W (which stays on D7 for production/monthly builds). Work lives on the fpc branch. This conversion has made extensive use of Claude Code for agentic coding..

Alternatives in Git

Git Worktree Setup — Create isolated git worktrees with instant feedback and background Rust verification 25.5k ★
Worktree Deliver — Commit all work, push, and create a pull request from the current worktree 23.4k ★
Container Use — by dagger - Development environments for coding agents 3.6k ★

README

TR4W

TRLOG 4 Windows free amateur radio logging application https://tr4w.net

New to contesting? The big loggers are powerful — and intimidating enough that most newcomers give up and just use their everyday logger, missing dupe checking, spotting, and live scoring. TR4W takes the other path: type the exchange in plain order into one field, let the software handle CW and FT8 for you, and plug a modern radio straight into the network. Real contest features, none of the learning cliff.

Free and open-source.

We welcome you to check out the code. Want to see how to send multi-cast UDP from a FreePascal app to WSJT-X? It is in the code. Want to see how to talk to a Kenwood, Elecraft, Flex or Icom radio over the network? What about statically linking to the hamlib C library? All there for the viewing. What about code to automatically download the latest CTY.DAT or POTA parks file. All here too...

The benefit of this being open source is you get to not only see how the program works, but you can use it for your own projects. You are welcome to take parts of our code for your own projects. Leave the copyright notice and it is customary to attribute the source material. We want to share what we have done here. Unlike too many open source projects, we do not feel like we can get the benefit of open source but still get to dictate the terms of how you use the software. We relied upon the community to help us develop this project. We're darn well going to let the community use it on their own terms. Isn't that what open source should be?