53 Modules to require
Choose the module for the task. You do not need to import every adapter merely to write a slide description. The supported Animate slide combinations use ordinary, unprefixed imports.
Module |
| Use it for |
| Visuals, Scenes, cameras, animation requests, and sampling. | |
| Source-program blocks and authored timelines. | |
| Interactive preview, reload, and inspection. | |
| Source, render, output, encoder, and cache declarations. | |
| PNG files, video encoding, media assembly, and project execution. | |
| Content, layouts, themes, slide clips, and storyboards. | |
| Static pictures and sampled Picts. | |
| Native Scenes/timelines and native content wrappers. | |
| Slide preparation and match-plan inspection. | |
| Mathematical presentation plans as slide content. | |
| Geometry programs/timelines as slide content. | |
| Restartable storyboard sources for render projects. | |
| Gallery entries and selected gallery storyboards. |
animate/slides/render prepares content; despite its name, it does not encode the final video. File output and project execution belong to animate/render. Geometry in slides uses parent-prepared data when a project sends work to subprocesses.
Use animate/experimental only for lower-level extensions such as derived-visual. For an object that follows other scene values, prefer relation-visual, which declares its inputs explicitly.
Importing the description modules should not open a preview window or render a movie. Keep calls that do so in an explicit runner. See Objects, scenes, and output and Make a slide and give it time.