Hello, > I know. In fact, my path is gekkota, and I've added a line like the > following to monodoc.xml: > > <node label="Gekkota Libraries" name="gekkota"/> > > By the way, why doesn't browser.exe automatically create a new node > for each *.source file it finds in the sources directory? Eventually, > *.source could also contain a label element...
My rationale was that monodoc.xml would define the skeleton, and various different providers would attach there. So for example, Gekkota should probably be on "Third Party software" node or something. Monodoc is on its early days, and today class libraries are at the top, but they will eventually move to Monodoc/Reference/Class Libraries, or we might find a different organization. If we allow people to choose new paths to install their stuff at, then we cant keep Monodoc's tree clean, nor can we reorganize it without talking to all the providers. So the best thing to do here is find an appropriate name, register that with us, and then use that pathname. > I'd like to generate also plain HTML documentation, so I can publish it > on our web site. Actually, to do that, I've to convert the XML files > generated with updater.exe to a single XML file (see the utility > written by Jarek), and then I can generate either plain HTML or > LaTeX source with NDoc. > > I hope not to bore you, Miguel. That works. _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
