[etoys-dev] Etoys in Javascript

[Jecel Assumpcao Jr.]

Kathleen Harness wrote:
> > Let's keep "compatibility with current projects" at the top of our requirements
> > for the changes to Etoys being considered here.

I fully agree with that priority. Note that we were talking about a
completely new Etoys and not a changed one. I was just trying to make
clear what the cost of the different options are.

> > I know Bert mentioned this recently and I am very grateful that he values what
> > we have been doing here in Illinois.
> > 
> > If the library collection of projects on EtoysIllinois will not run in Etoys it would
> > be the end of us. We can not meet again with the hundreds of students who
> > made those projects. 
> > 
> > The example projects and lesson materials were developed in classrooms and
> > reflect years of experimentation with project ideas that make programming
> > relevant to young children's interests and knowledge. 

Yes, that is far more important than any specific Etoys feature in my
opinion as well. In the Squeak community, after Edgar De Cleene it is
likely that I have been the most vocal about keeping old stuff working.

Bert Freudenberg wrote:
> would converting the projects be okay? Meaning, suppose the "Javascript Etoys"
> couldn't read the old project files directly, but there was a way to export a project
> from Squeak Etoys into another file that could be imported by Javascript Etoys,
> would that be sufficient?

That sounds like an interesting plan. I had only though about putting
all of the conversion work in the new system, but it is true that some
things are easier to do inside the original system. It might be the case
that getting 100% of the projects converted is really hard but 97% is
reasonably easy. It would be a good idea to find out, specially if the
3% turn out not to be among the most important projects.

-- Jecel