To answer my own questions: To integrate the framework doc into my own docs, add a source-path pointing to the framework source to the asdoc compiler options.
As for the problem with includes.. still cant resolve that, currently the only thing is to only doc the components rather than the entire library. --- In [email protected], "reflexactions" <[EMAIL PROTECTED]> wrote: > > I have a couple of issues creating docs for a component. > > Firstly I want to doc the whole source branch rather than just one > class. > > When I specify source-path and docs-sources to point to the root of > my source and run AsDocs it genererates error for included metadata > actionscript files i.e. /styles/metadata/BorderStyles.as when it sees > this file and tries to parse it(as it recursively parses all .as > files) it recognises its not a proper class file and stops running. > > I dont want to have to maintain different versions of the source > code, one with includes and one without so how do you handle this/how > did Adobe create their docs... > > Second issue is that when I can create output it is only for my own > classes i.e. although I extend UIComponent it doesnt show "inherited" > props/events etc which is confusing to people reading the docs as > they are not seeing the majority of methods or props for a component. > > So how do I make my docs "integrate" with the framework source docs? > > tks >
