Repository navigation
Release 1.0.0 - #15
Merged
Merged
Conversation
This PR gets SNAILNET ready to release. It adds a Gitea Actions pipeline (build-release.yml) with four jobs: - build compiles the x64 Release SnailNet.exe. - test runs the command line test suite against that build and publishes a readable HTML report listing each test, its result, and the commands it ran. - docs renders Docs/userguide.md to userguide.pdf using the shared GitOps userguide-pdf action. - release runs on v* tags and attaches the exe, the PDF, and the test report to a Gitea Release. The documentation is restructured: - The README is now aimed at developers. - There are three lowercase guides: userguide.md, shipped as the PDF; developerguide.md, covering build, release, and CI; and testguide.md. - The logo moves to Docs/image.png, and the unused image and the redundant Tests/README.md are removed. The code is cleaned up: - All Sockets defines and hard-coded values move into a new SocketsConstants.h. - The CLI test harness now stops the program with Ctrl+Break instead of Ctrl+C. - Dead test helpers and the pytest-html dependency are removed, and there is a small pytest plugin for the static report. Pre-commit now includes a markdownlint hook, configured in the existing .pre-commit-config.yaml with no extra config file. Reviewed-on: https://gitea.com/Kyle-Spicer/SNAILNET/pulls/12 Co-authored-by: Kyle Spicer <kyledspicer@gmail.com>
Workflow moves to .github/workflows, uses the GitOps actions from KyleSpicer/GitOps, publishes releases with softprops/action-gh-release, and still runs on the self-hosted tweedledum runner. Fork pull requests are skipped so untrusted code never runs on it. Docs and package URLs now point at github.com/KyleSpicer/SNAILNET.
actions/checkout@v7 and actions/download-artifact@v8 replace the v4 releases, which target the deprecated Node.js 20 runtime. Artifacts are downloaded by name, so the v5 path change does not apply.
The main window can now be resized and maximized, and the fields widen to fit. Layout sizes are defined at 96 DPI and scaled to the window's DPI on every WM_SIZE, WM_GETMINMAXINFO keeps the client area from shrinking below its starting size, and WM_DPICHANGED re-lays the window out when it moves to a monitor with a different scale. The process opts into per-monitor v2 DPI awareness before any window is created, so Windows scales the frame and common controls instead of stretching a 96 DPI bitmap. Also adds CHANGELOG.md for user-visible changes, a step in the developer guide to update it, and a note on resizing in the user guide. Part of #11 (DPI awareness).
Make the window resizable and DPI aware
Complete development, documentation and testing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First release of SnailNet:
(to client, to target, or both ways)
short flags