On Thu, May 5, 2016 at 1:43 PM, tim Rowledge <tim@rowledge.org> wrote:

On 05-05-2016, at 1:02 PM, Yoshiki Ohshima <Yoshiki.Ohshima@acm.org> wrote:

On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <tim@rowledge.org> wrote:

On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <Yoshiki.Ohshima@acm.org> wrote:

It actually is not clear yet which branches are the right one for

current Scratch on raspi and also future proof.  Perhaps doing for

multiple branches is necessary?  (What are the relationship of those?)

Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.

Okay!

By any chance, can you tell me how you test things? for Raspberry Pi?

For Japanese input? I don’t, because I can’t and wouldn’t have the faintest idea if it were correct anyway. I leave it to Kazuhiro Abee to let me know when he notices something wrong.

Ah, no.  I meant to ask how you test your things.  Is there a dev
image of some sort you are using (presumably .changes is there), and
compiling VM and transferring it to a Pi, etc.

(I have done my own little share of compiling and testing things on
Pi, which in the end involved compling C with some asm code on Pi on
an SSH terminal and run it.  But I am just curious how you've been
doing it.)