[Google Blockly][Outbreak] Set up Outbreak level to work with Google Blockly

[ajpal]

Most of the changes here are just adding stubs so that Outbreak, which is a Sprite Lab level, can load without error.

• FunctionEditor - this is the modal function editor which is custom to our fork. Outbreak levels won't actually use this feature.
• Block.createProcedureDefinitionBlock - Outbreak won't use procedure blocks
• Variables getters and setters - we have custom logic to separate variables of different types. Outbreak levels won't use variables.
• dispatchEvent - used in Sprite Lab when you switch from the costume tab to the code tab. Outbreak levels won't use the costume tab.
• New constants: DEFINITION_BLOCK_TYPES and BlockValueType
• prefixLines - Our code expects this function to be defined on Blockly.Generator but in Google Blockly it's on Blockly.JavaScript, so just aliasing it solves the problem.

There's a couple small pure refactor changes in here as well:

• Pulling out some constants from googleBlocklyWrapper to cdoConstants
• Renaming initializeBlocklyXml to initializeTouch in CdoTouch

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[epeach]

Not sure what works for your workflow, but do you have a task or reminder for at the 'end' of getting Outbreak onto Blockly to go back and make sure that all the 'ToDos' are addressed?

[ajpal]

Not all of these TODOs need to be addressed before HOC. In fact, I think most of them will not be addressed as part of Outbreak work. The stubs will need to be filled in when we migrate all of Sprite Lab, but leaving them as no-op stubs for now is fine because Outbreak doesn't actually use the features

[epeach]

I would argue that we should add additional details to the ToDos then - to indicate the lifespan on the ToDo and differentiate between ToDos that require action and expected for-the-time-being No-Op functions .

[epeach]

Is there a technical doc that outlines our approach/philosophy/process to moving things onto Blockly? It might be useful to have just one or two pages that outlines the process and major steps.

[epeach]

This looks good to me.

[ajpal]

Is there a technical doc that outlines our approach/philosophy/process to moving things onto Blockly?

These are probably a good place to start:
https://docs.google.com/document/d/1UG-TSEfdMglzOmZbvWeyNXtUm3YfEborpRIWHgHlBjA/edit
https://docs.google.com/document/d/1kVVnTRfmQQur62uVca4MKIu8SHHA6bWHSIFvfyzOcfE/edit#

[epeach]

Immediately after leaving that comment, I read the Blockly Status doc and was like, "Oh, well, there it is!". 😆