Open Propeller Project #5: Explore the Possibilities of MIT's Scratch 2.0 Extensions
We would like to develop a graphical programming interface for the Propeller
Graphical programming is very popular with our educational customers and we are continually reminded that we need to develop some type of MIT Scratch
support for the Propeller. Why would you care about the funny cat carrying the Propeller Activity Board? First, you're a Propeller programmer
and you understand what could be accomplished with our multicore architecture. And we all have a responsibility to share our interests and capabilities with future programmers.
This is your chance to contribute to the Parallax community through an important educational project. If we can achieve this goal, we will have a Scratch-supported, American-made hardware choice for STEM education. And you know we've got all hardware we need in the shield-free Propeller Activity Board at $49, so let's make this happen!
Open Propeller Project #5 is initially about exploration, discussion, and hopefully examples. We don't know what's possible and we don't have a set of specifications for our goal [yet]. Just like the iPad to ActivityBot
effort lead to a bigger project of actually downloading code from iOS to Propeller over WiFi, this one could have a similar outcome. It could even become as big as Open Propeller Project #3
, which is bringing open source Spin support to several operating systems!
We'll learn together, share what we develop, and maybe formalize our goals to take Scratch support for the Propeller to the next level. Maybe we'd build this into Learn.parallax.com, use it as the S3 robot programming interface, and who knows what else?
A few starting points:
Let's start by doing a bit of research, experimenting and hopefully showing some of the possibilities with a real example. Maybe these questions will be answered along the way:
- Could the tool support multicore, having parallel program paths with shared memory?
- Programming blocks be used for sensors, like a Ping))), accelerometer, compass, etc.
- Invoke a command-line interface to the Spin or C compiler? Or is it really more appropriate to configure the Propeller from Scratch to do pre-defined functions?
- Suitability for an S3 Robot GUI?
- Ease of development?
It may be too early to get started if they haven't released the Scratch 2.0 Extensions and documentation yet, but they're coming "in April".
Who's in on the Scratch effort with us?
Your support is appreciated more than you can imagine.