bert at freudenbergs.de
Tue Sep 15 00:57:33 UTC 2009
is it okay if I add the ScratchPlugin to VMMaker? We are including it
in Etoys and it makes it simpler for John Maloney if was maintained in
the official VM. We got explicit permission for that (even though it's
MIT it doesn't hurt to ask), see forwarded message below.
John is working on the 1.4 version as he wrote below, but the previous
one would suit us fine for now, current source is here:
- Bert -
Begin forwarded message:
> From: John Maloney <jmaloney at media.mit.edu>
> Date: 10. September 2009 13:12:00 MESZ
> To: Bert Freudenberg <bert at freudenbergs.de>
> Cc: "Software Squeakland.org" <software at squeakland.org>
> Subject: [sq-software] Re: ScratchPlugin
> Hi, Bert.
> Re: we're about to include the ScratchPlugin with Etoys
>> Mostly for the incredibly useful openURL prim ;) but secondly for
>> access to the ScratchBoard etc., Korakurider already made an Etoys
>> interface for it (though this won't make it in this release). Now
>> the question is if we need to include the "Scratch Source Code
>> License" file with the Etoys release. My reading of it is that we
>> don't. Also we both agreed that having the plugin be part of the
>> Squeak VM proper would make things quite a bit easier, and you
>> certainly would not require the license to be bundled with the VM
>> in that case, right?
> Mitchel has given permission for you to bundle the ScratchPlugin
> code with the Squeak VM. (You can keep this email as proof!) You
> don't need to include the Scratch source license.
> It's also fine to include the include the ScratchPlugin accessor
> methods (and the entire class). Giving credit in a class comment is
> Two questions:
> (a) Are you interested in including the Scratch Unicode plugin as
> (b) Should I send you the latest C code for the Scratch Plugin?
> Actually, I'm working to bundle up the Scratch 1.4 source code
> release, so I'll be putting a zip file of the latest C code online
> in the next week or so. But I can send you a copy sooner if you need
> -- John
More information about the Vm-dev