I might be missing something obvious here, but why is FFI forbidden in Etoys? Is it a matter of security?

Regarding the "generic hardware-interface plugin", I think it would be great to have something like that but don't you think the underlying platforms are very much incompatible with each other?



On Tue, Mar 2, 2010 at 4:32 AM, Bert Freudenberg <bert@freudenbergs.de> wrote:
On 02.03.2010, at 01:38, Ricardo Moran wrote:
On Mon, Mar 1, 2010 at 6:43 PM, Bert Freudenberg <bert@freudenbergs.de> wrote:
Awesome!


Thanks!
 
I assume this uses a plugin to get the data - where's the code?

No, actually. We tried to develop this stuff using mostly Smalltalk code. For Arduino and SqueakNxt we are only using the SerialPort class. The other projects use FFI to access the libraries that do the hard work. If you're interested I can give you the links to their websites.

Hmm, that's unfortunate. I was hoping to get this included in Etoys properly, but FFI is a no-go there. My idea was having a generic hardware-interface plugin that could input/output any number of signals (from joysticks and accelerometers over the XO's sensor port to special hardware like Scratch's PicoBoard or Phidgets etc.).

Well maybe we can at least find a common interface in Smalltalk for all the great interface-to-real-world projects ...

- Bert -

A lot more sensors could be added to something like this. In particular ones that are built into laptops nowadays, like accelerometers. Would you take contributions?

Yes, of course! We would be very glad to accept contributions. In fact, we want to increase the list of supported hardware with everything considered worthwhile, and the sensors built into laptops seem to be a great addition.

Cheers!
Richo