UML Class Diagram

[meganindya]

Engine

using Music Blocks' jargon

Notes

• Except Turtle (and thereby Painter, Singer, and State), all the rest of the classes are singleton.

• The InstructionDataStructure (block tree) is present in the pool shared by the engine and the client, i.e. outside the engine, and so is Tone.js.

• The GATEWAY is the component responsible for any communication external to the engine.

• The State and StateTransitionUtils (utilities to work on a State object) form the feature API (all available programming features of Music Blocks, basically a library). This can be exposed to the client via a middleware in the broker.

• The HotspotCompiler pre-processes non-interactive instructions by traversing the InstructionDataStructure and generates a variable-based (some State properties including the first dispatch time are variables) schedule; the Interpreter actually executes the instructions and uses the compiled schedules generated by the HotspotCompiler, resulting in a faster and lightweight dynamic execution.

@walterbender opinions?