Hi Alex,

> 1) The Falcon compiler code base may be easier to work with.

I don't know anything about the Falcon compiler, so excuse if my questions are 
dumb:
- Does the Falcon compiler include ASDOC compiler ? or is it limited to AS/MMXL 
compiler ?
- Is it already operational ? 
- Also, current ASDOC build uses asdoc  ant task, which is a wrapper on the 
asdoc compiler. Will that change in the future?

> 2) I've been wondering if an AIR app would easier to maintain as the ASDoc 
> generator.  I don't know how XSLT at all.
Basically asdoc generation is done in two passes:
- first, java-based classes (flex2.compiler.asdoc.TopLevelClassesGenerator and 
co) will parse the source code for asdoc comments, and generate high-level xml 
files with all the asdoc data. That makes the XLST job much easier. The result 
is in asdoc-ouput/tempdita/
- then the XSLT in asdoc/templates will parse these xml files and generate the 
final html structure.

> 4)  I think another feature we need ASDoc is to have links to the Adobe ASDoc 
> for flash.*.* packages.
Fully agree that the flash.*.* ASDOC should be added.
So of course having the flash API seamlessly embedded in the ApacheFlex doc 
(that is inherited props, shared UI, etc...) is out of reach, 
but providing a link would be acceptable, and shouldn't be that  difficult :-)

Regarding the asdoc as an AIR app:  
I understand the concerns but that's a lot of work. 
I was more on the idea of "tweaking" the existing tools, than rewriting 
everything... 
So if someone else is interested in doing it, "pourquoi pas ?" :-)

Regards,

Maurice         

-----Message d'origine-----
De : Alex Harui [mailto:aha...@adobe.com] 
Envoyé : vendredi 4 octobre 2013 06:02
À : dev@flex.apache.org
Objet : Re: Thoughts about ApacheFlex ASDOC

Hi Maurice,

If you've got the time and energy, go for it.  A couple of things to
consider:

1) The Falcon compiler code base may be easier to work with
2) I've been wondering if an AIR app would easier to maintain as the ASDoc 
generator.  I don't know how XSLT at all.
3) And I've been wondering why our ASDoc viewer isn't itself an AIR app.
I suppose we should always have an HTML version to browse from the web, but an 
AIR version should be a much smaller download if it could display from raw data 
instead of downloading the entire set of HTML files, would allow off-line 
access, would allow AIR-related examples, and a better UX.
4) I think another feature we need ASDoc is to have links to the Adobe ASDoc 
for flash.*.* packages.

-Alex

 

Reply via email to