This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
var Parallax = function () { | |
/** | |
* @type {Parallax} | |
*/ | |
var that = this; | |
/** | |
* Holds all of the elements and their callback | |
* functions inside objects. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// this is (a start of) an example of a Susy+mq() setup that mimics bootstrap grid. | |
// I work on multiple bootstrap-based projects. | |
// I want to stop using grid classes in the markup, and start using mixins with susy and sass-mq. | |
// Since the project is heavily tied to the bootstrap grid, I want to have the exact same behavior | |
// between bootstrap classes (old code) and susy mixins (new code). | |
// all the grid classes generated below are here to ease up testing. | |
// required: susy + sass-mq |
This is an unofficial, uncomplete and (pretty sure) wrong documentation of the RESTful service which powers the League of Legends spectator mode.
This documentation is desgined to be community driven and should be extended by everyone. If you find things missing, add them please!
Riot's spectator mode works by requesting replay data via HTTP form a service. The data is split in chunks which usually contain about 30 seconds of gameplay. Additionally there are key frames which seem to contain more information then a single chunk. They seem to be used to support