<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Georgia">As karl mentioned, there is such a thing,
but perhaps specialization is useful. Attached is an update to
DropZoneMorph which can create drop zones (</font><font
face="Georgia"><font face="Georgia">with thumbnail)</font> for
all morphic projects, with the extra feature that dropped morphs
are centered in the destination world to make them easy to find.</font></p>
<p><font face="Georgia">Also, it's not just top-level morphs -- here
is a class list from a browser dropped into a different project:<br>
</font></p>
<p><font face="Georgia"></font><br>
</p>
<img src="cid:part1.22D7E352.12F200C8@comcast.net" alt="">
<div class="moz-cite-prefix">On 5/3/18 9:50 AM, Eliot Miranda wrote:<br>
</div>
<blockquote type="cite"
cite="mid:A8C076A3-1482-4F74-9BAB-7F79170739FC@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div><br>
</div>
<div>On May 2, 2018, at 5:09 AM, Bob Arning <<a
href="mailto:arning315@comcast.net" moz-do-not-send="true">arning315@comcast.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p><font face="Georgia">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.</font><br>
</p>
</div>
</blockquote>
<div><br>
</div>
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.<br>
<blockquote type="cite">
<div>
<p> </p>
<br>
<div class="moz-cite-prefix">On 5/2/18 5:48 AM, H. Hirzel
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGQxfVgi28FeaKbj4TapWo69RK-rL8RRo7=vnTE_206+k05_EQ@mail.gmail.com">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:lecteur@zogotounga.net" moz-do-not-send="true"><lecteur@zogotounga.net></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">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
</pre>
</blockquote>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><DropZone.02May0805.cs></div>
</blockquote>
<blockquote type="cite">
<div><span></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>