I've got loadable libraries working to a large degree in swf9, although there are going to be some issues related to sloppy things we have been able to get away with in other runtimes regarding references to global variables and functions. But basic use of views, classes, resources, and script blocks in libraries seems to be working.
There is an issue though, which is that currently each library is getting linked to its own copy of the LFC, which obviously is wasteful and defeats somewhat the advantages of loadable libraries. So I need to figure out the best way to not link the LFC in. I am about to try experimenting with telling the flex compiler to not link in the LFC , using the 'external-library-path' option, and see if it can still be loaded and executed from the main app. If not, then I'm going to try using the "runtime shared library" feature, which will cause apps to be compiled which don't link in the LFC, but load it at runtime from a known URL. This is probably something we want to do anyway, as it will make our app size go way down, and will allow multiple applications to share the same LFC. But there could be versioning issues there, so we should make this a compiler option. This will unfortunately add some complexity to the embedding wrapper, but we already do something similar for the DHTML runtime (it loads the LFC separately, effectively making it a runtime shared library), so it shouldn't be a big deal. -- Henry Minsky Software Architect [EMAIL PROTECTED]
