Hey, all:
Is there a how-to on moving code between images? I like Damien's dev-images so I like to update when he does, but is there an easy way to move all my stuff between an old image and a new one?
And what about desktop? If I keep stuff in workspaces and Transcripts and so on, can I move those? (I mean, I can, if I do it manually but...)
===Blake===
Blake wrote:
Hey, all:
Is there a how-to on moving code between images? I like Damien'sdev-images so I like to update when he does, but is there an easy way to move all my stuff between an old image and a new one?
Hi Blake,
Monticello is a great way, at least for me. http://www.wiresong.ca/Monticello http://wiki.squeak.org/squeak/43 http://wiki.squeak.org/squeak/43
And what about desktop? If I keep stuff in workspaces andTranscripts and so on, can I move those? (I mean, I can, if I do it manually but...)
You can save workspace contents in files. There is a selection in the window menu: "save contents to a file...". There's probably a better way if there are many workspaces. (Bert seems to always come up with great ways to do things like this.)
On Sat, 21 Apr 2007 17:03:07 -0700, Brad Fuller brad@bradfuller.com wrote:
Hi Blake,
Monticello is a great way, at least for me. http://www.wiresong.ca/Monticello http://wiki.squeak.org/squeak/43 http://wiki.squeak.org/squeak/43
The docs pointed to in the first link suggest you can use #fileOut, which the PackageInfo class doesn't seem to understand exactly, but more importantly, I don't think I have the hang of the class, in general. If I follow the code in that link:
refactory := PackageInfo named: 'Refactory'. refactory classes.
I get an empty OrderedCollection. Frankly, I don't even see =how= it could work.
Blake wrote:
On Sat, 21 Apr 2007 17:03:07 -0700, Brad Fuller brad@bradfuller.com wrote:
Hi Blake,
Monticello is a great way, at least for me. http://www.wiresong.ca/Monticello http://wiki.squeak.org/squeak/43 http://wiki.squeak.org/squeak/43
The docs pointed to in the first link suggest you can use #fileOut, which the PackageInfo class doesn't seem to understand exactly, but more importantly, I don't think I have the hang of the class, in general. If I follow the code in that link:
refactory := PackageInfo named: 'Refactory'. refactory classes.
I get an empty OrderedCollection. Frankly, I don't even see =how= it could work.
I suggest you start at: Getting Started: http://www.wiresong.ca/Monticello/UserManual/GettingStarted/ You probably already have Monticello included in your image. From the World menu try "open...>>Monticello Browser" Do you see it?
brad fuller www.bradfuller.com +1 (408) 799-6124
El 4/21/07 8:48 PM, "Blake" blake@kingdomrpg.com escribió:
Hey, all:
Is there a how-to on moving code between images? I like Damien's dev-images so I like to update when he does, but is there an easy way to move all my stuff between an old image and a new one?
And what about desktop? If I keep stuff in workspaces and Transcripts and so on, can I move those? (I mean, I can, if I do it manually but...)
===Blake===
If you have a 3.9 7067 final image, have good chances of upgrade to 3.10. Do a good backup and on the working image open the Squeak flap and push upgrades. When you was asked to delete all projects, ask no. Could take some time, but you should end with a green degradee showing what you are in 3/10 now. Hint, you must start in a clear morph project window, the process wipes all morphs in world. You could publish a .pr named "Today" in your disk and when process finish, load this .pr into 3.10. Any problems , I wish know..
If you have a earlier image , save all in .pr . Some could load into 3.10 and some not. No general recipes, is each .pr specific problem Tell me whose what don't load and what the debugger said and I try to assist on what to do.
Edgar
Do not be seduced by the image!
The idea of "an image" is wonderful, and is one of the core ideas of Smalltalk. It is great to restart the system and have all your debugging sessions where you left them. However, the image is fragile, and it can be hard to share work the you have done to the image. Someday you will develop an image that works OK until you save it, and then when you try to restart it, it will not work. It can hard to export changes from your image so that other people can use them. It can be hard to update your image with changes from other people.
The key to living in an image happily is to always be able to regenerate it. All long-term work should be stored outside the image, or at least storable outside the image.
The best way to store code in Squeak at the moment is with Monticello. It is far from perfect, but it makes it easy to compare different versions of your source code and can usually merge them.
I have not had good luck with storing projects. Instead, I make sure I can store all the objects I need. Workspaces go in text files. For other objects, I either make it possible to write them to disk or I always create them from scripts, and store the scripts in Monticello.
If you don't make sure you can regenerate your system from components then you will end up stuck to an old version of the image and unable to migrate to a new version.
-Ralph Johnson
beginners@lists.squeakfoundation.org
-
Blake -
Brad Fuller -
Edgar J. De Cleene -
Ralph Johnson