MicroBlocks select board

[Hans Braakmann]

My proposal is to place the vendor-related libraries ELECFREAKS, Kits, and Boards, and Robots at the forefront of Microblocks. Some of these boards require pre-installed libraries. To avoid hardware conflicts would it be possible, by providing the option to select these boards in the 'update firmware on board' feature.

[John Maloney]

Going forward, MicroBlocks will no longer have vendor-specific folders. Instead, it will organize all libraries into folders based on functionality.

In the most recent pilot release, we split the ELECFREAKS folder between Robots and Kits and Boards. That change will be pushed to a stable release this summer.

[John Maloney]

MicroBlocks has a mechanism for pre-loading libraries for specific boards when you create a new project. For example, when you make a new micro:bit project the "LED Display" and "Basic Sensor" libraries are loaded.

Some of these boards require pre-installed libraries

Which boards and libraries were you thinking of?

[Hans Braakmann]

I was thinking of the weeks of our troubleshooting the Raspberry Pi Pico I2C with the BME280, Color(TCS34725) and te preloaded OLED SSD1306 library.