> I did some tests yesterday, and I found out that the generated code > and the default .css file differ substantially between doxygen > versions (you wrote that your version is 1.5.9): > > $ doxygen --version > 1.5.5 > $ doxygen -w html h.htm f.htm c.css > $ diff -ubw c.css src/html_stylesheet.css | wc -l > 711 > > There are lots of new or changed css classes/attributes in the new > file. My suspicion is that we can use a new .css file with older > doxygen versions, but not vice versa, because the generated html > code wouldn't find the new css definitions in the old .css file.
Oops! That's an oversight on my part. It didn't occur to me that different versions of doxygen would generate different css files. I was in too much of a rush to commit something to show everyone. > My current conclusion is that we can do the following: > > (1) leave the Doxygen file at 1.5.5 for now > (2) use 1.5.9 for generating the web docs (html and pdf) > > We should then "fix" this at 1.5.9 for a while, so that the core > developers are in sync with their versions, and thus updating the > web docs wouldn't have too many diffs. BTW.: the current web docs > are created with 1.5.7 (by Fabien). > > Maybe we should all test and see if we can all upgrade to 1.5.9, > or only those who have 1.5.9 should update the web docs. I think that for the moment we should keep it simple and try to avoid surprises. Therefore we should keep the Doxyfile generated from 1.5.5 as this will work with later versions. 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. And it would be easiest if Fabien continues to update the web docs, whenever there are major changes. I wouldn't expect any until 1.3.0 is released, so that shouldn't involve much work. We should re-evaluate doxygen version and web page update system when 1.3.0 is released. What about a Comments version for feedback? Cheers D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
