The Living Gallery release — Parallax Sketchbook

SKETCHBOOK / 08 The Living Gallery · 2-week chapter

Page 1 of 3: Freeze one complete lifecycle

Capstone / release scope

Freeze one complete lifecycle

Choose a finishable workflow: prepare an owned asset, publish only the current generation, display or save its result, replace it once, and shut down cleanly. A CPU-only gallery is a valid finished subset when its UI and implementation claims say so.

The supplied gallery now prepares actual images in a bounded background service, rejects stale completion, preserves the last good image, and saves it. You also have a tiled PMR renderer and an optional Asio coroutine experiment. These are separate, deliberately small reference programs; a streaming file decoder, cache eviction policy, renderer window, and GPU resource retirement still need their own integration work.

Write an explicit contribution statement and credit the reference code and primary reading. Your release should show an original adaptation, tests that address its risks, and a result someone else can reproduce, rather than presenting the companion executable unchanged as a new engine.

TRY IT IN YOUR STUDIO

Write the one-paragraph release scope before editing features. Include one deferred subsystem and one supported platform claim you can actually test.

From the page to your own work

Your studio assignment.

Release your original Living Gallery subset with a reviewable lifetime story.

A finish line you can see

A reproducible application subset, owner/shutdown diagrams, failure tests, one measurement, and a contribution statement.

Demonstrate normal, failed, stale, and cancelled work.
Join before borrowed state is released.
Separate reference code, your changes, and planned integrations.
State tested hosts and known limitations.

Keep the evidence in your weekly notebook ↗

Explain it like an engineer

Try answering aloud before opening the review notes. Use your own implementation as evidence.

Walk me through closing the gallery while an asset replacement is running.

Stop admission and choose the publication policy.
Request cooperative cancellation or finish bounded work.
Join CPU work, then follow any real backend retirement requirements before destroying owners.

These prompts support practice; they are not an automatic assessment of your work.

A tip for this exercise

Freeze one complete prepare, publish, replace, and close workflow for the release. A small CPU gallery can demonstrate ownership and shutdown clearly when the contribution statement identifies your adaptation and every deferred integration.

Hints, when you need them.

Try a first step, then reveal as much help as you need. Each hint gets a little more specific.

1Hint 1 · Find a starting point

Choose the one asset operation your release will support. Follow its owners from accepted input through publication and replacement, marking the boundary that ends each borrow.

2Hint 2 · Choose an approach

Rehearse success, failed work, stale completion, cancellation, and rejected oversized input. Record what stays published in each case, and use deterministic synchronization when testing shutdown during active preparation.

3Hint 3 · Check your reasoning

Run the smoke workflow from your written build commands, replace one asset twice in reversed completion order, and close during a gated job. Request stop, verify joined completion before owner destruction, and include the tested-host evidence.

A small creative variation ↗

Replace one asset twice in a deterministic test and write the observed publication sequence.

Optional. Save it for later if this chapter already feels full.

Coming back after a break? ↩

Run the smoke workload and close one release checklist item instead of adding another subsystem.

Books & principles behind this study +

Original Parallax explanations and assignments, with these works for further reading.

YOUR MARGIN NOTES

Leave yourself a good question.

What changed your mind? What would you try next?

Notes for The Living Gallery release

Notes are private to this browser and saved as you write.

A CHECKPOINT, NOT A SCORE

Can you explain the idea and try the exercise yourself?

Completion records your own assessment. It does not compile or test your C++.

Companion source 14 files