Last updated at 7:18 am UTC on 9 June 2018
This is intended as a temporary (? as of 2017/2018) SqueakSource project for working out how to structure EtoysProject and get it to open a new project with the familiar playfield.
EtoysProject as a subproject of MorphicProject
Note about initial change set
Load the following or later version
Time: 5 November 2017, 6:17:07.061654 pm
Then Choose 'Projects' -> new project -> 'EtoysProject'
From within the EtoysProject there is no direct way yet to open a Etoys subproject unless you execute
EtoysProject openViewOn: nil
in a workspace.
Test case 'Loading a saved project from the Squeakland release'
and drop it onto the desktop.
Going back brings up a deprecation warning but after hitting 'Proceed' the parent project is brought in.
Note about project loading
... We might have some kind of rule in project loading that says "if the current project is an EtoysProject, and if I am loading a theFileName.pr for a MorphicProject, then make it an EtoysProject".
And perhaps when saving a project, we could reverse the rule and always save a project as MorphicProject, because we know that a loader in EtoysProject will know how to do the right thing with it.
Creation of new projects : how should it work?
Idea to simplify the creation of new projects
More information about creating a specific project type
Subclassing MorphicProject, TheWorldMenu and PasteUpMorph