# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Samples Points and expected field values are the file. Include: a point at a ball's centre, a point at distance r, a point far away, and a mid-point between the merge and the apart cases. ## Screenshot tolerance 8 levels, 98% of pixels, 1600 by 1000, camera in `fixtures/metaball-camera.json`. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A few soft bodies | Shown in a corner. | | `threshold` | Threshold | 1.0 | The iso-value of the surface, from 0.4 to 2.0. | | `normals` | Lit surface | on | If off, a flat colour is used. | | `grid` | Show the field grid | off | A faint grid, useful in tests. | | `field` | Falloff | inverse-square | How a ball contributes to the field. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `fixtures/metaball-camera.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/metaball-samples.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/metaball-set.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/field.png` | A golden render of the fixture soft bodies at threshold 1.0. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. Field samples at known points match a file within 1e-5 for both falloffs. A fixture set of balls renders to a golden. A documented merge and a documented apart case are confirmed by inside/outside samples. No network.