Support Javascript as a Codebook language
No due date
0% complete
The first major part of the development process is to support the execution of Javascript code within the Codebook editor.
This will be utilized with a WebAssembly module that is maintained here. At the moment it is using the Otto library to execute the code, but this might change in the future when we want to support, for example, nodejs and node modules.
…
The first major part of the development process is to support the execution of Javascript code within the Codebook editor.
This will be utilized with a WebAssembly module that is maintained here. At the moment it is using the Otto library to execute the code, but this might change in the future when we want to support, for example, nodejs and node modules.
This milestone is completed when
- The user can execute javascript and gets a proper output. He will also see errors that might appear.
- The code execution is based on a "global" Otto VM for the whole codebook, meaning that one cell can access the scope of other cells. The execution order is top-to-bottom. Other than in, for example, jupyter notebooks Codebook will not support running cells in a different order.
- There is some specification on how cells might be executed, meaning that there is some kind of "interface" between the Angular app and the Go code. This includes proper error handling as well as already thinking about how other languages could be supported.