Closed zepumph closed 4 years ago
Initial commit is done, next steps:
@zepumph and I worked on adding initialization code to scenery and supporting self build tonight. We moved initialization code from Sim.js to Display.js, and then modified scenery's config files to require utteranceQueue (and added the necessary main.js file to utterance-queue). We were able to successfully build and run the built version of scenery with utteranceQueue in it.
However, we realized in some runtimes where more than one display is being created, this implementation breaks everything because utteranceQueue is initialized multiple times (and it is a singleton). For that reason, we didn't commit as-is (see patch below). We think the way forward is to not make utteranceQueue a singleton so that there is one utteranceQueue initialized per display, as opposed to a single global utteranceQueue. @jessegreenberg what do you think about this?
-
This was a side project that was discussed in the last few weeks with @emily-phet and @jessegreenberg as something that @twant may be able to tackle as a back burner project. The priority of it may shift as we think about https://github.com/phetsims/molarity/issues/155 and how a fix for alerts firing in full-screen mode in Chrome may be to have scenery control the
UtteranceQueue
.On hold until we decide exactly what to do over in that issue.