Jargon

[meganindya]

We need to settle on a set of jargon, which we shall use throughout the development and maintenance cycles, for components, units, data structures, etc. We're often at a dilemma in the current Music Blocks.

• Entry point of the application: ________ (analogous to Activity in Music Blocks).
• Component that handles program execution: ________ (analogous to Logo in Music Blocks).
• Data Structure to store the program's instruction sequence: ________ (analogous to blockList and macros in Music Blocks).
• UI bars that contain the buttons: ________ (analogous to Toolbar in Music Blocks).
• The Sprite: ________ (analogous to Turtle in Music Blocks).
• (if required) Subcomponent of the Sprite that handles "music": ________ (analogous to Singer in Music Blocks).
• (if required) Subcomponent of the Sprite that handles "art": ________ (analogous to Painter in Music Blocks).

With respect to the Model-View-Architecture

• Engine is the Model.
• Client is the View.
• Broker is the Controller.

@walterbender @pikurasa

[walterbender]

+1

[pikurasa]

Sounds good to me.