* boilerplate for category attribute
* style tweaks for Travis
* I read up on valid-jsdoc
* add to horizontal as well
* categories for vertical/event
* categories for vertical/data
* categories for vertical/control
* categories for vertical/looks
* categories for vertical/more
* categories for vertical/motion
* categories for vertical/operators
* categories for vertical/pen
* categories for vertical/senising
* rename Blockly.Categories.sounds to Blockly.Categories.sound
* add categories for vertical/sound
* categories for horizontal/control
* categories for horizontal/event
* categories for horizontal/wedo -- based off of color instead of adding wedo category
* add shapes list
* distinguish shadow blocks from reporters
* remove comparison to current attribute value around setAttribute -- this was to avoid CSS flickering but I believe the browser does this automatically
* naming/style tweaks
* add horizontal support
* add arguments to horizontal
* only reclassify if redrawing
* style tweaks
Move build dependencies back to devDependencies.
The build is now a prepublish step, not a postinstall step since the build will be supplied with the package when installed.
Use travis-after-all to deploy to npm only after all tests pass in all Node environments.
Only release non-PR builds for master and develop branches. For convenience, these branches are defined in the Settings panel for the repo in Travis. This way builds can be rerun without a new push with different values for these vars (e.g. if the token needs to change or a release should happen outside of the normal release branches)
Since this happens in `after_script`, we can't use Travis's built-in npm deployment. So create an .npmrc for authentication for `npm publish`.
Publish versions with the package.json version + "-<git sha>", e.g. 0.1.0-93d2f. This allows us to deploy every push to GitHub without considering version bumps. This is intended to be a temporary solution until we have more systematic releases.
