I have a project I'm working on that I intermittently publish to BSS (see the Activity project if you're curious, but it's sparsely documented). It's a priority planning tool, and I now have a fair amount of data in it. I want to publish it without the data to keep a little privacy, and also to save space. How can I do that?
I figure if I temporarily move things to another project I can avoid publishing them. I have a number of morphs I'd like to move. Is there a reasonable way to move them? I looked quickly in the Project and Morph protocols, and didn't see anything obvious. Perhaps I somehow get the Project's world and put the morph in there?
There is data separate from the Morphs. I've put my data in the Smalltalk dictionary, and one of my classes accesses it. Is that enough to keep it out of being published? I assume if I just left it as a class variable it would get published (since the class itself is published).
Ross,
One easy way to move morphs from project to project is via flaps:
* Create a new flap. (world... flaps... make a new flap). After the flap is created, a menu for it is left behind; click the "shared by all projects" checkbox. This flap will now appear in all projects, and in particular will be seen both in project A and project B.
* While in project A, grab the morphs you wish to use and deposit them onto the flap.
* Go to project B, and grab the morphs from the flap and deposit them onto the desktop of project B.
* Once you are done, you will probably want to destroy the new flap ("destroy this flap" from the flap tab's own halo menu.)
-- Scott
At 10:53 PM -0700 10/16/01, Ross Boylan wrote:
I have a project I'm working on that I intermittently publish to BSS (see the Activity project if you're curious, but it's sparsely documented). It's a priority planning tool, and I now have a fair amount of data in it. I want to publish it without the data to keep a little privacy, and also to save space. How can I do that?
I figure if I temporarily move things to another project I can avoid publishing them. I have a number of morphs I'd like to move. Is there a reasonable way to move them? I looked quickly in the Project and Morph protocols, and didn't see anything obvious. Perhaps I somehow get the Project's world and put the morph in there?
I sometimes use the "Squeak" Flap for this.
But, my favorite way is to get a ProjectView of the destination project and just Drag and Drop objects to it. This is nice because the copies go to the same places in the destination project as they were in the source project (thanks to Bob Arning!).
Cheers,
Alan
-----
At 8:21 AM -0700 10/17/01, Scott Wallace wrote:
Ross,
One easy way to move morphs from project to project is via flaps:
- Create a new flap. (world... flaps... make a new flap). After
the flap is created, a menu for it is left behind; click the "shared by all projects" checkbox. This flap will now appear in all projects, and in particular will be seen both in project A and project B.
- While in project A, grab the morphs you wish to use and deposit
them onto the flap.
- Go to project B, and grab the morphs from the flap and deposit
them onto the desktop of project B.
- Once you are done, you will probably want to destroy the new flap
("destroy this flap" from the flap tab's own halo menu.)
-- Scott
At 10:53 PM -0700 10/16/01, Ross Boylan wrote:
I have a project I'm working on that I intermittently publish to BSS (see the Activity project if you're curious, but it's sparsely documented). It's a priority planning tool, and I now have a fair amount of data in it. I want to publish it without the data to keep a little privacy, and also to save space. How can I do that?
I figure if I temporarily move things to another project I can avoid publishing them. I have a number of morphs I'd like to move. Is there a reasonable way to move them? I looked quickly in the Project and Morph protocols, and didn't see anything obvious. Perhaps I somehow get the Project's world and put the morph in there?
Unfortunately, neither of the methods described below for hiding data seem to work.
When I create (or use) a flap, I can drag some test morphs into it. However, SystemWindows (which I think all my stuff is) will not stick in the flap but just drop behind it. I have tried fiddling with their drag and drop setting and manipulating them in various ways, but always with the same non-stick result.
They also won't drop into ProjectView's (at least, the one I go by (ProjectViewMorph on: (Project named: 'Almost Top')) openInWorld). When I try to put regular morphs in those views, I get a nice message that they are accepted, but then they seem to bounce back to the previous location in the original project. However, the vanilla morphs did also appear in the other project when I visited them.
I'm currently at 3.2alpha #4441; I'm going to be reviewing more recent updates for inclusion. Perhaps they'll have a fix. Then again, perhaps I just don't know how to make it work!
If anyone could explain to me what's going on, or how to hide my data, I'd appreciate it.
Thanks.
On Wed, Oct 17, 2001 at 10:06:21AM -0800, Alan Kay wrote:
I sometimes use the "Squeak" Flap for this.
But, my favorite way is to get a ProjectView of the destination project and just Drag and Drop objects to it. This is nice because the copies go to the same places in the destination project as they were in the source project (thanks to Bob Arning!).
Cheers,
Alan
At 8:21 AM -0700 10/17/01, Scott Wallace wrote:
Ross,
One easy way to move morphs from project to project is via flaps:
- Create a new flap. (world... flaps... make a new flap). After
the flap is created, a menu for it is left behind; click the "shared by all projects" checkbox. This flap will now appear in all projects, and in particular will be seen both in project A and project B.
- While in project A, grab the morphs you wish to use and deposit
them onto the flap.
- Go to project B, and grab the morphs from the flap and deposit
them onto the desktop of project B.
- Once you are done, you will probably want to destroy the new flap
("destroy this flap" from the flap tab's own halo menu.)
-- Scott
At 10:53 PM -0700 10/16/01, Ross Boylan wrote:
I have a project I'm working on that I intermittently publish to BSS (see the Activity project if you're curious, but it's sparsely documented). It's a priority planning tool, and I now have a fair amount of data in it. I want to publish it without the data to keep a little privacy, and also to save space. How can I do that?
I figure if I temporarily move things to another project I can avoid publishing them. I have a number of morphs I'd like to move. Is there a reasonable way to move them? I looked quickly in the Project and Morph protocols, and didn't see anything obvious. Perhaps I somehow get the Project's world and put the morph in there?
--
Hi, Ross,
See:
http://groups.yahoo.com/group/squeak/message/20502
or, for a more recent mention of this topic,
http://groups.yahoo.com/group/squeak/message/36889
But how would a person ever figure this out on his own?
If you had a suspicion that this matter would be governed somehow by a "Preference," you could turn to the "search" facility in Preferences:
Open up a Preferences panel, go to the ? page, type something into the what-to-search-for pane, and hit the Search button.
If you type "window", you'll get fifteen hits, including the one you need.
If you type "drop", you'll get six hits, including the one you need.
If you type "embed", you'll hit the jackpot right away.
-- Scott
At 11:22 PM -0800 12/23/01, Ross Boylan wrote:
When I create (or use) a flap, I can drag some test morphs into it. However, SystemWindows (which I think all my stuff is) will not stick in the flap but just drop behind it. I have tried fiddling with their drag and drop setting and manipulating them in various ways, but always with the same non-stick result.
Cheers,
-- Scott
I just discovered that the semantics of moving things between projects by dropping them in a project view appears to be a (deep) copy. In contrast, dropping them on flaps looks at first blush like a move.
I haven't fully traced through or cleaned up things, but I thought I'd warn others who might be thinking of the same maneuver.
Visually, dropping something into a project creates a copy, since the original remains in the current project. So the hints are all there, but in my case hope and expectation triumphed over what was in front of my face. So I had a bunch of windows up, each referring to the same underlying data. After I moved them, I had many copies of the underlying data.
Since this is a warning, not a warranty, I'll say that I'm not sure that moving a bunch of morphs to the flap, and then into a different project, will avoid this problem.
Ross --
Moving an object to a global flap and then into another project is supposed to be the same as a move (no new object is created).
Cheers,
Alan
--------
At 1:13 PM -0800 12/30/01, Ross Boylan wrote:
I just discovered that the semantics of moving things between projects by dropping them in a project view appears to be a (deep) copy. In contrast, dropping them on flaps looks at first blush like a move.
I haven't fully traced through or cleaned up things, but I thought I'd warn others who might be thinking of the same maneuver.
Visually, dropping something into a project creates a copy, since the original remains in the current project. So the hints are all there, but in my case hope and expectation triumphed over what was in front of my face. So I had a bunch of windows up, each referring to the same underlying data. After I moved them, I had many copies of the underlying data.
Since this is a warning, not a warranty, I'll say that I'm not sure that moving a bunch of morphs to the flap, and then into a different project, will avoid this problem.
squeak-dev@lists.squeakfoundation.org
-
Alan Kay -
Ross Boylan -
Scott Wallace