Me: >> The quick guide (and I can commit the changes later this evening) >> 1. doxygen -w html header.html footer.html customdoxygen.css >> 2. copy customdoxygen.css to documentation/src >> 3. in Doxyfile, set HTML_STYLESHEET to customdoxygen.css >> 4. in customdoxygen.css, change fontsize for h2 and h3
Albrecht: > Okay, that looks good! Although I'm not sure if the generated .css > file might change with different doxygen versions. We would have to > check this from time to time. All we can do is generate a new customdoxygen.css from time to time using the command above, and check it against the version in the repo. Although we could save a 'raw' version in the repo as well to check against, and even script/automate such a check, it's not worth it IMHO. > And, maybe more important, if developers and users would use different > doxygen versions, what would happen if someone uses a newer doxygen > version, and the generated output uses other (missing) tags/classes? So far doxygen has proven to be very backward compatible, and will use an old version Doxyfile with a new doxygen. I'm now using doxygen-1.5.9. As long as nobody regenerates the Doxyfile from scratch with a bleeding edge version, we should be OK. Cheers D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
