How to reduce the standalone application's filesize built wi

[goomoo]

The compiled windows executable is toooo big, It is very slow when it starts up.
How to reduce the filesize and improve startup responsibility.

Thanks very much.

[Mark]

Hi,

How big is your standalone? To speed up initialization, you can create a small splash stack, which opens other stack files as needed. Your splash stack should contain a script like

Code: Select all

on startUp
  go stack "Main Window.rev"
end startUp

This script would open a second stack, with the actual interface. The file "Main Window.rev" would contain other scripts that open files as needed. E.g. a menu script may open navigation palettes or tools palettes when selected by the user. These stacks would stay closed, until the user needs them. This way, the user never needs to wait a long time to open all stacks.

This approach is called the "splash stack approach" because the first stack, which is used to build a standalone, often displays a splash window with the name of the app and a copyright notice, but you can also open the splash stack invisible and immediately continue to the main window.

Kind regards,

Mark

[goomoo]

Thanks for your reply, Mark.

As simple as a "hello,world" program, the executable file built with livecode 7.0 has 27+ M bytes on windows 7, I think this is not acceptable. In LiveCode 6.x, the final executable file is about 3M bytes, that's good.

Is there a plan to reduce the final filesize in future versions?

[Mark]

Hi,

I expect that LC 7 standalones will be slightly larget than LC 6 standalones, but 27MB is indeed too much. You could report this as a bug.

Kind regards,

Mark

[Klaus]

Hi guys,

this (BIG standalone file size in LC 7.0) is a known issue and has to do
with the new UNICODE libraries as Mark Waddingham recently wrote on the
mailing list, if I remember correctly.

Best

Klaus