Created by the design team
Description
Related Objects
- Mentioned In
- T27033: Clean up stale remote branches
Event Timeline
After integrating the three provided style files it does not look exactly like the mockup on my system. See attached screenshot.
[6242e8]: Merge branch 'bug-18159-new-doxygen-style'
Merged commits:
2014-10-29 03:46:45 Sascha Zelzer [3ef43f]
Added new Doxygen stylesheet.
2014-10-29 03:41:26 Sascha Zelzer [446db0]
Updated doxygen conf files to version 1.8.8.
Are the tab.css and navtree.css included in the mitk_doxygen_extra.css ? They were part of the designer proposal as far as I am aware.
Also we might consider downgrading the doxygen configuration files to doxygen 1.8.7 seeing as it is the current minimum version. Alternatively we can of course up the minimum version to 1.8.8
(In reply to Caspar Jonas Goch from comment #9)
Are the tab.css and navtree.css included in the mitk_doxygen_extra.css ?
They were part of the designer proposal as far as I am aware.
Yes, they are. In fact, only the differences to the original Doxygen css files are contained in mitk_doxygen_extra.css.
Also we might consider downgrading the doxygen configuration files to
doxygen 1.8.7 seeing as it is the current minimum version. Alternatively we
can of course up the minimum version to 1.8.8
Ah, yes. Assuming that 1.8.8 did not remove major configuration options which are using, we could also just downgrade the doxgen executable version on the machine generating the documentation. I do not know if doxygen can downgrade configuration files.
As far as I can tell the difference between 1.8.7 and 1.8.8 config files (not including documentation) is:
-CLANG_ASSISTED_PARSING = NO
-CLANG_OPTIONS =
+PLANTUML_JAR_PATH =
So I guess we will be fine by using the 1.8.8 config file.
The CLANG options were removed because my doxygen executable was not built with Clang support. So there seems to be only one new option.
I downgraded the doxygen executable to 1.8.7 on the cdash client and triggered the nightly documentation build. I guess this bug can be closed?