Smalltalk User Guide : Getting started : System architecture : Saving an image to keep components loaded
Saving an image to keep components loaded
Until you save your image, new work that you have done exists only in temporary memory. The system does not automatically update the abt.icx file on disk. It is up to you to save the image at appropriate times.
After you select one of the Save Image options from the File menu, work stored in temporary memory becomes part of the abt.icx file. This means that when you next start the system, the development environment is exactly the same as when you saved the image.
Saving your image keeps components that you have been working on loaded in the image. You might want to save your image when one of the following conditions apply:
You have been developing for a while and are satisfied with the results.
You leave your desk or begin work in another application.
You are about to exit the system.
When the system saves an image, the new image is first written to disk; then the old image is erased. Thus, for the save to be successful, you must have a free amount of disk space equal to the size of the image in memory. For example, if you are using an image that is 10MB in size, you need at least 10MB of free disk space to save the image.
If you exit the system without saving the image, all work done since the last save is lost from the image. However, you can recover the lost work. See Recovering from image crashes for information on recovery.
You have three options for saving your Smalltalk image:
Save Image
Saves the image to a file called abt.icx.
Save Image As
Saves the image to an alternate image file.
Exit <product>
The system displays a window, asking whether you want to save the image to the abt.icx file upon exiting from VA Smalltalk.
Last modified date: 06/02/2020