[squeak-dev] MorphicProject subclass: #EtoysProject
hannes.hirzel at gmail.com
Tue Oct 3 12:46:32 UTC 2017
your change set contains the class EtoysProject with
#(#finalEnterActions: #restoreGlobalPreferences #saveGlobalPreferences
For complete configuration of a EtoysProject it might be necessary to do
PasteUpMorph subclass: EtoysPasteUpMorph
as well. http://wiki.squeak.org/squeak/6461
Then Etoys related methods may be pushed down to EtoysPasteUpMorph.
And probably an Etoys specific subclass of WorldMenu would be fine as well
there is a test project  and some more information about adaptions
needed because of the UI changes in the thread 'Etoys in 2017?' - UI
preferences . And it would be good to have Etoys methods /
configuration separate .
I suggest that you start go ahead and start implementing this while
using a test Etoys project dropped onto the desktop.
 > You simply drop it in. E.g. download this project
 Hannes Hirzel, 'Etoys in 2017?' mail, Wed, Feb 22, 2017 at 11:01 AM
 David T. Lewis, Sep 4, 2016 at 3:34 PM
"I think it would be great if both Etoys and Scratch were easily
loadable and unloadable in trunk."
On 10/2/17, David T. Lewis <lewis at mail.msen.com> wrote:
> An EtoysProject is a project that is configured for running Etoys. On
> first entry to a new EtoysProject, the playground and project preferences
> are initialized to provide an environment similar to that of a traditional
> standalone Etoys image.
> Certain preferences that are required for Etoys are initialized on project
> entry, overriding their global preference values while this EtoysProject
> is active. On leaving the project, these preferences are restored to their
> previous values.
> "ProjectViewMorph openOn: EtoysProject new"
> Change set attached for a minimal implementation.
> Anyone with Etoys knowledge care to help? I do not know enough about Etoys
> to fill in the rest of the initialization that will be required, but it
> should not be hard to do.
More information about the Squeak-dev