Hi,

Ok now I managed to get things up and running. Having a look at the way the 
asdocs are generated from ANT I can see that they are generated with „SWF“ 
turned on and „JS“ turned off. This will only generate the Flash version of the 
documentation. We have quite a lot of classes, methods and properties that only 
exist in SWF or JS, so I think a real api documentation should contain both and 
point out if an element is available in SWF, JS or both. I am trying to do this 
in the compie-asdoc maven mojo by doing a compilation for SWF and outputting 
things to „target/asdoc/swf“ and a second one with JS to „target/asdoc/js“. 
Then I’m able to merge both and create „target/asdoc/merged“ which contains 
exactly the information where an element is available. The last step will then 
simply be sending each XML to a XSLT and using that HTML as final output for 
the asdoc compilation.

So far so good. The SWF xml outupt looks gread, even if I don’t know why 
classes, index and tags are Json files, but I’ll fix that later. Unfortunately 
I can’t compile the JS version of Core (the first module I tried) because of a 
missing definition of the JS version of TextField ... where does this come 
from? Any ideas?

Chris

Am 21.12.16, 09:41 schrieb "Christofer Dutz" <[email protected]>:

    
    Unfortunately the JSSharedData is byting me at the moment ... I’m having 
static stuff bleeding into one execution from another ... we should generally 
address that sooner than later ☹
    
    Chris
    
    
    Am 21.12.16, 08:15 schrieb "piotrz" <[email protected]>:
    
        It's about half past 8 AM and I'm in a Zombie Mode, so doing weird and
        unpredictable things! I hope my code will be ok at half past 1 PM when 
other
        guys from my Team will start doing Code Inspections. :D
        
        Thanks Chris!
        
        Looking forward to the results. :)
        
        Piotr
        
        
        
        -----
        Apache Flex PMC
        [email protected]
        --
        View this message in context: 
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-ASDoc-Any-reason-for-additional-config-options-tp57486p57489.html
        Sent from the Apache Flex Development mailing list archive at 
Nabble.com.
        
    
    

Reply via email to