- esptool.py (for flashing firmware)
- nodemcu-tool (for file management/code upload)
- mpremote file management and console
some new games I am interested in:
An ongoing list of resources for developing Apple Homekit stuff
I am developing or maintaining these CircuitPython libraries:
All of these are based on the [Adafruit CircuitPython Library Cookiecutter](https://learn.adafruit.com/creating-and-sharing-a-circuitpython-library/creatin
Over the past few years, the old "write once, run anywhere" mantra has gotten a refresh. The broad adoption of mobile devices has increased the need for solutions that allow developers to write core application code and UI in a single framework, and package that code for deployment. The following are some of the more popular cross-platform, modile-friendly frameworks for various languages.
Some of these solutions are hybrid frameworks, which provided containers for non-native app code and integrations with native features. Others compile to native code.
For a good rundown on the architecture and considerations in using hybrid platforms, take a look at Comparing Cross-Platform Frameworks.
Python is a great language for development. Microcontrollers are wonderful for physical computing. What's better than either one alone? Both together!
The good news is there's growing support for using Python on microcontrollers, both as programming language off-board and directly interpreted on embedded hardware.
Based on MicroPython, CircuitPython was created by Adafruit for its boards, and is intended to provide a easy to use, consistent interface across multiple microcontrollers. It also has an extensive library/driver bundle.
| class Base { | |
| constructor(x, y) { | |
| this.x = x | |
| this.y = y | |
| } | |
| get point() { | |
| return {x: this.x, y: this.y} | |
| } | |
| } |
I created a simple Node.js server that emits events, then uses a socket to publish them, as well as very basic client for listenting on that socket to consume the events.
This demo server was created as part of a POC for a broadcast system that required timestamp-based synchronization of events across multiple streams.