![]() Doxygen will list the pieces in the order in which they appear in the XML file. ![]() Some pieces can appear in each type of page, others are specific for a certain type of page. The directory section represents the layout of all pages generated for documented directories.Įach XML tag within one of the above page sections represents a certain piece of information.The group section represents the layout of all pages generated for documented groups (or modules).The file section represents the layout of all pages generated for documented files.The namespace section represents the layout of all pages generated for documented namespaces (and also Java packages).The class section represents the layout of all pages generated for documented classes, structs, unions, and interfaces.The sections after navindex represent the layout of the different pages generated by doxygen: Only a fixed set of types are supported, each representing a link to a specific index. Do not change the value of the type attribute however. You can reorder the tabs by moving the tab tags in the XML file within the navindex section and even change the tree structure. If the title field is the empty string (the default) then doxygen will fill in an appropriate title. You can also override the default title of a tab by specifying it as the value of the title attribute. You can hide tabs by setting the visible attribute to no. Each tab is represented by a tab tag in the XML file. The first section, enclosed by navindex tags represents the layout of the navigation tabs displayed at the top of each HTML page. The root tag of the XML is doxygenlayout, it has an attribute named version, which will be used in the future to cope with changes that are not backward compatible. The default layout can be generated by doxygen using the following command: The solution doxygen provides is a layout file, which you can modify and doxygen will use to control what information is presented, in which order, and to some extent also how information is presented. A different style sheet or custom headers and footers do not help in such case. In some cases you may want to change the way the output is structured. If you use images or other external content in a custom header you need to make sure these end up in the HTML output directory yourself, for instance by writing a script that runs doxygen can then copies the images to the output. Note: You should not put the style sheet in the HTML output directory. This again, is not ideal however, your maintenance process now resides in a single page order file (instead of touching one (1) or more Doxygen configuration files).See the documentation of the HTML_HEADER tag for more information about the possible meta commands. For instance: INPUT += PageOrder.doxĪnd you add all the page references in a PageOrder.dox file: \page developers Developers What I found is that if you wish to maintain using directory paths in your Doxygen configuration file, you can create an 'page order' file to parse first before any other content. For instance, you can achieve the desired order by specifying your files manually such as: INPUT = Developers.dox \ ![]() Just as mentions, the current way to ensure a desired order of pages in Doxygen is to ensure the page conditions (\page) are parsed in the same order. After some investigation, it seems Doxygen currently does not support the ordering of pages in a custom (or any) fashion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |