3dtours
0b827ecfa3
A reading was made to say so on one row only — the folder it was kept to — and that row is the wrong row to say it alone, because it is the row a folded branch takes away. A reader who has closed the folder being read, or who is looking at a branch of it, is left with a tree in which nothing at all is happening while a reading runs under the fold. The rows that say a reading is under way are now the folder it was kept to and every folder above it on the way down. Depth is the whole of the rule: the way down is what the eye follows to reach the folder, so a mark on that path is a mark the reader can walk to the work from. The roll's own row is the exception, and the reason is the same depth read the other way. A roll is the head of everything under it, and a roll that marks itself while one folder of it is being read tells the reader that the whole of it is being read — the one answer a tree of a hundred folders cannot afford, and the exact answer the row's counts were already forbidden from giving. The roll says so only when the roll itself is the folder being read. Nothing under the row being read says anything at all: a reading has not reached the folders below it, and a mark there would be a row claiming work done in a folder nothing has yet looked at. The rule turns on one of those boundaries being emptier than it looks. The path of the picked folder is the empty string, and every path has the empty string in front of it, so a prefix test against the way down answers yes for the head of the tree no matter which folder below it is being read — the roll marking itself for a branch was not an exception that had to be written, but a comparison that had to be spelled so the empty path is asked about its own self and nothing else.
RecipesCam
RecipesCam is a camera and photo-editing app built around recipes — reusable
looks that carry a film simulation plus a full set of adjustments. You shoot or
open a photo, dial in a look, and keep it as a recipe you can apply again, share
as a .recipe file, or save to your account.
It ships twice from one repository: a React Native (Expo) app for iOS and
Android, and a self-contained web build under docker/ that runs the same
render pipeline in the browser.
What it does
- Shoot with a recipe applied. Live viewfinder, GPS-tagged captures, and the recipe baked into the saved file.
- Film simulations. Built-in looks — PROVIPES, VELVIPES, CLASSIC CHRIPES, CLASSIC NEGIPES, ASTIPES, ETERNIPES, ACRIPES, B&W HIGH CONTRAST and the LC STREETLIFE pair — each with its own grain and tone curve.
- The full adjustment set. Exposure, contrast, highlights and shadows, saturation, colour temperature, clarity, grain, and an HSL mixer with a colour picker that samples straight off the photo.
- Geometry. Crop to a fixed ratio or free-form, quarter turns, and a straighten ruler, plus printed frames (classic border, retro instant, wall frame portrait/landscape).
- Finishing. Watermark and GPS stamp, EXIF carried through the export, JPEG written with a proper 300 DPI JFIF header.
- On-device upscaling. A Real-ESRGAN pass runs locally when an export asks for more pixels than the source has — no server sees the photo.
- Recipes. Save, favourite, export and import
.recipefiles; the web build keeps them in your account, the phone build also keeps them on device.
The two builds
| Build | Where | Stack |
|---|---|---|
| iOS / Android | repo root | Expo + React Native, @shopify/react-native-skia for the render pipeline, NativeWind for styling |
| Web | docker/ |
Vite + React, CanvasKit (canvaskit-wasm) for the same pipeline, Fastify + SQLite API for accounts and recipes |
The render engine is shared by design: the web build compiles the app's own
src/utils/* and type definitions unchanged, with @shopify/react-native-skia
aliased to a CanvasKit shim (docker/frontend/src/engine/skiaShim.ts). A look
looks the same on both because it is the same code.
Running the web build
cd docker
cp .env.example .env
docker compose up -d --build
# → http://localhost:8090
Photos never leave the browser: grading, framing, watermarking and JPEG
encoding all run in the visitor's tab; the API only stores accounts and recipe
JSON. See docker/README.md for the layout and the proxy setup.
Running the app
npm install
npx expo start # Expo Go / dev client
npx expo run:android # or run:ios for a native build
Repository layout
App.tsx, src/ the Expo app: screens, tool rail, viewfinder, shaders
docker/ the web build (frontend + API + compose file)
frontend/shared/ vendored copies of the app's types and utils
frontend/src/engine/ CanvasKit shim, export engine, super-resolution
docs/ privacy policy
THIRD_PARTY_NOTICES.md licences of the bundled fonts, models and libraries
Licence
See LICENSE and THIRD_PARTY_NOTICES.md.