* 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.
* Check result of window.confirm before deleting variables.
* Create CONTRIBUTING.md
* Localisation updates from https://translatewiki.net.
* Cherrypick fixes made directly to master back into develop (#619)
* Check result of window.confirm before deleting variables.
* Create CONTRIBUTING.md
* rebuild
* Localisation updates from https://translatewiki.net.
* Minor wording change.
* Localisation updates from https://translatewiki.net.
* Localisation updates from https://translatewiki.net.
* Simplify the handling of the active desc for a toolbox without categories.
* Remove tables from the HTML. Move the toolbar buttons to the end so that they don't impede switching between the toolbox and workspace.
* When cutting or copying a block, do not include blocks joined to it.
* Add shadow to flyout buttons.
* Move 'create new group' button to the bottom of each toolbox block, and remove other buttons if there is nothing in the workspace.
* Add keyboard shortcuts for cut, copy and paste operations.
* Remove clipboard buttons to simplify UI.
* Prevent setting a number value to NaN. Select the field value on entry to an input field. State the contents of the input field when describing the field.
* Add aria-level and aria-selected attrs to dropdowns.
* routine recompile
* Update demo to latest interpreter.
* Move 'move to marked spot' button to the top of the block options list.
* Fix incorrect aria-levels in toolbox tree component.
* Add new fields to toolbarButtonConfig.
* Recompile
* Remove CONTRIBUTING
When installing from github, npm doesn't run prepublish on install, like it does when you're using npm link.
npm also doesn't install the devDependencies of its dependencies, so since these are needed for installation, move them to dependencies.
