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 <lecteur@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>