How do I move a morph from one project to another?

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 <[hidden email]> 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 [hidden email] 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>

and EToySenderMorph can send a morph to another computer

NetMorph on Squeak map was a package to send morph to anywhere :-)

Best,

Karl

On Wed, May 2, 2018 at 10:25 AM, Bob Arning <[hidden email]> wrote:

Sounds to me like the discussion has moved into the it-could-mean-just-about-anything stage. So far we have:

- sending morphs from one project to another
- perhaps selecting the destination based on some morph property
- perhaps the receiving project could refuse to accept the morph
- make the morph frontmost in the receiving project's world, unless that project doesn't even have a world

And other questions occur:

- why limit this to morphs? Why not send arbitrary data from project to project?
- is a morph a ui representation of some separate domain object? Where does the domain object live?
- what if the sending project is in "grid-view mode" and the receiving project is in "list-view mode"? Does sending a specific morph make any sense?
- why assume the morph would be installed in the world at the other end?
- do we assume the morph must be deleted from the sending world? Dropping a morph on a PVM will send a *copy* to the other project.

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?

On 5/2/18 1:36 AM, H. Hirzel wrote:

On 5/2/18, Bob Arning [hidden email] wrote:

a Flap would do that

Yes it does, but the new method discussed here will allow to send the
morph to another project without leaving the current project.

In addition, depending on how it is implemented,  a script might send
several morphs to different projects depending on their properties
(e.g. moving task cards around for a project mgmt system).

On 5/1/18 8:04 PM, Francisco Garau wrote:

I use to like the squeak trash bin morph were you could recover previously
deleted morphs.

How about a similar sort of morph that acts as a teleporter? You drop the
morphs in one project and recover it from any other.

NetMorph on Squeak map was a package to send morph to anywhere :-)

Best,
Karl

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

<image.png>

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 [hidden email] 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>

 EToyProjectHistoryMorph shows all the projects 

As karl mentioned, there is such a thing, but perhaps specialization is useful. Attached is an update to DropZoneMorph which can create drop zones (with thumbnail) for all morphic projects, with the extra feature that dropped morphs are centered in the destination world to make them easy to find.

Also, it's not just top-level morphs -- here is a class list from a browser dropped into a different project:

On May 2, 2018, at 5:09 AM, Bob Arning <[hidden email]> 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.

Yes, I like drag & drop too.  But I would like to be able to drag&drop onto the project morph itself. That way we could provide a "projects" morph that showed all the projects in the system, and allow selecting the morph thumbnails one sees in each project morph, and then be able to directly manipulate and drag any top-level morph from any project to any other.  Given a multiple selection convention we could batch, although in my own use I typically only need to move one of two morphs.

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 [hidden email] 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>

DropZone.03May1015.cs (3K) Download Attachment