Wednesday, April 16, 2008
Wednesday, April 16, 2008
While I am on my PC (and thus cannot use Visdoc to generate AS3 documentation for my packages), I am using ASDoc. While normally this is great, I've run into a large issue.Some of my classes implement UI elements that come from the CS3 IDE... and I export them with class names (classes are generated for me). This is so I can "attach" the UI elements via the new command. Everything works just dandy.
However, if ASDoc encounters an error, it won't document. And since several UI elements are implemented in some of my classes (they are dependent on generated classes from the IDE), I end up getting no documentation output.
Is there some kind of trick to get this rolling, or is ASDoc simply not engineered to be able to handle this kind of thing? I suppose I can wait until later to generate my documentation, but it would be cool to know if there is a fairly convenient work-around.
Update:
Taking a comment to heart, I have created a SWC from my FLA's Library.
I inspected it using nemo400 & indeed all of the generated classes are in there. However, I really do dislike the command-line, and have been using a tool called ASDocGUI. But because it provides simple use, I am unable to actually add the class path to the SWC too. I suppose I have to command line things. But at least those generated classes are available to ASDoc now and I should be able to snag some documentation out of all of it.
I can't wait to sick Visdoc on it however :)
1 Comments:
-
Josh Tynjala said...
-
“It's an extra step, but you could probably export your library assets in a SWC and add that to ASDoc's library-path.”
