IV Complete Example Programs
Start with a result you would like to make. Each chapter shows selected frames, the complete source files, a short explanation of their structure, and a command that renders the example. The programs are read from the repository, not copied into the manual.
The Guide teaches each idea in order. The Cookbook answers short questions. This part shows how those ideas fit together in a whole program.
Choose a program
Example |
| Study it for |
| The smallest complete Scene and a final hold. | |
| A sampled curve, a reveal, and a shared group. | |
| Three slides, named beats, and a render project. | |
| One derivation carried across two layouts. | |
| A construction, narration timing, and playback. | |
| Named children that rearrange across a transition. | |
| A 3D lesson split into three related files. | |
| A longer Scene divided into editable blocks. |
Running the examples
Run the shell commands from the Animate checkout root, with Animate installed in the Racket installation you use. The commands use racket and raco from your PATH; a full path to either executable works too. MP4 commands need FFmpeg. Each chapter names any additional requirements.
Most source files only export a description. Running such a file by itself does not show a window or write a movie. Use the command printed in its chapter. Choose a fresh output location rather than mixing a new render with old files.
The illustrations are stored samples of Scenes and storyboards. Captions retain their original times. Gallery-supplied captures are identified as such; they illustrate the same example without claiming to be newly encoded MP4 frames. Changing a source file does not automatically regenerate its stored pictures.