[squeak-dev] How do I move a morph from one project to another?
Tim Johnson
digit at sonic.net
Wed May 2 14:44:00 UTC 2018
Thanks for this, Bob!
I work in a similar way to what other people describe. I keep my work separated into different Morphic projects. When I find myself starting to digress, I start a new project, and move the related inspectors/browsers/workspaces into it. However, I simply do this by dragging-and-dropping morphs into the project's snapshot/thumbnail morph*. The thumbnail will say "GOT IT!" and contain a copy of the morph.
This approach has caveats:
(1) the snapshot/thumbnail morph will only accept drops if its project has been entered and exited, erm, recently (?).
(2) this technique creates a copy of morphs rather than moving them.
(3) this exposes what I believe to be a bug: the thumbnail bitmap/form will not always show the most recent visual representation of the project contained inside.
I too have wanted a halo menu item to send a morph to another project. I like the possibility of having a "drop zone" morph as a teleporter ... though the project snapshot/thumbnail morph can work in this way.
I am asking myself now what would happen if I dragged a project snapshot/thumbnail morph into a shared flap so I could move it between projects: tested, done. it works. So: one way to move morphs between projects is to move a project's thumbnail/snapshot morph between projects, and drag-and-drop morphs into it. Just be aware that it will probably only work if the project has been entered and exited "recently".
Best,
Tim
* a SystemWindow/PasteUpMorph with a model of MorphicProject
> On May 2, 2018, at 5:09 AM, Bob Arning <arning315 at comcast.net> wrote:
>
> In the course of this discussion, it seemed like drag&drop might be handy for some use cases. Attached is a (really simple) DropZoneMorph that can do whatever you like to things dropped into it.
>
> On 5/2/18 5:48 AM, H. Hirzel wrote:
>> Bob, thank you for the good summary of the points of discussion.
>> I work in a similar way as Stéphane describes.
>>
>> --Hannes
>>
>> On 5/2/18, Stéphane Rollandin <lecteur at zogotounga.net> <mailto:lecteur at zogotounga.net> 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
>>>
>>>
>
> <DropZone.02May0805.cs>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180502/17c0c099/attachment.html>
More information about the Squeak-dev
mailing list
|