Best practices in keeping file sizes small

[Mark Wieder]

Vijay-

Monday, April 16, 2007, 7:52:03 AM, you wrote:

> Are there any ways to reduce the size of an executable??

If you're used to development in another environment (C, perhaps) you
may well wonder about this. There's no way at the present to pick and
choose which libraries get bundled into an executable beyond just a
few choices. Someday in the future that may change.

But consider that you've got the entire GUI environment at your
disposable in an executable - a full-blown database frontend or arcade
game isn't that much bigger than a "hello, world" program. It's
certainly a two-edged sword - I wouldn't normally consider writing a
"hello, world" program in rev, but I have been known to write
graphical front ends to perl scripts. The upside is never having to
worry about where or whether the other libraries are loaded.

Here's my tip of the day: only one stack needs the engine attached. If
you have several stacks that need to work together, consider keeping
them as separate stack files and loading them from the mainstack.
You'll find that they may only be a few k in size, since there's no
extra baggage to carry around. Also, they can be modified and updated
without needing to recompile the main stack/engine combination.

Oh, all right... a second tip: you might want to consider distributing
just the stacks themselves along with instructions about where to
download StackRunner:

http://www.sonsothunder.com/devres/revolution/downloads/StackRunner.htm

-- 
-Mark Wieder
 mwieder at ahsoftware.net