I would like to propose that we package-for-the-web our cobundle
installer in a more efficient way for our next cobundle with Merlin
fcs. This will decrease the size of the footprint by a small amount of
153KB, but more importantly the install process will be much faster. On
a fast winNT machine that it usually takes 4 minutes and 28 seconds to
install, it will now only take 3 minutes and 49 seconds. This time
difference will be more dramatic on slower systems. Another plus is
that the decrease in time will be taken away from the part where the
user would normally have to stare at our "Setting up J2sdk" and "Setting
up Forte for Java" screens that have no progress bars.

When we build an installer project with install shield, the output is
about 10 installer files. We then use package-for-the-web to compress
these 10 files into a single .exe file (for example j2sdk.exe and
forte_ce.exe). The way we have been building the cobundle so far, is by
bundling up the single packaged-for-the-web forte_ce.exe and j2sdk.exe
bundles (which each include their 10 installer files packaged up). We
then package-for-the-web our 10 cobundle installer files with these 2
.exe bundles. Note that we are using package for the web 3 times, for
the forte .exe, the j2sdk .exe and the cobundle.exe. This may simplify
the build process, but it is inefficient during install time because we
are using the package-for-the-web technology 3 times. My proposal for
the cobundle is to package-for-the-web the 10 cobundle installer files
with the 10 forte_ce installer files and the 10 j2sdk installer files.
This way we will be only using the package-for-the-web technology once,
which reduces the footprint by 153KB. During the install when we invoke
the forte and j2sdk bundles silently, they won't need to
un-package-for-the-web which results in a faster install.
###@###.### 2002-01-24