| 49 | | * Discussion notes: |
| 50 | | * Additional GUI for animation sequence |
| 51 | | * Drag-n-drop from key frame layout into an animation sequence |
| 52 | | * The sequence interface can be an abstract representation of a time-line, with discrete scenes and transitions between scenes |
| 53 | | * There can be a default transition between key frames (create a preferences setting) |
| 54 | | * Auto-detection of component changes between key frames |
| 55 | | * Features for grouping key frames into a loop sequence |
| 56 | | * Features for multiple instances of a key frame in the sequence |
| 57 | | * Options to pause a sequence (esp. at the end of a loop sequence) |
| 58 | | * Features to control execution of the sequence: play | pause toggle, stop, rewind, fast-forward |
| 59 | | * Feature to record a movie of the sequence |
| 60 | | * Might call up movie recorder |
| 61 | | * Saving animation sequence using povray rendering |
| 62 | | * Key frame integrity checking |
| 63 | | * Handle the presence or absence of model data |
| 64 | | * Transition specifications independent of models |
| 65 | | * Some facets of transitions may be dependent on model components or attributes |
| 66 | | * Transitions for display: problems for transparency |
| 67 | | * Implications for core graphics engine in handing animation of transparency values |
| 68 | | * May be problems for multiple models, spatial ordering (depth peeling) |
| 69 | | * Transparency specificity for components of models (ligands, etc., or surfaces) |
| 70 | | * Transition components |
| 71 | | * Components include: spatial, model styles, display (appearance, disappearance), color, titling (labels), clipping planes, etc. |
| 72 | | * Additive or cumulative constructs for transitions, with potential for independence |
| 73 | | * Animation features should include morphing (trajectories) |
| 74 | | * Might call up the morph utility |
| 75 | | * Animation sequence could be saved as a command sequence |
| 76 | | * Possible to run it at a later time and edit the sequence code |
| 77 | | * Saving and loading a sequence command file |
| 78 | | * Session support |
| 79 | | * Key frame data structures, transitions, etc. saved to session files |
| 80 | | * Advanced options |
| 81 | | * Facility to run python code; per-frame script option |
| 82 | | |
| 83 | | |
| | 49 | * Discussion notes: |
| | 50 | * Additional GUI for animation sequence |
| | 51 | * Drag-n-drop from key frame layout into an animation sequence |
| | 52 | * The sequence interface can be an abstract representation of a time-line, with discrete scenes and transitions between scenes |
| | 53 | * There can be a default transition between key frames (create a preferences setting) |
| | 54 | * Auto-detection of component changes between key frames |
| | 55 | * Features for grouping key frames into a loop sequence |
| | 56 | * Features for multiple instances of a key frame in the sequence |
| | 57 | * Options to pause a sequence (esp. at the end of a loop sequence) |
| | 58 | * Features to control execution of the sequence: play | pause toggle, stop, rewind, fast-forward |
| | 59 | * Feature to record a movie of the sequence |
| | 60 | * Might call up movie recorder |
| | 61 | * Saving animation sequence using povray rendering |
| | 62 | * Key frame integrity checking |
| | 63 | * Handle the presence or absence of model data |
| | 64 | * Transition specifications independent of models |
| | 65 | * Some facets of transitions may be dependent on model components or attributes |
| | 66 | * Transitions for display: problems for transparency |
| | 67 | * Implications for core graphics engine in handing animation of transparency values |
| | 68 | * May be problems for multiple models, spatial ordering (depth peeling) |
| | 69 | * Transparency specificity for components of models (ligands, etc., or surfaces) |
| | 70 | * Transition components |
| | 71 | * Components include: spatial, model styles, display (appearance, disappearance), color, titling (labels), clipping planes, etc. |
| | 72 | * Additive or cumulative constructs for transitions, with potential for independence |
| | 73 | * Animation features should include morphing (trajectories) |
| | 74 | * Might call up the morph utility |
| | 75 | * Animation sequence could be saved as a command sequence |
| | 76 | * Possible to run it at a later time and edit the sequence code |
| | 77 | * Saving and loading a sequence command file |
| | 78 | * Session support |
| | 79 | * Key frame data structures, transitions, etc. saved to session files |
| | 80 | * Advanced options |
| | 81 | * Facility to run python code; per-frame script option |
![[Chimera Issue Tracking System]](/trac/chimera/chrome/site/chimera_logo.png){kind=logo}
