Looking at Scott's old Python script lzx2html.py (part of http://wiki.openlaszlo.org/images/e/e8/Lzxdoc.zip), that script actually takes each LZX file of an application an applies an XSTL transformation to it:
> lzxdoc is a fairly simple tool that will traverse your LZX source tree and generate HTML documentaiton for the files within, much like Javadoc. It uses a stripped-down version of the documentation syntax seen in LFC files. It does not support live inline examples, HTML templates, inheritance, and probably a bunch of other stuff. > lzxdoc outputs an HTML file for each .lzx file, and an index.html that lists all of the lzx files, organized by directory. Most of the content of the README.txt still seems to be valid: > OpenLaszlo has fairly sophisticated scripts that build the reference manual for the foundation classes, etc. These scripts spit out very nice output, but they're too heavyweight to use for a project that simply needs internal documentation without live examples and so on. > So we extracted some pieces of these tools and hacked them up a bit to create lzxdoc. On Fri, Jan 7, 2011 at 11:03 PM, Raju Bitter < [email protected]> wrote: > Which mechanism is used to identify all files which make up one > application? Does anyone know how I can point to one LZX file and generate a > list of all other LZX files I'd need to process? > > On Fri, Jan 7, 2011 at 10:39 PM, Raju Bitter < > [email protected]> wrote: > >> Thanks, Tucker. That's what I guessed, that we have to use the XSLT >> transformation. I'm currently looking at this page, let's see how far I get >> with that. >> http://www.openlaszlo.org/lps4.9/docs/developers/doc-toolchain.html >> >> >> On Fri, Jan 7, 2011 at 10:13 PM, P T Withington <[email protected]> wrote: >> >>> Our doc tool maintainer is on sabbatical (:-0). I was able to fix a bug >>> in the tools by reading the doc doc. It's pretty well written. >>> >>> Basically OL use a bunch of XSLT to walk over the LZX and output >>> something that docbook understands and then use docbook to create the final >>> doc. >>> >>> I expect it would be reasonably easy to use the tools on your own LZX. >>> The complicated stuff is the bit that walks over the LFC JS and outputs >>> something that the LZX XSLT can parse... >>> >>> On 2011-01-07, at 16:05, Raju Bitter wrote: >>> >>> > Guess that means: no new tool available. Besides what's built into the >>> LPS >>> > for generating the OL docs. >>> > >>> > On Wed, Jan 5, 2011 at 8:33 PM, Raju Bitter < >>> > [email protected]> wrote: >>> > >>> >> What is the recommended tool for generating LZX documentation? The >>> wiki >>> >> lists the following tools: >>> >> http://wiki.openlaszlo.org/Development_Tools#Documentation_Tools >>> >> >>> >> The page on the LzxdocTool has not been updated since 2007. Does that >>> still >>> >> work with the 4.8 version of OL? >>> >> http://wiki.openlaszlo.org/LzxdocTool >>> >> >>> >> - Raju >>> >> >>> >>> >> >
