Changes between Version 2 and Version 3 of AnimationCommands


Ignore:
Timestamp:
Jun 14, 2011, 1:18:47 PM (15 years ago)
Author:
Darren Weber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • AnimationCommands

    v2 v3  
    11
    2 This page defines the animation command syntax and expected behavior (this is related to ticket:9055, see also ticket:9404).
     2This page defines the animation command syntax and expected behavior (this is related to ticket:9055, see also ticket:9404). 
    33
    4 Corrected scheme:
     4== Note on Syntax Style ==
    55
    6 (1) scene definition
     6Greg's suggested using [http://en.wikipedia.org/wiki/Extended_Backus-Naur_Form extended Backus-Naur form].  It was used it to define a [http://www.cgl.ucsf.edu/chimera/current/docs/UsersGuide/midas/nucleotides.html nucleotides command] (see the [https://plato.cgl.ucsf.edu/trac/chimera/browser/trunk/libs/NucleicAcids/cmd.py source code] comments too).
     7
     8== Animation command syntax ==
     9
     10Elaine's "corrected scheme" from ticket:9055.
     11
     12=== (1) scene definition ===
    713
    814{{{
    … …  
    1218}}}
    1319
    14 Notes:
     20==== Notes ====
    1521 - "scene-name" and "trans-name" are user-specified, see (2) for the latter.
    1622 - default scene not necessary.
    … …  
    2531 }}}
    2632
    27 (2) transition definition
     33=== (2) transition definition ===
    2834
    2935{{{
    … …  
    3440}}}
    3541
    36 Notes:
     42==== Notes ====
    3743 - Keywords could be different, I just wanted to convey purpose/scope
    3844   ... many many possibilities, e.g.
    3945   {{{
    40     color ( linear [f1,f2] | sigmoid [f1,f2] | abrupt f )
     46   color ( linear [f1,f2] | sigmoid [f1,f2] | abrupt f )
    4147   }}}
    42    where f are % fractions of the transition from the preceding scene 0
    43    and the next scene 100. A percentage is easier to type than values
    44    within the 0-1 range.
    45  - Would we want to allow different behaviors for different models?
     48   where f are % fractions of the transition from the preceding scene (0%) to the next scene (100%). A percentage is easier to type than values in the 0-1 range.
     49 - Would we want to allow different behaviour for different models?
    4650
    47 (3) animation between scenes, analogous to existing [http://www.cgl.ucsf.edu/chimera/docs/UsersGuide/midas/fly.html fly command]:
     51=== (3) animation between scenes ===
    4852
     53This may be analogous to the existing [http://www.cgl.ucsf.edu/chimera/docs/UsersGuide/midas/fly.html fly command]:
    4954{{{
    50 fly [master-frames] pos1 [[ frames1_2] pos2] \
    51     [[ frames2_3] pos3] ... [[ framesN-1_N] posN]
     55fly [master-frames] pos1 \
     56    [[ frames1_2] pos2] \
     57    [[ frames2_3] pos3] \
     58    ... \
     59    [[ framesN-1_N] posN]
    5260}}}
    53 
    5461see http://www.cgl.ucsf.edu/chimera/docs/UsersGuide/midas/fly.html
    5562
     63That is, we define a new command called 'animate' with similar syntax:
    5664{{{
    5765animate [master-frames[,master-trans]] scene1 \
    … …  
    6270}}}
    6371
    64 Notes:
    65  - scene*, trans* previously defined with scene and transition, respectively
    66  - alternative: expand existing fly command to do all this
     72==== Notes ====
     73 - scene*, trans* previously defined with scene and transition commands, respectively.
     74 - alternative: expand existing fly command to do all this.
    6775
    68 Concerns:
    69  - Does this limit transitions (other than positions, which would be splined as in "fly") to depending on only the bracketing pair of scenes?
    70  - Do we need fancier transitions that also depend on further preceding and following scenes?
     76 Concerns:
     77 - Does this limit transitions (other than positions, which would be splined as in "fly") to depending on only the bracketing pair of scenes?  Do we need fancier transitions that also depend on further preceding and following scenes?
    7178 - How does animation integrate with recording, 2dlabels, coordset, other commands with frame arguments (move,turn,rock,roll)? Simply as interleaved commands between "movie record" and "movie stop"? Could coordset or 2dlabels changes occur at the same time as other transitions?