> BTW, while you're looking at this link aspect, it would be nice if we > could also cross-reference the custom pages with the module pages, like: > the Fl event functions discussed in our dox custom page should link to > the event module in Modules because it's more detailed and vice-versa > because it's good for the user to get the essentials of events in the > custom page (which BTW also deals with related enums) while having a > look to the Modules event functions.
Yes, this is the main reason why I'm bringing this up. At the moment a lot of the information that should be in the class/function reference pages has been 'commandeered' by the *.dox tutorials pages. There needs to be appropriate reference info on the reference pages, and a suitable amount of description or discussion text in the tutorial pages, with the appropriate links between the two. We now have the reference info in the 'wrong' place, and if we replace the hand crafted HTML anchors in the tutorial pages, the natural doxygen links for Fl_Widget::draw() for example will point from the tutorial pages to the [almost empty] reference pages. So somehow we need to be able to maintain, and also distinguish between, the in-page links in the tutorial pages with the links to the reference. I don't think I'm explaining this very well, so it's probably best to wait for the drawing.dox commit later so you can see what I'm on about. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
