Integrate global sound controls into sim framework

[jbphet]

There are two sound controls that need to be added into the sim framework, one for turning sound on and off for the sim, and another for choosing between "basic" and "enhanced" sounds.

The issues where this was previously discussed are:

• How should we control sound on/off in sonified sims? tambo#11
• Add ability to set the sonification level tambo#12

The UI design is being finalized in:

• Decide on layout of sound control icon on the nav bar tambo#19

In the 7/9/2018 sonification framework design meeting we decided that this should be committed to a branch on joist until the Equality Explorer release branch is created in order to minimize the risk of destabilizing core framework code.

[jbphet]

I committed some code for this but forgot to reference the issue, please see 4dd92fc.

[pixelzoom]

@jbphet said:

... we decided that this should be committed to a branch on joist until the Equality Explorer release branch is created in order to minimize the risk of destabilizing core framework code.

RCs are published for Equality Explorer, so you may proceed with merging into master.

[jbphet]

@samreid - since the Equality Explorer RC is out, please review the code on the sound-control branch and let me know what if anything needs to be done before merging it to master. One exception: for now, please don't spend any time on NavigationBarSoundToggleButton, since we are looking at ways to reduce the amount of memory that it used.

[samreid]

In the preceding 3 commits (note these are for 3 repos), I added review comments for the proposed changes. @jbphet please take a look?

[jonathanolson]

I ran grunt update on every active-repo (perennial/bin/for-each.sh active-repos grunt update and committed the results (omitting interaction-dashboard).

@jbphet I believe the config files are now correct. Is there some place we should document how to update dependencies?

[jbphet]

Thanks for the fix.

Is there some place we should document how to update dependencies?

Sure. Maybe a new document in phet-info/doc? The challenge will be remembering that it exists and using it when needed and keeping it updated, since adding a new dependency is a pretty rare event. I would suggest creating it (it should be quite short, right?) then marking for dev meeting to see if people agree with the location and just to let the other devs know that it exists.

[jonathanolson]

Added phet-info/checklists/updating_metadata.md (fits as a checklist). Tagging for developer meeting to see if anything needs to change.

[jonathanolson]

https://github.com/phetsims/phet-info/blob/master/checklists/updating_metadata.md

[pixelzoom]

My task is to review https://github.com/phetsims/phet-info/blob/master/checklists/updating_metadata.md.