For my next clock project, I'm thinking of resurrecting my old #ScratchGPIO #TopsyTurvy clock that was inspired by @Workshopshed one https://www.workshopshed.com/2014/09/a-working-topsy-turvy-clock/

But this time programming it using @microblocks
#3DPrinting

A working Topsy Turvy Clock - Workshopshed

Late last year I was watching a kids TV show and spotted a rather unusual clock, it was a simple mantel clock but the numbers were in topsy turvy

Workshopshed
I have finally started on converting #ScratchGPIO to #Python3 :) Using good old #PiBrella for testing
I'm going to try and make a slight bug fix to my >10 year old #Python2 #ScratchGPIO project - wish me luck!
I might have to end up converting #ScratchGPIO to #Python3 as a teacher has bought 15 #4Tronix #PiToGo2 Mk2 robots and wants to program them using Scratch. Current workaround is is get them to install #Stretch instead :)
@permagriculture The issue with #ScratchGPIO is that it uses #Python2 :( - every time I look at converting it - the enormity of the task stops me from doing it :)

@cymplecy
Sorry that page is a bit confusing at the moment.
There are currently two distinct use cases

1) Using a ESP on it's own
2) Optionally connecting a SBC (Pi/Jetson/AI-64)

So for 1) I'll look into microblocks more. Thanks for the tip

For 2) I'd be interested in hearing more about #scratchGPIO https://github.com/cymplecy/scratch_gpio would it need a significant update to LGPIO? https://ubuntu.com/tutorials/gpio-on-raspberry-pi#1-overview

GitHub - cymplecy/scratch_gpio: Code for scratch_gpio_handler

Code for scratch_gpio_handler. Contribute to cymplecy/scratch_gpio development by creating an account on GitHub.

GitHub
@rosmo em - I'm a bit confused by all the info. If it's being driven by an ESP32, then #Microblocks would be my 1st choice. If a #RaspberryPi, then maybe it would make me update #ScratchGPIO :) Or use @SnapCloud to talk to whatever is on the robot using #MQTT or HTPP