Look out for issues on the development of the new Music Blocks

[meganindya]

Music Blocks is being built from the ground-up, to address several architectural problems with this run. Since Music Blocks is a fork of Turtle Blocks JS, musical functionality was added on top of it. However, music is fundamental to Music Blocks. Besides, the Turtle Blocks JS started initially with handful of features, and was written without a complex architecture. As Music Blocks got built on top of that, it got incrementally complex, but the architecture remained simple, thus resulting in a monolith. Also, the functionality is tightly coupled with the interface and native client API (Web API).

Keeping these problems in mind, we have considered a foundational rebuild that will address all these issues, whilst adding buffers for future additions. We'll also be using a more elegant tech-stack to develop and maintain this project given its scale. After the core is built, we'll be porting features from this application to it.

Development of Music Blocks 2 will on sugarlabs/musicblocks-2.

The new architecture will be based on the discussion Abstracted Architecture.

The development of the engine (or VM) of the new Music Blocks will on sugarlabs/musicblocks-lib.

Look out for issues on the said two repositories.

[shrutibhardwaj22]

I am interested in working on this issue. Could you kindly assign it to me?