socket events

To connect two clients together, and maintain game state.

If too much work just poll game states

npm package socket.io may be a good idea.

Server->Client: Your game is ready
Client->Server: Ready (x2)

Server->Clients: Round start (interval 60 seconds, type: preround)
Client->Server: Ready (x2)
Client->Server: Set card to turret (1-1, 1-2, 1-3, 2-1, 2-2, 2-3) etc
? Client->Server: Terminate round early ?
Server->Clients: Round ended
Client->Server: Ready (x2)

LOOP:
Server->Clients: Round start (interval 60 seconds, turn: blue)
Client->Server: Ready (x2)
Blue->Server: Set card to turret( 2-3)
Blue->Server: Attack turret (1-1)
Server->Clients: Attack start
Client->Server: Ready (x2)
Server->Red: Send blue card + result
Server->Blue: Result
Server->Clients: Round ended
Client->Server: Ready (x2)

Server->Clients: Your game had ended

build card styling and prettiness. Possibly creating an Angular directive to display the card.

Using card data display appropriate resources.

We will need to work out how to resolve static resources. I think we need to write a resource to map champions to images. https://developer.riotgames.com/docs/static-data
example data: https://github.com/RpprRoger/lolapichallenge/blob/generoatrs/scripts/parse/card.js#L50

http://donpark.github.io/scalable-css-playing-cards/

enough to flesh out a basic card

linked: #9

Ant's laptop is really bright on the screen and stuff so yeah

Parsing to be done in components passing a stream between each component.
Preferably the first component (retrieval of URF game ids) to take a date range parameter
Fixture each of the components for development/debugging

https://github.com/postcss/autoprefixer

dgnrAEIUVHAE8920T9

Bring two clients together with cards using simple auth to manage clients

Client->Server: find me game
Client2->Server: find me game

END WITH

Server->Client: Your game is ready
Client->Server: Ready (x2)

so it connects to #38