I’m talking about using XSLT in the Maven plugin to convert the XML to HTML.
You don’t even need a dependency to anything, because XSLT is so standard, that
it’s part oft he JDK.
XML, XSL and HTML are everything but rocket-science ... you can do some crazy
stuff with XSL, but that’s not what I’ll try to do. My plans are keeping things
as simple as possible.
And it’s still not me taking down FlexJS a path that no other language is going
down. I don’t recall any of the other main languages out there not providing
HTML API Docs.
What do I have to do to get the XML files? I’ll have a look at what I find.
And regarding the empty compiler jars ... they don’t contain anything but a
MANIFEST.MF (I generate them where I generatet he distribution).
Chris
Am 15.12.16, 18:47 schrieb "Alex Harui" <aha...@adobe.com>:
On 12/15/16, 2:59 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Hi Alex,
>
>great to hear that ... being someone who still thinks the static API
>documentation is important, I would like to work on a maven site mojo to
>generate that static stuff. I am very experienced with XSLT, so that
>shouldn’t be a problem. You mentioned, that the Falcon compiler outputs
>XML ... where is that output to and what do I need to do to make him
>generate that?
I have the beginnings of a DITA emitter, but it needs finishing. You are
welcome to finish it. IMO, the project is better off not having new
dependencies on XSLT. It is great that you are an expert at it, but it is
more important that we have redundancy in the community, so relying on
languages most of us know is better. If you want to modify the ASDoc app
to generate HTML pages that's great as well, but I don't understand why
static pages are better than dynamic pages. If your concern is search
engines, that is a problem we need to solve for every FlexJS app and the
answer hopefully isn't to generate a pile of HTML from your app.
My 2 cents,
-Alex
