ModuleManager is lower-level and therefore a bit more work. The most common thing people do with modules (generate some UI when switching to a viewstack page) is encapsulated in ModuleLoader. Everything else (Popup, class loading) probably requires using ModuleManager directly.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of reflexactions Sent: Thursday, January 24, 2008 1:46 AM To: [email protected] Subject: [flexcoders] ModuleLoader vs ModuleManager As I read the docs... If I use ModuleLoader it is a container that ultimately parents the module I load. If I use ModuleManager I can add the module directly as a child i.e. there is one less layer between me and the module. Is that right, does that make ModuleManger marginally more effecient because I dont have a redundant container? If so any hidden drawbacks to using ModuleManager? tks
