We successfully run Scratch on our embedded Linux board OLinuXino and with the help of scratchpy we can have access to all resources of the board like GPIOs, SPI, UART, I2C etc.
Here is picture of OLinuXino running Scratch 1.4 and connected to MOD-IO board with 4 relays:
the relays are variables rel1 - rel4
now we are about to set template for the GPIOs, they will be split in half as inputs and half as outputs, then easily GPIOs can be conneced to breadboard and interface buttons, LEDs, PIR motion sensors etc.
What I'm asking myself is how to name the Inputs and Outputs to be more kids friendly
GPIO.INPUT.1 and GPIO.OUTPUT.10 seems to me too technical, what do you think is easily for the kids to remember as names for the IOs?
For me at least, "input" and "output" are fine, so "OLinuXino input 1" and "OLinuXino output 1" are good.
Last edited by technoboy10 (2013-03-26 15:28:18)
Very cool! Also, I noticed that in the article, you mentioned that Snap! does not have a very good sprite selection. While Snap! only has one default sprite, you can drag images from your computer to make new costumes. Snap! will also (hopefully) have a paint editor in its full release.
Also, thank you for the nice comments about my extensions.
Last edited by technoboy10 (2013-03-28 17:07:58)
Hi, I've done the same sort of thing with the RPi http://cymplecy.wordpress.com/2012/08/2 … spberrypi/ and working on V2 now http://cymplecy.wordpress.com/2013/03/1 … velopment/
I've run a few classes and the kids (Age10) seem very comfortable with the concept of Pin numbers and MotorA/B type variables.
Just introducing using "Power" alongside "Motor" for variable brightness LED type projects
The shorter the word that you can come up with that still makes sense is the way to go - also recommend no case sensitivy and if possible handle with or without spaces (mine doesn't yet - it won't handle spaces and you can bet that 20% will of a class will add them in )