MorphicProject subclass: #EtoysProject

Am 03.10.2017 14:57:55 schrieb H. Hirzel <[hidden email]>:

On 10/3/17, H. Hirzel wrote:
> Dave
>
> your change set contains the class EtoysProject with
>
> EtoysProject selectors
>
> #(#finalEnterActions: #restoreGlobalPreferences #saveGlobalPreferences
> #initializeProjectPreferences #configureOnFirstEntry
> #finalExitActions:)
>
> 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.

See screen shot attached.

> And probably an Etoys specific subclass of WorldMenu would be fine as well
> http://wiki.squeak.org/squeak/6461
>
>
> there is a test project [2] and some more information about adaptions
> needed because of the UI changes in the thread 'Etoys in 2017?' - UI
> preferences [3]. And it would be good to have Etoys methods /
> configuration separate [4].
>
> I suggest that you start go ahead and start implementing this while
> using a test Etoys project dropped onto the desktop.
>
> --Hannes
>
>
> [2] > You simply drop it in. E.g. download this project
>> http://etoys.laptop.org/src/Content/ExampleEtoys/CarAndPen.014.pr
>
> [3] Hannes Hirzel, 'Etoys in 2017?' mail, Wed, Feb 22, 2017 at 11:01 AM
>
> [4] 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 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.
>>
>> Dave
>>
>>
>

Am 03.10.2017 15:34:25 schrieb H. Hirzel <[hidden email]>:

What Marcel refers to

Morph
BorderedMorph
PasteUpMorph "maintains the current tasks of Background
images, gridding,
drag-and-drop helpers"
EtoysMorph "keeps Etoys specific messages"


And then

Morph
BorderedMorph
WorldMorph (PasteUpMorph renamed, methods such as gridding maintained)
PasteUpMorph "empty PasteUpMorph class for compatibility"
EtoysPasteUpMorph "keeps Etoys specific messages"


Another issue not discussed here is that PasteUpMorph includes
WorldMorph functions.

Pharo has separated this. This is an issue which comes up from time to
time. [5] The advantage of keeping them together is that you may have
worlds in worlds. But this discussion is not related to the issue
Etoys refactoring issue.

--Hannes

[5] http://forum.world.st/WorldMorph-subclass-PasteUpMorph-tp4946461p4946465.html

On 10/3/17, H. Hirzel wrote:
> On 10/3/17, Tobias Pape wrote:
>>
>>> On 03.10.2017, at 15:03, Marcel Taeumel wrote:
>>>
>>> +1 :)
>>>
>>> And then later: Rename PasteUpMorph to WorldMorph, and keep an empty
>>> PasteUpMorph subclass around for compatibility reasons. So many ideas
>>> have
>>> been ported down to Morph class over the past years. New applications
>>> have
>>> no reason to ever use other instances of PasteUpMorph.
>>
>> -1
>> Except for Background images, gridding, drag-and-drop helpers, etc.
>> It should rather be a PlayField (as it comment already states).
>
> PlayField? I do not find a class named 'PlayField' in a current Trunk
> image.
> Which class do you mean?
>
>>
>> Also, be wary of the "rename then subclass" deprecation, because if
>> certain
>> projects extend the deprecated subclass (And a lot do for PasteUpMorph),
>> those extensions will never be used in typical circumstances.
>>
>> (This also bit me with the ContextPart depercation… Certain tools that
>> hook
>> into debugging stuff via ContextPart extensions no longer work as no
>> ContextParts will ever be around. Oh well..)
>>
>> Best regards
>> -Tobias
>>
>>>
>>> Best,
>>> Marcel
>>>> Am 03.10.2017 14:57:55 schrieb H. Hirzel :
>>>>
>>>> On 10/3/17, H. Hirzel wrote:
>>>> > Dave
>>>> >
>>>> > your change set contains the class EtoysProject with
>>>> >
>>>> > EtoysProject selectors
>>>> >
>>>> > #(#finalEnterActions: #restoreGlobalPreferences
>>>> > #saveGlobalPreferences
>>>> > #initializeProjectPreferences #configureOnFirstEntry
>>>> > #finalExitActions:)
>>>> >
>>>> > 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.
>>>>
>>>> See screen shot attached.
>>>>
>>>> > And probably an Etoys specific subclass of WorldMenu would be fine as
>>>> > well
>>>> > http://wiki.squeak.org/squeak/6461
>>>> >
>>>> >
>>>> > there is a test project [2] and some more information about adaptions
>>>> > needed because of the UI changes in the thread 'Etoys in 2017?' - UI
>>>> > preferences [3]. And it would be good to have Etoys methods /
>>>> > configuration separate [4].
>>>> >
>>>> > I suggest that you start go ahead and start implementing this while
>>>> > using a test Etoys project dropped onto the desktop.
>>>> >
>>>> > --Hannes
>>>> >
>>>> >
>>>> > [2] > You simply drop it in. E.g. download this project
>>>> >> http://etoys.laptop.org/src/Content/ExampleEtoys/CarAndPen.014.pr
>>>> >
>>>> > [3] Hannes Hirzel, 'Etoys in 2017?' mail, Wed, Feb 22, 2017 at 11:01
>>>> > AM
>>>> >
>>>> >
>>>> > [4] 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 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.
>>>> >>
>>>> >> Dave
>>>> >>
>>>> >>
>>>> >
>>>>
>>>
>>
>>
>>
>

Am 04.10.2017 03:29:07 schrieb David T. Lewis <[hidden email]>:

I put my initial change set on SqueakSource at http://www.squeaksource.com/EtoysProject.

This is intended as a temporary SqueakSource project for working out how
to structure EtoysProject and get it to open a new project with the familiar
playfield.

Hannes, Tobias, Bert and I have write access, and I would like to add Marcel
if he has a squeaksource.com account (I could not find it). Please commit
anything that you thimk makes sense.

As you may have guessed by now, I do not actually know enough about Etoys
to make it work. I just put that change set out to see if I could Tom Sawyer
a few of the more knowledgable folks to doing the hard parts. I think it
might be working :-)

I think that the Etoys package in trunk is probably too large for us to be
doing a lot of experimental changes right now, so my hope is that by putting
the Project related part into its own package temporarily, and putting that
up on squeaksource.com, that we can get this part working well enough
to merge back into Etoys in trunk when it is ready.

From my point of view, "working well enough" means:

- Open a new EtoysProject in Trunk, and the result is an Etoys playfield
that is reasonably similar to a stand-alone Etoys image. The new project
should open with the little car driving around, and with tabs and menus
as expected for Etoys.

- Returning from that Etoys project brings you back to a project that
still works. Whatever preferences were established or overridden to make
Etoys work should be restored so that the other projects are not affected.

Dave


On Tue, Oct 03, 2017 at 10:45:12PM +0200, H. Hirzel wrote:
> Thank you for the clarification, Tobias.
>
> As noted earlier in the thread the suggestion at the moment is just to subclass
>
> PasteUpMorph subclass: EtoysPasteUpMorph
>
> and push all the *Etoys related methods down to EtoysPasteUpMorph.
>
> Link to from EtoysProject to EtoysPasteUpMorph can easily be done in
> the initialize method of EtoysProject
>
>
> MorphicProject
> initialize
> "Initialize a new Morphic Project"
> super initialize.
> world := PasteUpMorph newWorldForProject: self.
> self setWorldBackground: true.
> Locale switchToID: CurrentProject localeID.
> Preferences useVectorVocabulary ifTrue: [world installVectorVocabulary]
>
>
>
> EtoysProject
> initialize
> "Initialize a new Morphic Project"
> super initialize.
> world := EtoysPasteUpMorph newWorldForProject: self.
> self setWorldBackground: true.
> Locale switchToID: CurrentProject localeID.
> Preferences useVectorVocabulary ifTrue: [world installVectorVocabulary]
>
>
> or maybe better not override the initialize method but asking the
> class in MorphicProject
>
>
> MorphicProject
> initialize
> "Initialize a new Morphic Project"
> super initialize.
> world := self class defaultPasteUpMorphClass newWorldForProject: self.
> self setWorldBackground: true.
> Locale switchToID: CurrentProject localeID.
> Preferences useVectorVocabulary ifTrue: [world installVectorVocabulary]
>
>
> It depends on other issue which have to be done in
>
> EtoysProject initialize
>
>
>
>
> On 10/3/17, Tobias Pape wrote:
> >
> >> On 03.10.2017, at 15:17, H. Hirzel wrote:
> >>
> >> On 10/3/17, Tobias Pape wrote:
> >>>
> >>>> On 03.10.2017, at 15:03, Marcel Taeumel wrote:
> >>>>
> >>>> +1 :)
> >>>>
> >>>> And then later: Rename PasteUpMorph to WorldMorph, and keep an empty
> >>>> PasteUpMorph subclass around for compatibility reasons. So many ideas
> >>>> have
> >>>> been ported down to Morph class over the past years. New applications
> >>>> have
> >>>> no reason to ever use other instances of PasteUpMorph.
> >>>
> >>> -1
> >>> Except for Background images, gridding, drag-and-drop helpers, etc.
> >>> It should rather be a PlayField (as it comment already states).
> >>
> >
> >
> >> PlayField? I do not find a class named 'PlayField' in a current Trunk
> >> image.
> >> Which class do you mean?
> >
> > Comment of PasteUpMorph:
> >
> > "A morph whose submorphs comprise a paste-up of rectangular subparts which
> > "show through". Anything called a 'Playfield' is a PasteUpMorph."
> >
> > etc.
> >
> > Best regards
> > -Tobias
> >>
> >>>
> >>> Also, be wary of the "rename then subclass" deprecation, because if
> >>> certain
> >>> projects extend the deprecated subclass (And a lot do for PasteUpMorph),
> >>> those extensions will never be used in typical circumstances.
> >>>
> >>> (This also bit me with the ContextPart depercation??? Certain tools that
> >>> hook
> >>> into debugging stuff via ContextPart extensions no longer work as no
> >>> ContextParts will ever be around. Oh well..)
> >>>
> >>> Best regards
> >>> -Tobias
> >>>
> >>>>
> >>>> Best,
> >>>> Marcel
> >>>>> Am 03.10.2017 14:57:55 schrieb H. Hirzel :
> >>>>>
> >>>>> On 10/3/17, H. Hirzel wrote:
> >>>>>> Dave
> >>>>>>
> >>>>>> your change set contains the class EtoysProject with
> >>>>>>
> >>>>>> EtoysProject selectors
> >>>>>>
> >>>>>> #(#finalEnterActions: #restoreGlobalPreferences #saveGlobalPreferences
> >>>>>> #initializeProjectPreferences #configureOnFirstEntry
> >>>>>> #finalExitActions:)
> >>>>>>
> >>>>>> 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.
> >>>>>
> >>>>> See screen shot attached.
> >>>>>
> >>>>>> And probably an Etoys specific subclass of WorldMenu would be fine as
> >>>>>> well
> >>>>>> http://wiki.squeak.org/squeak/6461
> >>>>>>
> >>>>>>
> >>>>>> there is a test project [2] and some more information about adaptions
> >>>>>> needed because of the UI changes in the thread 'Etoys in 2017?' - UI
> >>>>>> preferences [3]. And it would be good to have Etoys methods /
> >>>>>> configuration separate [4].
> >>>>>>
> >>>>>> I suggest that you start go ahead and start implementing this while
> >>>>>> using a test Etoys project dropped onto the desktop.
> >>>>>>
> >>>>>> --Hannes
> >>>>>>
> >>>>>>
> >>>>>> [2] > You simply drop it in. E.g. download this project
> >>>>>>> http://etoys.laptop.org/src/Content/ExampleEtoys/CarAndPen.014.pr
> >>>>>>
> >>>>>> [3] Hannes Hirzel, 'Etoys in 2017?' mail, Wed, Feb 22, 2017 at 11:01
> >>>>>> AM
> >>>>>>
> >>>>>>
> >>>>>> [4] 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 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.
> >>>>>>>
> >>>>>>> Dave
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >
> >
> >
>