Add Magma Hub firmware spec for Pico developers
New wiki page covering the exact I2C protocol the Pico must implement:
slave configuration, memory map, button bitmasks, joystick encoding,
select-write handshake, IRQ-driven implementation pattern, and error
handling. Links from the existing Magma Hub and I2C page.
4053e2a
Document 0.5.0: scenes, entity groups, audio, player seats, theming
Three new pages — Scenes and Game Structure (modality as a stack, the
flags-to-scenes migration table), Audio (the backend tiers and the WAV
guarantee), and Players and Multi-Controller (join, hotplug, and why a
returning controller reclaims the same seat).
Updated for the release: Rendering and Camera (follow() now requires dt —
the 0.4.0 deprecation landed), UI Components (theming, with the pinned
DEFAULT_THEME guarantee), Input (player-seats pointer), Core Concepts (the
stack as the recommended shape past one screen), Getting Started, Home,
sidebar, and the Hardware Dev Kit's hotplug cross-link.
Every code sample on the changed pages was executed before committing.
8f428f4
Remove the last pre-0.3.0 claim about dialogue timing
The DialogueBox section still ended by saying typing runs off the canvas's own
after() timer and continues while the game is paused. That is the behaviour
0.3.0 removed, and it contradicted the frame-driven section added earlier on
the same page.
Replaced with what actually holds: a paused loop is a paused typewriter, and
the way to animate dialogue over a frozen world is to call update(dt) first and
early-return from the rest — which is what examples/game_template.py does.
93c2b35
Document 0.4.0: hardware dev kit, and correct what 0.3.0 left stale
Adds Hardware Dev Kit — the simulator, the test bench, background polling and
record/replay — and fixes several pages that had drifted out of true.
The corrections matter more than the new page:
- UI Components still described the pre-0.3.0 DialogueBox, claiming the
typewriter ran on its own canvas.after() timer and kept animating while the
game was paused. That behaviour was removed in 0.3.0; a reader following the
page got a dialogue that never appeared. The frame-driven contract is now
stated up front, in its own section.
- Rendering and Camera said smoothing was per-call rather than per-second and
suggested working around it by hand. dt has existed since 0.3.0 and is the
answer; omitting it is deprecated as of 0.4.0.
- Getting Started called camera.follow() without dt in both listings, so the
tutorial emitted DeprecationWarnings on a clean run.
- Input demonstrated writing a custom source with a class named ReplayInput,
which 0.4.0 turned into a real engine class — the example now shows an
autopilot instead, and points at the real one.
- Releasing described token-based publishing. 0.4.0 moved to Trusted
Publishing, and the page now documents the two ways it silently fails: a
permissions block that omits id-token: write, and a password: input that
disables TP even when the secret it names does not exist.
- Contributing's "where things live" table predated four modules and the
devtools package.
Every code sample on the changed pages was executed before committing, per the
page's own convention.
0cb8fb2
Correct the Releasing page: token-based publishing, not Trusted Publishing
7bf85e0
Write the texastoast wiki
Replaces the default stub with 14 pages: getting started, core concepts,
per-subsystem reference, a 0.2.0 migration guide, and project process.
Every code snippet was executed against texastoast 0.2.0 rather than written
from the API surface.
2cce30b