Hi Stephen Thanks for your replay, this is what I eventually found in the documentation. Sad that the ASDoc tool fails if the source is defined externally (<mx:Script source="..." />) - it complains that "[public etc.] can only be used inside a package". I will never put my code inside the <mx:Script> tag directly, though, so I'm out of luck.
If I'm correct, you are from the documentation team so you could feel the pain it currently causes me. Documentation is essential for me as a component developer but so is the productivity which is much higher in MXML in certain scenarios. Please fix this bug in ASDoc and allow me to generate documentation equivalently from both ActionScript and MXML (they should both be first-class code artefacts, at least I can see no good reason why they shouldn't). Regards, Borek --- In [email protected], "Stephen Gilson" <[EMAIL PROTECTED]> wrote: > > There is only limited support in ASDoc for MXML files. > > - All ActionScript entities defined in an <mx:Script> block, such as > properties and methods, appear in the output. Items defined in MXML tags > do not appear in the ASDoc output. > > - You can only insert an ASDoc comment in an <mx:Script> block of an > MXML file. > > - The superclass corresponds to the first tag in the MXML file. For an > application file, that tag is the <mx:Application> tag and therefore an > MXML application file appears in the ASDoc output as a subclass of the > Application class. > > Stephen >
