I just sent out an updated changeset for the fat lzo's patch. In order to get swf10 lzo libraries to instantiate their top level forms in the proper order (primarily the calls to LzInstantiateView) I made something similar to how main apps start up, where all the top level forms get stuffed into the "runtopleveldefinitions()" method.
Each lzo library has its own constructor class, with a "runtoplevelDefinitions()" method which contains any top level defs from the library. The main app, when it links in lzo's, adds calls to its own "runtopleveldefinitons" method which call the runtopleveldefintions method of each lzo, in the order they were first encountered in the source. A .lzo file can contain at most one .swc and one .dhtml runtime=specific object code file, and the files are tagged with the compiler options, so if you build a lzo lib in non-debug mode, and then compile an app that uses it in debug mode, it will use the runtime-independent lzs script code instead of trying to link in the binary object code. -- Henry Minsky Software Architect [email protected]
