We intended Modules to be "the way". You'd bake the manifest into the SWF or have some contract via the interface to effectively get the manifest. DescribeType is very slow so pure introspection/reflection and even the use of metadata can be a performance problem, so it is a classic speed trade-off. The more work you do upfront to build the SWFs, the less work will be needed at runtime.
I think the original modules developer showed somethings on his blog in this regard. I haven't looked, but his stuff is here: http://blogs.adobe.com/rgonzalez/ -Alex ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Rick Winscot Sent: Saturday, August 23, 2008 2:04 PM To: [email protected] Subject: [flexcoders] Introspection Recommendations What would any of you all say to a client who wants to implement, in Flex, an extensible plug-in framework through pure introspection? This would include things like property and event management. To help frame this - with the right framework in place one could create a property explorer to manage bits a runtime. Anyway... Initially I recommended the use of a manifest and interfaces to help keep / track target properties, and manage event life cycles and such... but they are concerned about having to manage 'files' in addition to the swf. If possible, I would like to find a balance somewhere between using 'describeType' and something that is too restrictive. Any recommendation? Am I missing something? Rick Winscot
