Refresh workspace when setting it to visible

Pin to `latest` for 3.0 modules

Deploy all branches but master to subdirectories

In case the remote one gets deleted for some reason. I already had a fork of gh-pages, which is why I'm using rschamp rather than LLK. This is intended to be temporary.

Use `comments` flag to disable comments in scratch-blocks

Make escape key exit library modals

Currently using an unmerged PR in gh-pages. (Will update to an LLK fork if we decide to go this way.)

Move to Travis build stages to handle the multiple deploy methods by branch.

Stop "testing" in more Node versions than 6, as this is basically just testing our build tools (using a single Node version simplifies using build stages.)

Also add a `watch` command for testing static build output.

It wasn't ever necessary. Still allow configuring this path in the GUI in case of different paths to static files for scratch-blocks.

Add instructions for publishing to the README

Full exposition here: https://github.com/LLK/scratch-gui/wiki/Publishing-to-GitHub-Pages

Use trusty beta for Travis builds

This allows gh-pages to work. Something changed in the precise VMs that prevents the git clone gh-pages uses from working correctly.  See https://github.com/travis-ci/travis-ci/issues/4942

On my fork, this change allowed the gh-pages deploy to succeed.

Fix library SVGs

This reverts commit 321839ca.

Asset load: use asset's data format, not default

Override callback for monitor checked state 

Show workspace before triggering resize

Check if blocks exists before updating values

Hide overflow-y on gui container

Reverts #335.

Pinning to `^0.1.0.prerelease.0` is not equivalent to `latest`, since has the effect of not installing the latest version on `npm install`, you have to also do `npm update`. This hurts us ergonomically on `npm install`, and doesn't help us since we already are releasing breaking changes on `prerelease`.

Update css-loader to the latest version