Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!ssc-vax!bcsaic!vanover
From: vanover@bcsaic.UUCP (Jann VanOver)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Stack Compaction and large distributions
Message-ID: <45267@bcsaic.UUCP>
Date: 16 Apr 91 16:15:23 GMT
References: <16495@chaph.usc.edu>
Organization: Boeing Computer Services AI Center, Seattle
Lines: 42

In article <16495@chaph.usc.edu> hashem@usc.edu (Basil Hashem) writes:
>Dear n-ether-lan-ders,
>
>1. What exactly does File menu command "Compact Stack" do?  What is compacted?
Deleted objects leave "holes" in the file.  Especially fields that have
been deleted.  I have noticed that deleting resources does not change
the "freesize", therefore doesn't have to be compacted.

btw, make sure you have as much disk space available as the size of the
stack before you compact.

>
>2. I'm designing a stack with lots of sounds in it.  I've used a 4:1
>compression to try and save space, does anyone have other suggestions to help
>reduce the size of the stack without sacrificing any more sound quality?
Don't know

>
>3. What are some techniques that some of you have used to distribute a multi-
>disk stack?  Supposing that the end-users don't have (or don't deal with)
>StuffIt/Compactor/etc...  Is HDBackup is only appropriate choice?  Just
>collecting before I going off to code it up myself.

Both Stuffit and Compactor have a capability to build self-extracting
archives, ie. the end users don't need nothin' but a mac.  These are the
ONLY appropriate choices.  I've never seen anything useful in any other
form.

The accepted form for documentation is some type of PLAIN TEXT file -
preferably named README, ideally a TeachText file.


So -- what's in these stacks?  Give us a preview-description-sales
pitch!

>
>Pre-thanks,

Pre-welcome    -- have fun!

Jann E VanOver
vanover@atc.boeing.com