My suggestion was based on the recent observation that Snap install on
Linux isn't just an rpm, and a conversation with someone at CoderDojo
earlier that day about the desirability of Scratch controlled robots for
Code Club etc.
I certainly have NOT put a great deal of thought into this, so I'm very
happy if anyone can tell me more.
> But for some completely weird reason they've moved to Flash, when
> everyone else seems to be trying to abandon it! According to the
> Wikpedia entry for Snap!, Scratch doesn't run on Linux - maybe it
> could on x86, but AFAIK there's no ARM support so no use on the Pi, etc.
Yes, Scratch v2 is weird. Version 2 of anything should be heading
towards more flexibility, not less. I'd guess that some senior committee
decided on using Flash (well, can't you just... ?) , rather in the same
way that the BBC decided that using Adobe AIR was a good idea.
> OTOH, Snap! is implemented in JavaScript, hence me wondering how /
> what the Scratch dependences are?
Dunno, but the instructions for the Snap! install require Scratch. Just
addressing that would be good.
> In terms of controlling robotics, I
> know the TinkerForge guys recently released JavaScript bindings that
> run from the browser using web sockets. That in itself might be a
> cool thing to get working in Snap!, but also I wonder how easy it
> would be to write a little daemon that communicated with an Arduino in
> the same / similar way?
> Or quick Googling found this -
https://github.com/MrYsLab/s2a_fm
> Looks like it uses Firmata on the Arduino, which is something I used
> years ago and probably the right thing for this job.
Yes, I saw the reference on the Snap! page - it looks like a good idea
to me.
Thanks,
Peter