Flex modules == win
Those using FlexBuilder3 will have noticed a new option in File>New. MXML Module! They're badass. I tried to explain what a module is yesterday, and failed terribly. So I'll copy/paste from the livedocs...
Modules are SWF files that can be loaded and unloaded by an application. They cannot be run independently of an application, but any number of applications can share the modules.
Modules let you split your application into several pieces, or modules. The main application, or shell, can dynamically load other modules that it requires, when it needs them. It does not have to load all modules when it starts, nor does it have to load any modules if the user does not interact with them. When the application no longer needs a module, it can unload the module to free up memory and resources.
Modular applications have the following benefits:
- Smaller initial download size of the SWF file.
- Shorter load time due to smaller SWF file size.
- Better encapsulation of related aspects of an application. For example, a "reporting" feature can be separated into a module that you can then work on independently.
Drop in a ModuleLoader. Search livedocs for the CustomModuleLoader component, it's nice
Load a module into it. Pass this function the URL to the module's swf
modLoad.url = module;
}
Call a public function within the module. Note I type cast the loaded module here
(modLoad.child as disciplineModule).treeClicked(evt);
}
There are no comments for this entry.
[Add Comment]