Duncan said:
> The current drawing.dox provides a function reference/tutorial by using
> a lot of function signatures as HTML H4 headers with embedded anchor
> names that are linked to from elsewhere. For example, there are full
> HTML links to Fl_Widget::draw() that point to the named entry on the
> drawing.dox page.
>
> If we follow the doxygen approach, we would simply remove the full HTML
> links, and just leave 'Fl_Widget::draw()' and let doxygen fill in the
> details. But then we don't get what we had before. We get a nice link
Could you add the pdf/latex doc you get in a ./documentation/pdf directory in 
the svn so that we can see this alpha version and help ?
It's not a problem if it is still alpha work provided that you name it as such 
like fltk_manual-1.3-alpha1.pdf (or .tex if you don't get the pdf yet).

> How should we proceed? Keep the current in-page links and add explicit
> links at the end of the paragraph to Reference Page: Fl_Widget::draw()?
I'm generally open to initiatives that make the doxygen doc. more doxygen 
compliant.
This said, we are talking about our custom pages so I need to 'see' what you 
are talking about to get a more precise idea before we try to find the best 
compromise.

Thanks,
Fabien

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to