[squeak-dev] How do I move a morph from one project to another?

Marcel Taeumel marcel.taeumel at hpi.de
Wed May 2 11:11:40 UTC 2018

Given that you just switched from the target project into the source project, execute this in the Morph's inspector:

Am 02.05.2018 11:49:09 schrieb H. Hirzel <hannes.hirzel at gmail.com>:
Bob, thank you for the good summary of the points of discussion.
I work in a similar way as St├ęphane describes.


On 5/2/18, St├ęphane Rollandin wrote:
>> This all started with a simple problem that had a simple answer. Then
>> many answers appeared without a clear notion of what the problem is. Who
>> has a real problem that happens several times a day that takes too long
>> to do? DTSTTCPW, anyone?
> I use projects mostly as virtual desktops where I keep different aspects
> of my work (be it development or music composition) more or less cleanly
> separated.
> When I realize that what I'm working on is not anymore in the meant
> scope of the current project, I create a new project and dispatch all
> workspaces, browsers and other tools (including homemade ones such as
> musical editors) that live in the current (usually crowded) World to the
> world of that project.
> So I only deal with top-level morphs, and as I said earlier I added an
> item in their red handle menu to easily send them away (usually several
> morphs in a row). I also have another item for sending a morph copy to
> another project, but I use this one much less often.
> Stef

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180502/b28d5cd9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 18856 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180502/b28d5cd9/attachment.png>

More information about the Squeak-dev mailing list