Me: > > Similarly, a 1.5.5 user should > > regenerate the stylesheet .css file, change the h2 and h3 fontsizes > > and add your "code" element definition, and check the output is OK.
Albrecht: > This would need documentation, and it would be at least "surprising" > for end users if the doxygen docs can't be generated out of the box. > But it would be a possible way to let users with older versions > generate local docs, if they can't upgrade to a newer version. > Currently I don't think that we can automate this with make :-( Ah, I wasn't as clear as I thought. When I said a "1.5.5 user" I meant a "developer who uses 1.5.5", not a general user. We [developers] need to provide a 1.5.5 .css file in the source tree once only. End users with even older versions of doxygen will still be out of luck though, but we can't cater for everyone - there has to be some cutoff point. I noticed your changes for the Comments. Keep up the good work. But I think we need a more proactive approach to any comments. We [developers] should review comments, then update the docs of STRs, and provide a reply comment on what has been done. But we probably still need to discuss this further in another thread. Cheers D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
