On Wednesday, February 4, 2004, at 03:57 PM, Dar Scott wrote:
So the issues:
For other than OS X, the result is not monolithic, in general.
If forced to be, the path is not what it was in most debugging and testing.
Oh, the application main stack is moved in the message path anyway.
OK, I think I have this pretty much resolved.
1.
For simple, tiny applications from a single stack-file, build monolithic.
2.
For most applications allow components to fall as they may, even if that means
using many outside library stacks.
3.
In extremely rare cases a complex multi-stack-file application can not be build as #2 and must be #1, so do one of these:
3.A Flatten it into a single stack-file and build as #1.
3.B Use Krunched In-stack Stack-file & Embedded External Technology (KISSFEET) (mine is not ready yet)
4.
In all cases, be aware that the mainStack of the standalone will be inserted into the stack just before the engine and handle one of these ways:
4.A Review Design
4.B Test with what will be the inserted stack by back script or something.
4.C Use a splash screen stack for the app and review it carefully
I think that my need in #3 caused me to have blinders about #2.
Dar Scott
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
