In favor of more straightforward scaling, the `dimensions` data key, whose value was an Object, has been replaced by numeric `width` a `height` keys.
No further use for width and height in the cache
New Boolean `responsive` option allows to turn on responsive mode. Reel can be responsive only in certain cases - when not sprite or stitched pano. Final decision is stored in `responsive` data key.
When responsive, the fixed dimensions are not applied leaving the image to grow freely with its parent
Original values of data keys which are supposed to be responsive are stored in the `truescale` key for later scaling.
Test for `responsive` option in the API
On browser window resize and on reel frame change, the instance is gauged against truescale and scale ratio is determined.
Annotations receive scaled position update
Adjusted preloader to position well even if scaled
As stitched nor sprites can not be responsive, there's no point in keeping the keys at the moment
Duplicated example removed (duplicate of object-movie-non-looping-sequence)
Tweaked example to work flawlessly when responsive
Compiled and documented
Image cache is being created earlier on setup rather than on preload
Rounding of scaled values
Data key `loading` stores whether preloading is in progress
Special private `loaded` var marks the moment Reel has been loaded for the preloader tick event binding
To reuse the preloader, it doesn't get removed anymore, and its width gets zeroed instead
Cache wipeout refactored
Instead of triggering individual events, a `resize` event is triggered