deck3d-from-pptx

deck3d-from-pptx

Take a real .pptx and rebuild it as a deck3d presentation whose slides match the original when the camera stops and move through 3D space between slides. Every creative decision is the user's: you generate variants, show them, ask, and record the answer in style.json. The deck3d rules of the deck3d tune loop still apply: never edit deck.html, never edit derived IR fields (only overrides), no randomness, timers or network in local effects, and finish with deck3d check deck.html --style clean — or every remaining warning explained (a derived credits slide counts as explained).

Detail per step (what to read, how to author variants, which samples, the question): reference/steps.md.

0. Import and reference renders (always first)

deck3d pptx import talk.pptx -o talk [--ref exports/]

writes talk/pptx/layout.json (1920-unit slide space, items with stable ids sNN-iMMM), talk/pptx/media/, a baseline deck.md and deck.json whose overrides.assets pin the layout and every media file. Unsupported constructs (charts, SmartArt, tables, EMF/WMF, WordArt, gradient fills…) become visible fallback items — a crop of the reference render, else an outlined placeholder — each with one warning.

Reference renders come first. Ask the user (ask_user) for a PNG export of the deck (PowerPoint: File → Export → PNG, all slides; Keynote and Slide1.PNG names work) and pass the folder as --ref. Skip the question only when LibreOffice (soffice) and pdftoppm are on PATH. If the user declines, say so once, and from then on every step reports snapshot review (deck3d snapshot, eyeballing, check) instead of compare scores — never pretend a score exists.

Then build the baseline: cd talk && deck3d build deck.md -o deck.html (a native deck3d slide per pptx slide). Re-importing later keeps your tuning: deck3d pptx import talk.pptx -o talk --force matches slides by content, backs up deck.json.bak, and deck3d variants replay re-applies every recorded pick.