SOURCE CODE SECURITY - for DrWimp users


The library has become rather large over the last few versions and now
exceeds 60k. Thus using it as a library for a RunImage means that even
the smallest and most simplest applications will be quite large. This
is undesirable.

Also your source code (the RunImage) will be open for everyone to see.

The total size of your source code combined with DrWimp can be reduced
spectacularly, and at the same time gain more security, by using the
applications contained in the Utils folder.

The procedure:

1. Store your original RunImage somewhere safe.

2. Link a copy of your RunImage with DrWimp using !Linker. (This
eliminates all unused wimp-functions and merges the !RunImage with the
remaining wimp-functions to produce a new linked !RunImage. A useful
reduction in disc storage space and run-time memory needs results.)

3. Compress the linked RunImage using !StrongBS (or another Basic
compression utility). (This can eliminate REMs, abbreviate variable
names, concatenate lines, etc. Apart from usually producing a large
reduction in !RunImage size, this process makes it very difficult to
read and alter the !RunImage. A run-time speed increase also occurs.)

4. Turn the linked and compressed RunImage into an absolute file by
dropping it onto !MakeApp2 and saving under a different name. (Renders
the !RunImage unreadable.)

5. Compress the result further by dropping it onto !Crunch, to give
you your final RunImage to distribute. (Further reduces the !RunImage
storage space - but not the run-time needs.)

EOF359
