This is called "lost in translation between engineering and
documentation", because its somewhat subtle.
It means that if you are using modules for code that doesn't include any
frameworks code, you should extend ModuleBase.
If your modules use code that interacts directly with the frameworks (in
particular, does it rely on CSS, and do you expect the product of the
module to be able to be added as a visual component) then you need to
extend Module so that the compiler does the correct code generation.
If you extend Module in a non-frameworks AS project, you will pull in
lots of code that you don't want.
-rg
________________________________
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Daniel Freiman
Sent: Tuesday, January 09, 2007 7:01 AM
To: flexcoders
Subject: [flexcoders] Modules and ActionScript
The docs say that you should extend from Module if you are using
mxml and ModuleBase if you are using Actionscript, but these Classes are
drastically different. One is a subclass of EventDispatcher (similar to
and Object) and one subclasses LayoutContainer (similar to Container).
This is a very important difference. I've tried using actionscript to
subclass Module and it works perfectly fine. Are the docs incorrect or
is there a more subtle reason why actionscript shouldn't extend Module?
- Dan
