On Wednesday 15 March 2006 10:31, Jose' Matos wrote: > On Tuesday 14 March 2006 17:55, Robert van der Kamp wrote: > > Hi list, long time ago for me. I see you guys have been > > busy. :) > > Hi Robert, > good to see you again.
Hi Jose! > I don't think that all is in place to do what you want. That's too bad. > > 1. I want each of the systems have their own document, > > explaining the system's features, etc. > > One way would be to have a master document in the root > and then use the other documents as slaves. So each > project would have its lyx file (That could include other > files...). I guessed it would have to be set up like this, yes. So the master-slave pattern can repeat again in the slave docs? Nice... > > 2. I want to be able to hyperlink from these documents > > to other Lyx documents (e.g. a section, a table, a > > figure), or to certain functions or other contructs in > > the C/C++ source code. > > In lyx that requires to always load the master > document. Now that could be a serious problem with some 80 documents involved. The master doc, with all slaves included, could become too big to handle easily. And there's no way to make a hyperlink (or crossref) to a non-lyx doc, like a C source file, right? > > 5. And finally I need all the individual files > > converted to HTML, the HTML file stored next to the > > orginal Lyx file in the corresponding subfolders, and > > with the hyperlinks now pointing to the associated HTML > > file instead of the original Lyx file, thus creating a > > nice web of HTML documentation. > > Here you need to tweak the latex to html converters as > it is not possible now. Yes, I guessed as much. What I need is some 'distributed documentation' feature, but it isn't implemented in any of the apps I tried so far (OpenOffice, Lyx). The master-slave feature comes half-way, but the moment you want the slave docs individually converted (distributed) as a batch, using the master document concept, it's a no no. Okay, thanks for the info Jose. Appreciated! - Robert
