Duncan Gibson wrote: >> I thought about it after my previous proposal: >> http://www.fltk.org/newsgroups.php?gfltk.development+v:7318 >> and I think the title page would best look like this: >> >> <html table>: >> --------------------------------------------------------------- >> [ snip main part ] >> --------------------------------------------------------------- >> <end of html table> >> >> \htmlonly >> Index Class Index >> Function Index >> --------------------------------------------------------------- >> \endhtmlonly >> >> I did some experiments with \htmlonly within the table, and >> it didn't work. The problematic part is the "Class Index" >> and the "Function Index". They link to doxygen'erated >> pages (annotated.html and globals_func.html or so). IMHO >> these should be excluded from the pdf docs. > > I already reorganized the intro page someone, and it almost > looks like that. I also question whether it is worth having > the generated Class Index and Function Index on this page at > all when they are available in the navigation frame on the > left or via the tabs at the top of all generated html pages.
Agreed, +1 from me. >> There are also some links in the introduction chapters >> that refer to (e.g.) "Chapter 3". They would have to be >> adjusted, too (they are currently wrong, anyway). >> >> I found that looking in the pdf file is a good way to >> find (bad) external html links, because they are red. > > One of the next doxygen tasks I had in mind was to go through > all of the *.dox files and replace the old HTML anchors and links > with doxygen \ref and \anchor as needed. As noted elsewhere, the > old HTML links are not relocatable so are useless in the PDF. Fine :-) > I also wonder whether we should limit the amount of cross-linking > from the *.H and *.cxx files. It's already going to be an effort > to go through just the *.dox files in one directory checking them > for consistency without including the code sources as well. Without looking at the amount or usefulness of the links to intro chapters in the *.H and *.cxx files, I would think that you are right. IMHO we should try to come to a point where the introduction is a closed "book" or tutorial with links to the reference manual, and the *.H/.cxx files are the sources of the "reference manual". There should be only exceptions where we need to link back to the tutorial, e.g. fluid or subclassing. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
