Add Quadrapassel CoCo specification and reviewed implementation workflow

This commit is contained in:
Brian Holman committed 2026-11-10 15:15:49 -07:00
commit 8a4b44bc73
13 files changed
+2250

No files matched your search

+73
View File
@@ -0,0 +1,73 @@
# Provenance and permitted use of reference material
## Behavioral reference
The specification was prepared from Brian Holman's
[Quadrapassel macOS fork](https://github.com/bkholman/quadrapassel-macos), revision
`be8769a403e506edb930372f963a9c4c83a0881e` ("Update references for
quadrapassel-macos repository"). Its upstream is
[GNOME Quadrapassel](https://gitlab.gnome.org/GNOME/quadrapassel).
Files reviewed for the specification include `src/game.vala`,
`src/game-view.vala`, `src/quadrapassel.vala`, `src/style.css`,
`data/org.gnome.Quadrapassel.gschema.xml`, `tests/test-scoring.vala`,
`tests/test-scoreboard.vala`, `README.md` and `COPYING`.
Their observed SHA-256 values are in [reference/source-manifest.json](reference/source-manifest.json).
The 28 piece states in [pieces.json](reference/pieces.json) were extracted from
`BLOCK_TABLE` in `src/game.vala` without changing positions or state order.
The numeric cases in [scoring.json](reference/scoring.json) express the reference
scoring rules and regression expectations, including new-level multiplication.
These files are data for the new implementation, not a bundled Vala application.
The implementation chat is intentionally restricted to this self-contained
specification and allowed public/reference material. The source links and hashes
above preserve attribution; they do not authorize that chat to inspect the Mac
source or its development chat. This is a black-box boundary around the emulator
and a specification-based implementation workflow, not a claim of legally
independent provenance from the GPL game.
## Credits and licensing
The reference application is **GPL-3.0-or-later**. `COPYING` preserves its GNU
GPL version 3 license text. `src/game.vala` credits **Robert Ancell (2010–2013)**
and **Lubomir Rintel (2009)**. The application's credits include **J. Marcin
Gorycki, Lubomir Rintel, Robert Ancell, John Ward, Will Warner**, and **Brian
Holman (macOS port)**. The difficult-piece selection describes its algorithm as
originating in **Federico Poloni's Bastet**. Retain these credits in the port.
The specification and derived piece/scoring reference data are distributed under
GPL-3.0-or-later. Future game code derived from them should preserve that license
and the relevant notices. The Mac fork's separate libgnome-games-support library
has its own LGPL-3.0-or-later terms; that library is not included here.
Pierre Sarrazin's CMOC/compiler and individual libraries/examples have their own
notices, including public-domain components. Check the exact files used; do not
label every example or bundled library GPL or public domain. Using a public API
does not require copying its implementation. No third-party sound recordings,
ROMs, Mac binaries or emulator source were imported into this repository.
## Supplied title image
[title-reference.png](reference/title-reference.png) is the image Brian supplied
for this project and explicitly authorized as its title reference. It is retained
unchanged and is **design reference only**, not a CoCo screenshot or runtime asset.
Its hash is recorded in the manifest. This permission is not a general grant to
relicense every visual element for unrelated reuse.
The CoCo screen should recreate the composition at native resolution with its
own game graphics: dark grid, colored tetrominoes and a readable title. Replace
the Mac platform wording with **for CoCo**. No other game's assets or implementation
are required for this reference treatment.
## Explicit adaptations
The specification identifies behavior adapted for the CoCo: conventional
persistent hold swapping, bounded score storage and rule markers, a compact
deterministic PRNG rather than GLib stream compatibility, one-button joystick
menus, lower-color CoCo 2 graphics, approximate tone sequences, and safe handling
of pieces above the board. They must not be described as byte-for-byte Mac parity.
Hardware feasibility, timing, physical palette appearance, API performance and
disk layout are still to be demonstrated by the implementation. The arithmetic
memory estimates and reference tests do not establish a working CoCo build.