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 >> >> >> >> >
