Re: Image versus package savers?

I typically do both. Early on, I ignore images and work exclusively
with packages. Once I'm beyond the "testing" phases of worksheets, etc,
then I start working on the image. However, even in the image,
everything (for me) is still package based. I've lost images, and being
able to remake the image quickly from the packages has been very handy.

Note: I've only just recently purchased the Dolphin pro version
(whee!), and I haven't been dealing if very large codebases yet (in
Smalltalk), so my approach will probably vary some in the future. Also,
I transfer the packages from machine to machine by means other than
thumbdrive/disk, so having my code saved in a tight format is nice
(where the image files can be quite bloated).

Jeff M.

Griff wrote:
As far as version control for applications within in your image, would
you say that you prefer backing up your whole image frequently and
exporting then backing up your packages frequently, or vice versa?

If you are using Subversion to do so, do you keep two separate
repositories: one for mostly binaries (like system images, graphical
images) and one for primarily text files (exported packages, text
files)?

.