Repository navigation
docs(architecture): design motion files for movies - #41
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds architecture 8.13 "Motion Files (planned)" (EN/JA): a YAML file (
yui-motion/1) that scripts camera turns about any axis, zoom, wait, frame stepping and representation changes (set:visible/opacity, with fade) for repeatable movies.Why
Users want to turn about a chosen axis by a chosen angle, and to save a fixed motion as a movie. The design keeps representations in the workspace (no second definition), validates the whole file before the first frame, and moves the camera rotation to quaternions (no elevation clamp) without changing the saved
CameraState.Design only; nothing is implemented yet. Planned PR order: (1) quaternion rotation, (2) file reading and export, (3)
set.Checks (
scripts/check.sh --trunk)Not checked: nothing skipped. No CHANGELOG entry, because there is no user-visible change.