Changes between Version 7 and Version 8 of ChimeraAnimationDiscussions

Timestamp:

Oct 5, 2010, 2:11:17 PM (16 years ago)

Author:

Darren Weber

Comment:

--

ChimeraAnimationDiscussions

@@ -27 +27 @@
 
  * Chimera meeting discussion: Oct 4, 2010
-   * Short demo of pilot implementation of animation commands and GUI, see: 
+   * Short demo of pilot implementation of animation commands and GUI, e.g.: 
 {{{
 git clone ssh://chimera@weber.cgl.ucsf.edu/data/gitroot/chimera-extension
@@ -65 +65 @@
        * Some facets of transitions may be dependent on model components or attributes
      * Transitions for display: problems for transparency
+       * Do we have or can we implement model level transparency?  Is this useful? 
        * Implications for core graphics engine in handing animation of transparency values
-       * May be problems for multiple models, spatial ordering (depth peeling)
-       * Transparency specificity for components of models (ligands, etc., or surfaces) 
+       * Currently there are problems in the display of multiple models (depth peeling issue)
+       * Do we need transparency specificity for components of models (ligands, surfaces, etc.)?
      * Transition components
        * Components include: spatial, model styles, display (appearance, disappearance), color, titling (labels), clipping planes, etc.
-       * Additive or cumulative constructs for transitions, with potential for independence
-     * Animation features should include morphing (trajectories)
+       * Independent constructs for transitions, with potential for cumulative effects
+       * Consider the EMANimator Memory GUI where states can be restored by specific components (color, motion, camera)
+       * Midas command qualifications: kfshow pos <kfname> ..., kfshow camera <kfname> ..., reset color <kfname> ...
+     * Animation features to include morphing (trajectories)
        * Might call up the morph utility
-     * Animation sequence could be saved as a command sequence
-       * Possible to run it at a later time and edit the sequence code
+     * Animation sequence may be saved as a command sequence
+       * Could be possible to edit the sequence code as a Midas command file or a python script
+       * Could be possible to run it at a later time and edit the sequence code
        * Saving and loading a sequence command file
      * Session support
        * Key frame data structures, transitions, etc. saved to session files
      * Advanced options
-       * Facility to run python code; per-frame script option
+       * Facility to run python code
+       * A per-frame script option (as in morph utility)