monolit/makecode repository overview

⁠Makecode for Mono

The purpose of this project is to get Mono⁠ to be an official target in Makecode⁠ by integrating the Mono Framework⁠ into the Programming eXperience Toolkit⁠. PXT offers the following:

• An editor for writing applications for Mono. The editor can swap back and forth between Blocky⁠ and JavaScript representation of the application code.
• A simulator for running the application code without a physcical device.
• A compiler that continuously, in the background, translates the application code to binary code that can run on the physcical device.

⁠Run PXT locally

$ cd src
$ npm install
$ npm start

⁠Deploy

The Docker container is built and started manually with

$ docker build .
$ docker run -d -p 7500:3000 [build_hash]

The Docker container is automatically built by DockerHub⁠ when you push to the Bitbucket repository.

To deploy on private.openmono.com, use

$ export DOCKER_HOST=tcp://private.openmono.com:2375

Then update the autobuilt container:

$ docker-compose pull
$ docker-compose up -d

To see the logs

$ docker-compose logs

⁠Plan

• Get PXT up and running locally, with the sample⁠ or microbits⁠ so that we know what it takes to get PXT up and running.
• Get PXT deployable into Monolit's infrastructure⁠ so that we (are able to) share and demonstrate the possibility to integration Mono into Makecode.
• Make a simplified PXT simulator of Mono so that it can be run in Makecode.
• Create the minimal set of Blocky building blocks that are needed to program the simple simulator.
• Connect the simplified simulator to the building blocks.
• Modify Mono Framework⁠ so that it can be compiled by Yotta⁠ into a library that can be used by PXT.
• Connect the building blocks to the Yotta library so that it is possible to generate Mono programs.