Hi Alex,
I don't think we should make ASDocs an application. If we would, Google could no longer index the online resources. Currently if I need info on an API I search in google and it usually directs me to an Adobe page where I can read it. Another thing is, in the current ASDocs I remember some methods, classes, properties being flagged as "Air" ... in case of FlexJS we would additionally need "Flash" and "JavaScript" because all of this conditional code. I'll check out if I can find some comment parsing code in falconjx, if there is eventually I could use this ... I'll dig a little deeper ... and I don't think having API documentation is a small fish ... I think it's essential. Ok ... you could continue to use the old ASDoc but this just makes things more complicated for new users (and existing ones) Chris ________________________________ Von: Alex Harui <[email protected]> Gesendet: Montag, 1. August 2016 20:29:09 An: [email protected] Betreff: Re: AW: AW: [FlexJS] ASDoc? I think there are past discussions about ASDoc and Falcon in the archives. I think FalconJX does keep the asdoc around in the AST nodes. I think you are probably right that Falcon doesn't. Some folks think that writing an ASDoc Emitter for FalconJX will be the fastest way for us to get ASDoc output working. I think that's what I would do if I were to spend any time on it, which I don't plan to right now. Too many bigger fish given that we can use the Flex SDK for ASDoc. Longer-term, I keep wondering whether FlexJS should produce ASDoc as we know it (a pile of HTML files). IMO, FlexJS will have additional doc filtering needs. Because we have separation of concerns with the beads pattern, there are going to be lots of public APIs that the application developer doesn't really need to know about, and public APIs that component developers need to know about. And maybe more attributes, like components that only work in HTML5, or components that are JS-only, etc. Having the ability for the doc to filter what you see might be very useful. So I keep thinking about ASDoc as a FlexJS app instead of static HTML files, and I think if we did that, we might output something other than what the Flex SDK does now for ASDoc. -Alex On 8/1/16, 11:19 AM, "Christofer Dutz" <[email protected]> wrote: >Thinking about it, I think all the interceptor site us attach the content >of the comment to the ast of falcon. I bet usually the comments are not >carried along as the comments shouldn't have any effect on the compiled >output. We probably need to serialize the nodes of the ast using a to be >written asdoc parser, that doesn't seem to exist yet. I remember the old >asdoc having problems so it might be better to write a new one. Is the >format described anywhere? I'd like to write an antlr4 grammar from that. > >Chris > > > >Von meinem Samsung Galaxy Smartphone gesendet. > > >-------- Ursprüngliche Nachricht -------- >Von: Josh Tynjala <[email protected]> >Datum: 01.08.16 17:03 (GMT+01:00) >An: [email protected] >Betreff: Re: AW: [FlexJS] ASDoc? > >I think Adobe still uses the older asdoc in their AIR SDK with ASC 2.0 >too. > >- Josh > >On Aug 1, 2016 7:52 AM, "Alex Harui" <[email protected]> wrote: > >> >> >> On 8/1/16, 7:42 AM, "Christofer Dutz" <[email protected]> wrote: >> >> >Soooo ... any ideas/suggestions/whatever? Hope I didn't stumble over a >> >"TODO: This feature has to be implemented" :-( >> >> I got lost reading your email. ASDoc generation works from the flex-sdk >> for generating ASDoc for flex-asjs. It is ASDoc, not JavaDoc. AFAIK, >>no >> work has been done on ASDoc generation from flex-falcon. Volunteers are >> welcome to work on it. >> >> Thanks, >> -Alex >> >>
