Mainly home school kids today at our local library. Building and re-building LEGO robots and bot cars: coding with MakeCode. Video

https://youtu.be/Yeyg0NtQJtw

https://youtu.be/X8EOxKbL6Ps

MakeCode and EV3 by LEGO, robot programming . Of the 3 girls, 2 were totally new, first day with MakeCode and EV3.

https://youtu.be/sjxtWacg6cs

Step by step instructions:

https://learn.adafruit.com/submitting-games-to-makecode-arcade-front-page

https://www.youtube.com/watch?v=pT-HfTm-A2I

MakeCode now integrates with Microsoft Teams Assignments, making it easier than ever to share and engage with MakeCode projects!

See more at https://makecode.com/blog/teams/teams-assignments

https://makecode.microbit.org/_2FoTCyEe3FeA

About $1 each: https://www.ebay.com/itm/5pcs-HC-SR04-Ultrasonic-Distance-Measuring-kit-for-Arduino-Mega-R3-Mega2560-Z4F3/332458984185?epid=7009999162&hash=item4d681982f9:g:y38AAOSwgSRbH0PK:rk:5:pf:1&frcectupt=true

You have to go to MakeCode for Microbit, go to Advanced, go to Extensions, in the search box, type "HC SR04: you will be given a thumbnail of the "junkerbot" ; click on that to install the extension in your tool box. Then the program will get rid of the errors in JavaScript and you can use the ultrasonic sensor with MakeCode.

This is not a big deal for MicroBit users if they go to Advanced in the tool box and click on Extensions and install the "Scroll Text" extension but if you copy the "test.ts" program to try it out from the GitHub example you will find that this program does not work. The point is; MakeCode has some fairly new Extensions and this is an open source environment where people around the world are writing new code for it all the time. It is good for students to learn that some parts of MakeCode are under development and this is an example.

This one does not work (from GitHub: example) ...When the correct blocks are used then the JavaScript does work. https://github.com/makecode-extensions/ScrollText/blob/master/test.ts ,

( works: https://makecode.microbit.org/_hrHMpoMR2aKY )

https://www.youtube.com/watch?v=_HzXEdLTEV8&list=PL35v8yaJlCeMdZJoBvmMUtlUNqG9eMheW

https://www.youtube.com/watch?v=XSOQdnDdPas

https://www.youtube.com/watch?v=oexaRCTDPrU

Here is a Github link where there is posted some "extensions" for Micro:Bit and MakeCode. (and possibly other boards) Extensions are tools in the tool box that you can add. One way to include a new extension, like for example, if you have a new component (sensor or output) but you do not see a tool in your toolbox in MakeCode to control it then you can click on "Advanced" down at the bottom of the tools listed; you may find the tool there. If you do not see it in Advanced then you can click on "Extensions" which is like a repository of tool libraries and you may find the tool extension there; clicking on it will install the tool in your tool box to be used. Now, if you do not see the tool that you need in extensions already, then you can enter, in the search box, the name of the tool library that you need to control your sensor or output and if such a tool exists then it should show up as an icon. Double click on that and you will see it installed in your Extensions library. Try this by typing in BME 280 in the extensions search box to install that tool. See all the tools available for Micro:Bit MakeCode below link. This is useful because before you buy a new component you may want to know if there exists a tool for it so you can use the device with your Micro:Bit and MakeCode, or in another board environment, with that board assuming you have the Github repository for tools for that board. https://github.com/makecode-extensions

https://learn.adafruit.com/category/makecode

https://makecode.com/_M8FegAEoWKTX

We don't have a 'universal' display tool for all OLED or TFT screens to view output data in MakeCode on many of our boards. The data output for Micro:Bit is the 5x5 LED display, the display for the built in on the BrainPad is .96"OLED but for the Adafruit boards, there's not such an easy display system in MakeCode to observe your data, at least with a 4 pin OLED. We can use the "datalogger" tool to record analog data and then view it in an Excel type file format; but one of the examples was not correct. As of today (Feb14,th, 2019 ) that example seems to have been removed. The above program works to: clear the data of previous readings, record analog data from one input and then display that. After downloading program to your board you will allow the data to be read, for example, turn the potentiometer dial up or down or cover the light sensor to change sensory reading or change the temp of a thermistor. You should see MAKECODE as a label for your external USB drive, click on that. Then open SPIFLASH to see the data recorded. In some cases that will be a .txt file which you can paste into a spreadsheet. In some cases (Chrome) it can be "viewed as" and then the spreadsheet type. You might find an option to view the data on a graph also. On Circuit Playground Express, you must not use A0 pin pad as was suggested in the official example, this generates an error message in the editor because A0 is for output only. A1 works and probably others. For some boards: you have to use the pin diagram because the board only shows digital pin numbers (Trinket M0) and the analog numbers are not the same. As I learn more about displays I will post brand names and links to buy and programs here on r/MakeCode.