Chet Haase | faebd8f | 2012-05-18 14:17:57 -0700 | [diff] [blame] | 1 | <html> |
| 2 | <body> |
| 3 | <p>The classes in this package enable "scenes & transitions" functionality for |
| 4 | view hiearchies.</p> |
| 5 | |
| 6 | <p>A <b>Scene</b> is an encapsulation of the state of a view hiearchy, |
| 7 | including the views in that hierarchy and the various values (layout-related |
| 8 | and otherwise) that those views have. A scene be defined by a layout hierarchy |
| 9 | directly or some code which sets up the scene dynamically as it is entered.</p> |
| 10 | |
| 11 | <p>A <b>Transition</b> is a mechanism to automatically animate changes that occur |
| 12 | when a new scene is entered. Some transition capabilities are automatic. That |
| 13 | is, entering a scene may cause animations to run which fade out views that |
| 14 | go away, move and resize existing views that change, and fade in views that |
| 15 | become visible. There are additional transitions that can animate other |
| 16 | attributes, such as color changes, and which can optionally be specified |
| 17 | to take place during particular scene changes. Finally, developers can |
| 18 | define their own Transition subclasses which monitor particular property |
| 19 | changes and which run custom animations when those properties change values.</p> |
| 20 | |
| 21 | <p><b>TransitionManager</b> is used to specify custom transitions for particular |
| 22 | scene changes, and to cause scene changes with transitions to take place.</p> |
| 23 | |
| 24 | </body> |
| 25 | </html> |