Modularization of Flex Applications Public Class

About the Class

Flex is amongst the hottest emerging technology to create Rich Internet Applications. However, Rich Internet Applications are known to be heavy and take time to load. Programmers can make use of modularization to avoid this.

Modules are SWF files that can be loaded and unloaded by an application. Modules let you split your application into several pieces, or modules. The main application 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.

• Introduction to Flex
• What is modularization
• Why we need it/benefit of modularization
• How we used to do it in old flash applications
• How we can do it in Flex 3
• Why we need it/ benefit of modularization
• Larger Applications can be easily managed
• Different teams can manage different parts of the product
• Increases team productivity
• Compile time can be reduced as each individual module is compiled separately
• Change in a single module would require only the compilation of that module
• We don’t have to replace the whole application if there is a change in a single module only
• Different ways of modularization in Flex
• RSL – Runtime Shared Libraries (collection of shared classes & components)
• When we should use it and when not
• How RSL works
• Types of RSL
• Standalone applications i.e. SWFs (compiled separately can run as standalone application)
• mx:Module Flex Module (runs within flex application)

Language of instruction:

Keywords: adobe flex, adobe flash, modularization