![]() ![]() This feature is currently supported for HTML and RTF only.Īn inverse include dependency graph is also generated showing for a (header) file, which other files include it.Ī graph is drawn for each documented class and struct that shows: This disables the generation of the built-in class inheritance diagrams.Īn include dependency graph is generated for each documented file that includes at least one other file. The inheritance relations with base classes. ![]() The usage relations with other structs and classes (e.g. class A has a member variable m_a of type class B, then A has an arrow to B with m_a as label). If CALL_GRAPH is set to YES, a graphical call graph is drawn for each function showing the functions that the function directly or indirectly calls (see also section \callgraph and section \hidecallgraph). ![]() If CALLER_GRAPH is set to YES, a graphical caller graph is drawn for each function showing the functions that the function is directly or indirectly called by (see also section \callergraph and section \hidecallergraph). If DIRECTORY_GRAPH is set to YES, doxygen will generate graphs that show the directory dependencies for every directory. The graph will show directories as boxes. Subdirectories are shown nested into the box of its parent directory. The depth of the graph is configured through DIR_GRAPH_MAX_DEPTH. Include dependencies between the directories are shown as arrows. Using a layout file you can determine which of the graphs are actually shown. The options DOT_GRAPH_MAX_NODES and MAX_DOT_GRAPH_DEPTH can be used to limit the size of the various graphs. (I think svg is the more interesting, because it is as lightweight as an html file and use client computer to render.The elements in the class diagrams in HTML and RTF have the following meaning:Ī yellow box indicates a class. Just create a new checkbox "DOT file" when user click on "New" and replace the action taken by the "preview" button by a request to graphviz to generate an image from a command-line. But this is an heavy and not user friendly workaround.įor implementation of such a feature, I guess that using a script like the one actually used on the wiki could be ok. If he want to edit, he can alter source and generate new the image, and then send both of them. I know, we can actually send dot source file into wiki aside with an image, and the man who want to read can just view the the image. Using DOT files will allow everyone to edit diagrams with a simple text editor, exactly like a wiki page. You could also use dia files, but in any case, you will need a software to modify them. Actually, you can only use formats not easy to alter, so, raster images (png, by example) or vector images (svg). Imagine you work on a class diagram with some other people. If the wiki were able to read such files (well, or to ask to graphviz to generate it from a stored DOT file), it could give us the possibility to use the wiki directly as a design tool. Graphviz creates raster (and vertor too if I remember correctly) images from it, and doxygen is known to use Graphviz to generate class diagrams and call graphs when it is available. In short, it is a language to create graphs from text files, like a programming language. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |