I look forward to implementing new drivers for hardware I wouldn’t have dreamed of working on (reading from old DOS floppy drives, perfect example), adapting old algorithms into CircuitPython (let’s do more image processing or maybe start doing audio processing), and finding small efficiency improvements and firmware size savings when they’re needed.

I want to both learn more about and improve asyncio. A personal project goal would be to have an interactive display that continues to update & respond to input even while doing wifi requests. I don’t think this works right now (I could be wrong), and I don’t know how much is needed in order to make it work.

I’ve noticed as you go from platform to platform, there seems to be very small changes in the way you connect to the internet. On the ESP32s, The Funhouse, and a couple others that I can’t think of, the connection to the wifi SSID is handled in the “code.py” file or in the front end code if I may refer to it that way. When It’s done like this, I was able to write code that would allow me to connect to different SSID’s depending on where I am at. I noticed on the Matrix Portal and the Magtag, the connection is made in the back end or in the library. When It’s like this I really can’t add the code to go choose the network connection I need. I guess I could, but I would have to modify the library everytime a new one was put out or updated. It’s not the end of the world, but It sure is handy when you want to just take a device from one place to another and it work.

#CircuitPython2022 is our annual reflection on the state of CircuitPython. We’d love to hear from you too! See the kick-off post for all of the details. Here are the previous posts:

•  CycleMatch’s (aka kmatch) thoughts on Twitter