ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated Animation Cases (markdown)

tschaub
2012-10-26 09:42:05 -07:00
parent d81a607980
commit bb397c04a9
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Animation-Cases.md
+10 -2
@@ -10,7 +10,11 @@ These types of animations change the map state (e.g. center and resolution) and
## Playback
These types of animation display changes in data over time. Typically the user would be presented with some playback controls and would start and stop the animation manually. An animation playback of this sort does not interfere with the animated changes in map state described above and vice versa (kinetic panning works as expected while watching the replay of a hurricane path).
These types of animation display changes in data over time. Typically the user would be presented with some playback controls and would start and stop the animation manually. An animation playback of this sort does not interfere with the animated changes in map state described above and vice versa.
**Examples**
* Hurricane track: a vector layer is populated with hurricane positions from a `gx:Track` in KML. The map is accompanied by a playback control that lets the user sit back and watch the position change over time. Things like kinetic panning work during this playback - though the application may also decide to center the map at the hurricane position at specific key frames.
## Display Effects
@@ -24,4 +28,8 @@ Some aspects of map rendering may be animated for a simple display effect (witho
## Things that are not Animations
* "Real-time" data updates: say we have a vector layer that streams data changes via a WebSocket. The layer may request a re-rendering of the map with every data change. The renderers should handle this in an efficient way (i.e. the layer shouldn't have to know how to animate, it should just demand a re-rendering with every data change).
There may be dynamic aspects of a map application that are not necessarily animation.
**Examples**
* "Real-time" data updates: say we have a vector layer that streams data changes via a WebSocket. The layer may request a re-rendering of the map with every data change. The renderers should handle this in an efficient way (i.e. the layer shouldn't have to know how to animate, it should just demand a re-rendering with every data change).