> Good work! > Looks pretty good, the indentation with \par is nice :-)
I have to confess that I wasn't sure whether it would work, and whether it could be applied consistently over multiple paragraphs, but it was only after the final round of changes that it really came together. Although \code and \note blocks don't quite fit. > If this works with LaTeX / pdf, then I would vote for this. I've disabled the LATEX generation because it just takes too long to regenerate and verify the results of any experimentation. I shall re-enable it this evening, and submit a couple of new files for the LaTeX document template and title page logo. My limited LaTeX skills are pretty rusty, and I was confused to see a LaTeX code snippet that appeared to pull in a png image file. The doxygen manual implies that the LaTeX side can only handle eps images, but if we can avoid having to convert, and maintain, all the images into two formats, that would save us a lot of work. > I'm very short in time today, therefore only one remark: The section > names are global (you can refer to them from everywhere), thus we > should use names that can easily be made unique. I proposed and > started with using the filename part (without .dox) and an underline > as a prefix to make things unique. I agree. See below... > Before you (or anybody else) start/s more work, we should decide how > to name the sections, because otherwise, we would get difficulties > to get them unique over all files. > > > -<h3><A name="lines"> > > -Line Dashes and Thickness > > -</a></h3> > > +<A name="lines"></A> <!-- For old HTML links only ! --> > > +\subsection ssect_Lines Line Dashes and Thickness > > In this case, this could be drawing_ssect_Lines, but IMHO "ssect_" > would be redundant and could be omitted, or replaced by the section > name. I agree that, ultimately, the "ssect_" part is redundant, but in the meantime I wanted to be sure that I have a unique name without having to search through the dox every time. The goal is to get rid of the html named anchors and links to them, and then we can tidy up again. Note: I think that there is already a link conflict. The fl_frame() in the text is not converted into a link to the reference page, but fl_frame2() is, and I think this has to do with the existing explicit named "fl_frame" anchor. I only spotted this at the last moment and have not had chance to verify yet. > A short rule could be: If you convert the HTML anchors to new doxygen > \section, \subsection, or \subsubsection, use the filename part + an > underscore + the previous anchor name, and we should be unique, and > transforming the referring links would be easy. > > Does this sound reasonable? Sounds good to me, as part of the next phase. > One more to html link formatting: *if* we want to make the html links > *look* like doxygen links, we could add class="el" to the html code. > I did this in a few cases in index.dox, and in the navigation links, > where I had to use html. I think that as long as we are consistent in using 'code()' to link to the reference pages, and 'phrase' to link to the tutorial pages, we probably won't need to tweak the appearance of the links. > And the last: Instead of \ref you can also use \link <ref> Any Link > Text \endlink, if you want to "rename" the link, .e.g. > \link ssect_Complex more info here \endlink That's a good trick to know. I had missed that one. Cheers D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
