Yeah, don't worry about it man! I was just showing you the error.
The Flex SDK asdoc emits DITA XML files and then runs XSL on the DITA
files. So I guess, if you produced the same DITA spec from the new
intermediate model, you could use the same XSL transformations. That would
be the way to do it instead of concocting some new XML dialect.
I'm doing a lot this summer with my mother-in laws house and finishing up
those audio apps, so my time is severely limited. I actually spent way more
time on Apache that I thought I was going to and have to make up some time.
:)
I just wanted to get this up so at least people could look at the available
API since ASDoc won't create the docs.
Mike
On Tue, Jun 23, 2015 at 11:35 AM, Alex Harui <aha...@adobe.com> wrote:
>
>
> On 6/23/15, 7:47 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:
> >
> >You can try and see if you could get asdoc working on those files but, I
> >boiled it down and asdoc just didn't want to parse Object, it said
> >Namespace not found and pointed to the package { declaration.
>
> I assume this is asdoc from the current Flex SDK? We still don’t have any
> Falcon-based ASDoc other than what you wrote, right? I’d prefer not to
> have to rummage through the old asdoc source.
>
> I thought existing asdoc generated some intermediate files then somehow
> ran XSLT on them. I’ll put this on my list, but right now it would go
> after trying to get my other test app working across domains and trying to
> improve the way it looks.
>
> -Alex
>
>
