ViewVC Help
View File | Revision Log | Show Annotations | View Changeset | Root Listing
root/OpenMD/branches/development/doc/Doxyfile.in
(Generate patch)

Comparing branches/development/doc/Doxyfile.in (file contents):
Revision 1807 by gezelter, Tue Sep 27 14:48:28 2011 UTC vs.
Revision 1808 by gezelter, Mon Oct 22 20:42:10 2012 UTC

# Line 1 | Line 1
1 < # Doxyfile 1.6.3
1 > # Doxyfile 1.8.1.1
2  
3   # This file describes the settings to be used by the documentation system
4 < # doxygen (www.doxygen.org) for a project
4 > # doxygen (www.doxygen.org) for a project.
5   #
6 < # All text after a hash (#) is considered a comment and will be ignored
6 > # All text after a hash (#) is considered a comment and will be ignored.
7   # The format is:
8   #       TAG = value [value, ...]
9   # For lists items can also be appended using:
10   #       TAG += value [value, ...]
11 < # Values that contain spaces should be placed between quotes (" ")
11 > # Values that contain spaces should be placed between quotes (" ").
12  
13   #---------------------------------------------------------------------------
14   # Project related configuration options
# Line 22 | Line 22 | DOXYFILE_ENCODING      = UTF-8
22  
23   DOXYFILE_ENCODING      = UTF-8
24  
25 < # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26 < # by quotes) that should identify the project.
25 > # The PROJECT_NAME tag is a single word (or sequence of words) that should
26 > # identify the project. Note that if you do not use Doxywizard you need
27 > # to put quotes around the project name if it contains spaces.
28  
29   PROJECT_NAME           = OpenMD
30  
# Line 33 | Line 34 | PROJECT_NUMBER         = 2.0
34  
35   PROJECT_NUMBER         = 2.0
36  
37 + # Using the PROJECT_BRIEF tag one can provide an optional one line description
38 + # for a project that appears at the top of each page and should give viewer
39 + # a quick idea about the purpose of the project. Keep the description short.
40 +
41 + PROJECT_BRIEF          = "Molecular Dynamics in the Open"
42 +
43 + # With the PROJECT_LOGO tag one can specify an logo or icon that is
44 + # included in the documentation. The maximum height of the logo should not
45 + # exceed 55 pixels and the maximum width should not exceed 200 pixels.
46 + # Doxygen will copy the logo to the output directory.
47 +
48 + PROJECT_LOGO           =
49 +
50   # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
51   # base path where the generated documentation will be put.
52   # If a relative path is entered, it will be relative to the location
# Line 57 | Line 71 | CREATE_SUBDIRS         = NO
71   # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
72   # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
73   # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
74 < # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
74 > # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
75   # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
76  
77   OUTPUT_LANGUAGE        = English
# Line 126 | Line 140 | STRIP_FROM_INC_PATH    =
140   STRIP_FROM_INC_PATH    =
141  
142   # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
143 < # (but less readable) file names. This can be useful is your file systems
143 > # (but less readable) file names. This can be useful if your file system
144   # doesn't support long names like on DOS, Mac, or CD-ROM.
145  
146   SHORT_NAMES            = NO
# Line 181 | Line 195 | ALIASES                =
195  
196   ALIASES                =
197  
198 + # This tag can be used to specify a number of word-keyword mappings (TCL only).
199 + # A mapping has the form "name=value". For example adding
200 + # "class=itcl::class" will allow you to use the command class in the
201 + # itcl::class meaning.
202 +
203 + TCL_SUBST              =
204 +
205   # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
206   # sources only. Doxygen will then generate output that is more tailored for C.
207   # For instance, some of the names that are used will be different. The list
# Line 207 | Line 228 | OPTIMIZE_OUTPUT_VHDL   = NO
228  
229   OPTIMIZE_OUTPUT_VHDL   = NO
230  
231 < # Doxygen selects the parser to use depending on the extension of the files it parses.
232 < # With this tag you can assign which parser to use for a given extension.
233 < # Doxygen has a built-in mapping, but you can override or extend it using this tag.
234 < # The format is ext=language, where ext is a file extension, and language is one of
235 < # the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,
236 < # Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat
237 < # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
238 < # use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
231 > # Doxygen selects the parser to use depending on the extension of the files it
232 > # parses. With this tag you can assign which parser to use for a given extension.
233 > # Doxygen has a built-in mapping, but you can override or extend it using this
234 > # tag. The format is ext=language, where ext is a file extension, and language
235 > # is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
236 > # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
237 > # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
238 > # (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
239 > # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
240  
241 < EXTENSION_MAPPING      = F90=Fortran cpp=C++ hpp=C++ c=C h=C
241 > EXTENSION_MAPPING      = F90=Fortran \
242 >                         cpp=C++ \
243 >                         hpp=C++ \
244 >                         c=C \
245 >                         h=C
246  
247 + # If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all
248 + # comments according to the Markdown format, which allows for more readable
249 + # documentation. See http://daringfireball.net/projects/markdown/ for details.
250 + # The output of markdown processing is further processed by doxygen, so you
251 + # can mix doxygen, HTML, and XML commands with Markdown formatting.
252 + # Disable only in case of backward compatibilities issues.
253 +
254 + MARKDOWN_SUPPORT       = YES
255 +
256   # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
257   # to include (a tag file for) the STL sources as input, then you should
258   # set this tag to YES in order to let doxygen match functions declarations and
259   # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
260 < # func(std::string) {}). This also make the inheritance and collaboration
260 > # func(std::string) {}). This also makes the inheritance and collaboration
261   # diagrams that involve STL classes more complete and accurate.
262  
263   BUILTIN_STL_SUPPORT    = YES
# Line 240 | Line 275 | SIP_SUPPORT            = NO
275  
276   # For Microsoft's IDL there are propget and propput attributes to indicate getter
277   # and setter methods for a property. Setting this option to YES (the default)
278 < # will make doxygen to replace the get and set methods by a property in the
278 > # will make doxygen replace the get and set methods by a property in the
279   # documentation. This will only work if the methods are indeed getting or
280   # setting a simple type. If this is not the case, or you want to show the
281   # methods anyway, you should set this option to NO.
# Line 261 | Line 296 | SUBGROUPING            = YES
296   # the \nosubgrouping command.
297  
298   SUBGROUPING            = YES
299 +
300 + # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
301 + # unions are shown inside the group in which they are included (e.g. using
302 + # @ingroup) instead of on a separate page (for HTML and Man pages) or
303 + # section (for LaTeX and RTF).
304  
305 + INLINE_GROUPED_CLASSES = NO
306 +
307 + # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
308 + # unions with only public data fields will be shown inline in the documentation
309 + # of the scope in which they are defined (i.e. file, namespace, or group
310 + # documentation), provided this scope is documented. If set to NO (the default),
311 + # structs, classes, and unions are shown on a separate page (for HTML and Man
312 + # pages) or section (for LaTeX and RTF).
313 +
314 + INLINE_SIMPLE_STRUCTS  = NO
315 +
316   # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
317   # is documented as struct, union, or enum with the name of the typedef. So
318   # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
# Line 278 | Line 329 | TYPEDEF_HIDES_STRUCT   = NO
329   # For small to medium size projects (<1000 input files) the default value is
330   # probably good enough. For larger projects a too small cache size can cause
331   # doxygen to be busy swapping symbols to and from disk most of the time
332 < # causing a significant performance penality.
332 > # causing a significant performance penalty.
333   # If the system has enough physical memory increasing the cache will improve the
334   # performance by keeping more symbols in memory. Note that the value works on
335 < # a logarithmic scale so increasing the size by one will rougly double the
335 > # a logarithmic scale so increasing the size by one will roughly double the
336   # memory usage. The cache size is given by this formula:
337   # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
338 < # corresponding to a cache size of 2^16 = 65536 symbols
338 > # corresponding to a cache size of 2^16 = 65536 symbols.
339  
340   SYMBOL_CACHE_SIZE      = 0
341  
342 + # Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be
343 + # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given
344 + # their name and scope. Since this can be an expensive process and often the
345 + # same symbol appear multiple times in the code, doxygen keeps a cache of
346 + # pre-resolved symbols. If the cache is too small doxygen will become slower.
347 + # If the cache is too large, memory is wasted. The cache size is given by this
348 + # formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,
349 + # corresponding to a cache size of 2^16 = 65536 symbols.
350 +
351 + LOOKUP_CACHE_SIZE      = 0
352 +
353   #---------------------------------------------------------------------------
354   # Build related configuration options
355   #---------------------------------------------------------------------------
# Line 304 | Line 366 | EXTRACT_PRIVATE        = YES
366  
367   EXTRACT_PRIVATE        = YES
368  
369 + # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation.
370 +
371 + EXTRACT_PACKAGE        = NO
372 +
373   # If the EXTRACT_STATIC tag is set to YES all static members of a file
374   # will be included in the documentation.
375  
# Line 326 | Line 392 | EXTRACT_LOCAL_METHODS  = YES
392   # extracted and appear in the documentation as a namespace called
393   # 'anonymous_namespace{file}', where file will be replaced with the base
394   # name of the file that contains the anonymous namespace. By default
395 < # anonymous namespace are hidden.
395 > # anonymous namespaces are hidden.
396  
397   EXTRACT_ANON_NSPACES   = YES
398  
# Line 411 | Line 477 | SORT_BRIEF_DOCS        = NO
477  
478   SORT_BRIEF_DOCS        = NO
479  
480 < # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
480 > # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
481 > # will sort the (brief and detailed) documentation of class members so that
482 > # constructors and destructors are listed first. If set to NO (the default)
483 > # the constructors will appear in the respective orders defined by
484 > # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
485 > # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
486 > # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
487  
488   SORT_MEMBERS_CTORS_1ST = NO
489  
# Line 431 | Line 503 | SORT_BY_SCOPE_NAME     = NO
503  
504   SORT_BY_SCOPE_NAME     = NO
505  
506 + # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
507 + # do proper type resolution of all parameters of a function it will reject a
508 + # match between the prototype and the implementation of a member function even
509 + # if there is only one candidate or it is obvious which candidate to choose
510 + # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
511 + # will still accept a match between prototype and implementation in such cases.
512 +
513 + STRICT_PROTO_MATCHING  = NO
514 +
515   # The GENERATE_TODOLIST tag can be used to enable (YES) or
516   # disable (NO) the todo list. This list is created by putting \todo
517   # commands in the documentation.
# Line 461 | Line 542 | ENABLED_SECTIONS       =
542   ENABLED_SECTIONS       =
543  
544   # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
545 < # the initial value of a variable or define consists of for it to appear in
545 > # the initial value of a variable or macro consists of for it to appear in
546   # the documentation. If the initializer consists of more lines than specified
547   # here it will be hidden. Use a value of 0 to hide initializers completely.
548 < # The appearance of the initializer of individual variables and defines in the
548 > # The appearance of the initializer of individual variables and macros in the
549   # documentation can be controlled using \showinitializer or \hideinitializer
550   # command in the documentation regardless of this setting.
551  
# Line 476 | Line 557 | SHOW_USED_FILES        = YES
557  
558   SHOW_USED_FILES        = YES
559  
479 – # If the sources in your project are distributed over multiple directories
480 – # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
481 – # in the documentation. The default is NO.
482 –
483 – SHOW_DIRECTORIES       = NO
484 –
560   # Set the SHOW_FILES tag to NO to disable the generation of the Files page.
561   # This will remove the Files entry from the Quick Index and from the
562   # Folder Tree View (if specified). The default is YES.
# Line 505 | Line 580 | FILE_VERSION_FILTER    =
580  
581   FILE_VERSION_FILTER    =
582  
583 < # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
584 < # doxygen. The layout file controls the global structure of the generated output files
585 < # in an output format independent way. The create the layout file that represents
586 < # doxygen's defaults, run doxygen with the -l option. You can optionally specify a
587 < # file name after the option, if omitted DoxygenLayout.xml will be used as the name
588 < # of the layout file.
583 > # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
584 > # by doxygen. The layout file controls the global structure of the generated
585 > # output files in an output format independent way. To create the layout file
586 > # that represents doxygen's defaults, run doxygen with the -l option.
587 > # You can optionally specify a file name after the option, if omitted
588 > # DoxygenLayout.xml will be used as the name of the layout file.
589  
590   LAYOUT_FILE            =
591  
592 + # The CITE_BIB_FILES tag can be used to specify one or more bib files
593 + # containing the references data. This must be a list of .bib files. The
594 + # .bib extension is automatically appended if omitted. Using this command
595 + # requires the bibtex tool to be installed. See also
596 + # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
597 + # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this
598 + # feature you need bibtex and perl available in the search path.
599 +
600 + CITE_BIB_FILES         =
601 +
602   #---------------------------------------------------------------------------
603   # configuration options related to warning and progress messages
604   #---------------------------------------------------------------------------
# Line 542 | Line 627 | WARN_IF_DOC_ERROR      = YES
627  
628   WARN_IF_DOC_ERROR      = YES
629  
630 < # This WARN_NO_PARAMDOC option can be abled to get warnings for
630 > # The WARN_NO_PARAMDOC option can be enabled to get warnings for
631   # functions that are documented, but have no documentation for their parameters
632   # or return value. If set to NO (the default) doxygen will only warn about
633   # wrong or incomplete parameter documentation, but not about the absence of
# Line 588 | Line 673 | INPUT_ENCODING         = UTF-8
673   # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
674   # and *.h) to filter out the source-files in the directories. If left
675   # blank the following patterns are tested:
676 < # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
677 < # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
676 > # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
677 > # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
678 > # *.f90 *.f *.for *.vhd *.vhdl
679 >
680   FILE_PATTERNS          = *.c \
681                           *.cc \
682                           *.cxx \
# Line 628 | Line 715 | FILE_PATTERNS          = *.c \
715                           *.PHP3 \
716                           *.M \
717                           *.MM \
718 <                         *.f90 *.f95 *.f77 *.ftn *.for *.F90 *.F95 \
719 <                         *.F77 *.FTN *.FOR *.F
718 >                         *.f90 \
719 >                         *.f95 \
720 >                         *.f77 \
721 >                         *.ftn \
722 >                         *.for \
723 >                         *.F90 \
724 >                         *.F95 \
725 >                         *.F77 \
726 >                         *.FTN \
727 >                         *.FOR \
728 >                         *.F
729  
730   # The RECURSIVE tag can be used to turn specify whether or not subdirectories
731   # should be searched for input files as well. Possible values are YES and NO.
# Line 637 | Line 733 | RECURSIVE              = YES
733  
734   RECURSIVE              = YES
735  
736 < # The EXCLUDE tag can be used to specify files and/or directories that should
736 > # The EXCLUDE tag can be used to specify files and/or directories that should be
737   # excluded from the INPUT source files. This way you can easily exclude a
738   # subdirectory from a directory tree whose root is specified with the INPUT tag.
739 + # Note that relative paths are relative to the directory from which doxygen is
740 + # run.
741  
742 < EXCLUDE                = src/UseTheForce/DarkSide/suttonchen.F90
742 > EXCLUDE                =
743  
744 < # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
745 < # directories that are symbolic links (a Unix filesystem feature) are excluded
744 > # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
745 > # directories that are symbolic links (a Unix file system feature) are excluded
746   # from the input.
747  
748   EXCLUDE_SYMLINKS       = NO
# Line 708 | Line 806 | INPUT_FILTER           =
806   # filter if there is a match.
807   # The filters are a list of the form:
808   # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
809 < # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
810 < # is applied to all files.
809 > # info on how filters are used. If FILTER_PATTERNS is empty or if
810 > # non of the patterns match the file name, INPUT_FILTER is applied.
811  
812 < FILTER_PATTERNS        =
812 > FILTER_PATTERNS        =
813  
814   # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
815   # INPUT_FILTER) will be used to filter the input files when producing source
# Line 719 | Line 817 | FILTER_SOURCE_FILES    = NO
817  
818   FILTER_SOURCE_FILES    = NO
819  
820 + # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
821 + # pattern. A pattern will override the setting for FILTER_PATTERN (if any)
822 + # and it is also possible to disable source filtering for a specific pattern
823 + # using *.ext= (so without naming a filter). This option only has effect when
824 + # FILTER_SOURCE_FILES is enabled.
825 +
826 + FILTER_SOURCE_PATTERNS =
827 +
828   #---------------------------------------------------------------------------
829   # configuration options related to source browsing
830   #---------------------------------------------------------------------------
# Line 737 | Line 843 | INLINE_SOURCES         = NO
843  
844   # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
845   # doxygen to hide any special comment blocks from generated source code
846 < # fragments. Normal C and C++ comments will always remain visible.
846 > # fragments. Normal C, C++ and Fortran comments will always remain visible.
847  
848   STRIP_CODE_COMMENTS    = YES
849  
# Line 821 | Line 927 | HTML_FILE_EXTENSION    = .html
927  
928   # The HTML_HEADER tag can be used to specify a personal HTML header for
929   # each generated HTML page. If it is left blank doxygen will generate a
930 < # standard header.
930 > # standard header. Note that when using a custom header you are responsible
931 > #  for the proper inclusion of any scripts and style sheets that doxygen
932 > # needs, which is dependent on the configuration options used.
933 > # It is advised to generate a default header using "doxygen -w html
934 > # header.html footer.html stylesheet.css YourConfigFile" and then modify
935 > # that header. Note that the header is subject to change so you typically
936 > # have to redo this when upgrading to a newer version of doxygen or when
937 > # changing the value of configuration settings such as GENERATE_TREEVIEW!
938  
939   HTML_HEADER            =
940  
# Line 836 | Line 949 | HTML_FOOTER            =
949   # fine-tune the look of the HTML output. If the tag is left blank doxygen
950   # will generate a default style sheet. Note that doxygen will try to copy
951   # the style sheet file to the HTML output directory, so don't put your own
952 < # stylesheet in the HTML output directory as well, or it will be erased!
952 > # style sheet in the HTML output directory as well, or it will be erased!
953  
954   HTML_STYLESHEET        =
955  
956 + # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
957 + # other source files which should be copied to the HTML output directory. Note
958 + # that these files will be copied to the base HTML output directory. Use the
959 + # $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
960 + # files. In the HTML_STYLESHEET file, use the file name only. Also note that
961 + # the files will be copied as-is; there are no commands or markers available.
962 +
963 + HTML_EXTRA_FILES       =
964 +
965 + # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
966 + # Doxygen will adjust the colors in the style sheet and background images
967 + # according to this color. Hue is specified as an angle on a colorwheel,
968 + # see http://en.wikipedia.org/wiki/Hue for more information.
969 + # For instance the value 0 represents red, 60 is yellow, 120 is green,
970 + # 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
971 + # The allowed range is 0 to 359.
972 +
973 + HTML_COLORSTYLE_HUE    = 220
974 +
975 + # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
976 + # the colors in the HTML output. For a value of 0 the output will use
977 + # grayscales only. A value of 255 will produce the most vivid colors.
978 +
979 + HTML_COLORSTYLE_SAT    = 100
980 +
981 + # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
982 + # the luminance component of the colors in the HTML output. Values below
983 + # 100 gradually make the output lighter, whereas values above 100 make
984 + # the output darker. The value divided by 100 is the actual gamma applied,
985 + # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
986 + # and 100 does not change the gamma.
987 +
988 + HTML_COLORSTYLE_GAMMA  = 80
989 +
990   # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
991   # page will contain the date and time when the page was generated. Setting
992   # this to NO can help when comparing the output of multiple runs.
993  
994   HTML_TIMESTAMP         = YES
995  
849 – # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
850 – # files or namespaces will be aligned in HTML using tables. If set to
851 – # NO a bullet list will be used.
852 –
853 – HTML_ALIGN_MEMBERS     = YES
854 –
996   # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
997   # documentation will contain sections that can be hidden and shown after the
998 < # page has loaded. For this to work a browser that supports
858 < # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
859 < # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
998 > # page has loaded.
999  
1000   HTML_DYNAMIC_SECTIONS  = NO
1001  
1002 + # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of
1003 + # entries shown in the various tree structured indices initially; the user
1004 + # can expand and collapse entries dynamically later on. Doxygen will expand
1005 + # the tree to such a level that at most the specified number of entries are
1006 + # visible (unless a fully collapsed tree already exceeds this amount).
1007 + # So setting the number of entries 1 will produce a full collapsed tree by
1008 + # default. 0 is a special value representing an infinite number of entries
1009 + # and will result in a full expanded tree by default.
1010 +
1011 + HTML_INDEX_NUM_ENTRIES = 100
1012 +
1013   # If the GENERATE_DOCSET tag is set to YES, additional index files
1014   # will be generated that can be used as input for Apple's Xcode 3
1015   # integrated development environment, introduced with OSX 10.5 (Leopard).
# Line 868 | Line 1018 | HTML_DYNAMIC_SECTIONS  = NO
1018   # directory and running "make install" will install the docset in
1019   # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
1020   # it at startup.
1021 < # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
1021 > # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1022 > # for more information.
1023  
1024   GENERATE_DOCSET        = NO
1025  
# Line 884 | Line 1035 | DOCSET_FEEDNAME        = "Doxygen generated docs"
1035   # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
1036   # will append .docset to the name.
1037  
1038 < DOCSET_BUNDLE_ID       = org.doxygen.Project
1038 > DOCSET_BUNDLE_ID       = org.openscience.OpenMD
1039  
1040 + # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
1041 + # the documentation publisher. This should be a reverse domain-name style
1042 + # string, e.g. com.mycompany.MyDocSet.documentation.
1043 +
1044 + DOCSET_PUBLISHER_ID    = org.openscience.OpenMD.documentation
1045 +
1046 + # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
1047 +
1048 + DOCSET_PUBLISHER_NAME  = Publisher
1049 +
1050   # If the GENERATE_HTMLHELP tag is set to YES, additional index files
1051   # will be generated that can be used as input for tools like the
1052   # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
# Line 930 | Line 1091 | TOC_EXPAND             = NO
1091  
1092   TOC_EXPAND             = NO
1093  
1094 < # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
1095 < # are set, an additional index file will be generated that can be used as input for
1096 < # Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
1097 < # HTML documentation.
1094 > # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1095 > # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
1096 > # that can be used as input for Qt's qhelpgenerator to generate a
1097 > # Qt Compressed Help (.qch) of the generated HTML documentation.
1098  
1099   GENERATE_QHP           = NO
1100  
# Line 947 | Line 1108 | QCH_FILE               =
1108   # Qt Help Project output. For more information please see
1109   # http://doc.trolltech.com/qthelpproject.html#namespace
1110  
1111 < QHP_NAMESPACE          = org.doxygen.Project
1111 > QHP_NAMESPACE          = org.openscience.OpenMD
1112  
1113   # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
1114   # Qt Help Project output. For more information please see
# Line 955 | Line 1116 | QHP_VIRTUAL_FOLDER     = doc
1116  
1117   QHP_VIRTUAL_FOLDER     = doc
1118  
1119 < # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
1120 < # For more information please see
1119 > # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
1120 > # add. For more information please see
1121   # http://doc.trolltech.com/qthelpproject.html#custom-filters
1122  
1123   QHP_CUST_FILTER_NAME   =
1124  
1125 < # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
1126 < # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
1125 > # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
1126 > # custom filter to add. For more information please see
1127 > # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
1128 > # Qt Help Project / Custom Filters</a>.
1129  
1130   QHP_CUST_FILTER_ATTRS  =
1131  
1132 < # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
1132 > # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1133 > # project's
1134   # filter section matches.
1135 < # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
1135 > # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1136 > # Qt Help Project / Filter Attributes</a>.
1137  
1138   QHP_SECT_FILTER_ATTRS  =
1139  
# Line 981 | Line 1146 | QHG_LOCATION           =
1146  
1147   # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
1148   #  will be generated, which together with the HTML files, form an Eclipse help
1149 < #  plugin. To install this plugin and make it available under the help contents
1149 > # plugin. To install this plugin and make it available under the help contents
1150   # menu in Eclipse, the contents of the directory containing the HTML and XML
1151   # files needs to be copied into the plugins directory of eclipse. The name of
1152   # the directory within the plugins directory should be the same as
1153 < # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before the help appears.
1153 > # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
1154 > # the help appears.
1155  
1156   GENERATE_ECLIPSEHELP   = NO
1157  
# Line 993 | Line 1159 | GENERATE_ECLIPSEHELP   = NO
1159   # the directory name containing the HTML and XML files should also have
1160   # this name.
1161  
1162 < ECLIPSE_DOC_ID         = org.doxygen.Project
1162 > ECLIPSE_DOC_ID         = org.openscience.OpenMD
1163  
1164 < # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1165 < # top of each HTML page. The value NO (the default) enables the index and
1166 < # the value YES disables it.
1164 > # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)
1165 > # at top of each HTML page. The value NO (the default) enables the index and
1166 > # the value YES disables it. Since the tabs have the same information as the
1167 > # navigation tree you can set this option to NO if you already set
1168 > # GENERATE_TREEVIEW to YES.
1169  
1170   DISABLE_INDEX          = NO
1171  
1004 – # This tag can be used to set the number of enum values (range [1..20])
1005 – # that doxygen will group on one line in the generated HTML documentation.
1006 –
1007 – ENUM_VALUES_PER_LINE   = 4
1008 –
1172   # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1173   # structure should be generated to display hierarchical information.
1174   # If the tag value is set to YES, a side panel will be generated
# Line 1013 | Line 1176 | ENUM_VALUES_PER_LINE   = 4
1176   # is generated for HTML Help). For this to work a browser that supports
1177   # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
1178   # Windows users are probably better off using the HTML help feature.
1179 + # Since the tree basically has the same information as the tab index you
1180 + # could consider to set DISABLE_INDEX to NO when enabling this option.
1181  
1182 < GENERATE_TREEVIEW      = NO
1182 > GENERATE_TREEVIEW      = YES
1183  
1184 < # By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1185 < # and Class Hierarchy pages using a tree view instead of an ordered list.
1184 > # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
1185 > # (range [0,1..20]) that doxygen will group on one line in the generated HTML
1186 > # documentation. Note that a value of 0 will completely suppress the enum
1187 > # values from appearing in the overview section.
1188  
1189 < USE_INLINE_TREES       = NO
1189 > ENUM_VALUES_PER_LINE   = 4
1190  
1191   # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1192   # used to set the initial width (in pixels) of the frame in which the tree
# Line 1027 | Line 1194 | TREEVIEW_WIDTH         = 250
1194  
1195   TREEVIEW_WIDTH         = 250
1196  
1197 + # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1198 + # links to external symbols imported via tag files in a separate window.
1199 +
1200 + EXT_LINKS_IN_WINDOW    = NO
1201 +
1202   # Use this tag to change the font size of Latex formulas included
1203   # as images in the HTML documentation. The default is 10. Note that
1204   # when you change the font size after a successful doxygen run you need
# Line 1035 | Line 1207 | FORMULA_FONTSIZE       = 10
1207  
1208   FORMULA_FONTSIZE       = 10
1209  
1210 < # When the SEARCHENGINE tag is enabled doxygen will generate a search box for the HTML output. The underlying search engine uses javascript
1211 < # and DHTML and should work on any modern browser. Note that when using HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) there is already a search function so this one should
1210 > # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1211 > # generated for formulas are transparent PNGs. Transparent PNGs are
1212 > # not supported properly for IE 6.0, but are supported on all modern browsers.
1213 > # Note that when changing this option you need to delete any form_*.png files
1214 > # in the HTML output before the changes have effect.
1215 >
1216 > FORMULA_TRANSPARENT    = YES
1217 >
1218 > # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
1219 > # (see http://www.mathjax.org) which uses client side Javascript for the
1220 > # rendering instead of using prerendered bitmaps. Use this if you do not
1221 > # have LaTeX installed or if you want to formulas look prettier in the HTML
1222 > # output. When enabled you may also need to install MathJax separately and
1223 > # configure the path to it using the MATHJAX_RELPATH option.
1224 >
1225 > USE_MATHJAX            = NO
1226 >
1227 > # When MathJax is enabled you need to specify the location relative to the
1228 > # HTML output directory using the MATHJAX_RELPATH option. The destination
1229 > # directory should contain the MathJax.js script. For instance, if the mathjax
1230 > # directory is located at the same level as the HTML output directory, then
1231 > # MATHJAX_RELPATH should be ../mathjax. The default value points to
1232 > # the MathJax Content Delivery Network so you can quickly see the result without
1233 > # installing MathJax.
1234 > # However, it is strongly recommended to install a local
1235 > # copy of MathJax from http://www.mathjax.org before deployment.
1236 >
1237 > MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest
1238 >
1239 > # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
1240 > # names that should be enabled during MathJax rendering.
1241 >
1242 > MATHJAX_EXTENSIONS     =
1243 >
1244 > # When the SEARCHENGINE tag is enabled doxygen will generate a search box
1245 > # for the HTML output. The underlying search engine uses javascript
1246 > # and DHTML and should work on any modern browser. Note that when using
1247 > # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
1248 > # (GENERATE_DOCSET) there is already a search function so this one should
1249   # typically be disabled. For large projects the javascript based search engine
1250   # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1251  
1252   SEARCHENGINE           = YES
1253  
1254 < # When the SERVER_BASED_SEARCH tag is enabled the search engine will be implemented using a PHP enabled web server instead of at the web client using Javascript. Doxygen will generate the search PHP script and index
1255 < # file to put on the web server. The advantage of the server based approach is that it scales better to large projects and allows full text search. The disadvances is that it is more difficult to setup
1254 > # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1255 > # implemented using a PHP enabled web server instead of at the web client
1256 > # using Javascript. Doxygen will generate the search PHP script and index
1257 > # file to put on the web server. The advantage of the server
1258 > # based approach is that it scales better to large projects and allows
1259 > # full text search. The disadvantages are that it is more difficult to setup
1260   # and does not have live searching capabilities.
1261  
1262   SERVER_BASED_SEARCH    = NO
# Line 1084 | Line 1297 | COMPACT_LATEX          = NO
1297   COMPACT_LATEX          = NO
1298  
1299   # The PAPER_TYPE tag can be used to set the paper type that is used
1300 < # by the printer. Possible values are: a4, a4wide, letter, legal and
1300 > # by the printer. Possible values are: a4, letter, legal and
1301   # executive. If left blank a4wide will be used.
1302  
1303 < PAPER_TYPE             = a4wide
1303 > PAPER_TYPE             = letter
1304  
1305   # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1306   # packages that should be included in the LaTeX output.
# Line 1100 | Line 1313 | LATEX_HEADER           =
1313   # standard header. Notice: only use this tag if you know what you are doing!
1314  
1315   LATEX_HEADER           =
1316 +
1317 + # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
1318 + # the generated latex document. The footer should contain everything after
1319 + # the last chapter. If it is left blank doxygen will generate a
1320 + # standard footer. Notice: only use this tag if you know what you are doing!
1321  
1322 + LATEX_FOOTER           =
1323 +
1324   # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1325   # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1326   # contain links (just like the HTML output) instead of page references
# Line 1127 | Line 1347 | LATEX_HIDE_INDICES     = NO
1347  
1348   LATEX_HIDE_INDICES     = NO
1349  
1350 < # If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.
1350 > # If LATEX_SOURCE_CODE is set to YES then doxygen will include
1351 > # source code with syntax highlighting in the LaTeX output.
1352 > # Note that which sources are shown also depends on other settings
1353 > # such as SOURCE_BROWSER.
1354  
1355   LATEX_SOURCE_CODE      = NO
1356  
1357 + # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1358 + # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
1359 + # http://en.wikipedia.org/wiki/BibTeX for more info.
1360 +
1361 + LATEX_BIB_STYLE        = plain
1362 +
1363   #---------------------------------------------------------------------------
1364   # configuration options related to the RTF output
1365   #---------------------------------------------------------------------------
# Line 1162 | Line 1391 | RTF_HYPERLINKS         = NO
1391  
1392   RTF_HYPERLINKS         = NO
1393  
1394 < # Load stylesheet definitions from file. Syntax is similar to doxygen's
1394 > # Load style sheet definitions from file. Syntax is similar to doxygen's
1395   # config file, i.e. a series of assignments. You only have to provide
1396   # replacements, missing definitions are set to their default value.
1397  
# Line 1307 | Line 1536 | EXPAND_ONLY_PREDEF     = NO
1536   EXPAND_ONLY_PREDEF     = NO
1537  
1538   # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1539 < # in the INCLUDE_PATH (see below) will be search if a #include is found.
1539 > # pointed to by INCLUDE_PATH will be searched when a #include is found.
1540  
1541   SEARCH_INCLUDES        = YES
1542  
# Line 1332 | Line 1561 | INCLUDE_FILE_PATTERNS  =
1561   # undefined via #undef or recursively expanded use the := operator
1562   # instead of the = operator.
1563  
1564 < PREDEFINED             = IS_MPI
1564 > PREDEFINED           =  ANTLR_CXX_SUPPORTS_NAMESPACE \
1565 >                        "ANTLR_USE_NAMESPACE(_x_)=_x_::" \
1566 >                        "ANTLR_USING_NAMESPACE(_x_)=using namespace _x_;" \
1567 >                        "ANTLR_C_USING(_x_)=" \
1568 >                        "ANTLR_API=" \
1569 >                        IS_MPI \
1570 >                        HAVE_QHULL \
1571 >                        HAVE_FFTW3
1572  
1573   # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1574   # this tag can be used to specify a list of macro names that should be expanded.
1575   # The macro definition that is found in the sources will be used.
1576 < # Use the PREDEFINED tag if you want to use a different macro definition.
1576 > # Use the PREDEFINED tag if you want to use a different macro definition that
1577 > # overrules the definition found in the source code.
1578  
1579   EXPAND_AS_DEFINED      =
1580  
1581   # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1582 < # doxygen's preprocessor will remove all function-like macros that are alone
1583 < # on a line, have an all uppercase name, and do not end with a semicolon. Such
1584 < # function macros are typically used for boiler-plate code, and will confuse
1348 < # the parser if not removed.
1582 > # doxygen's preprocessor will remove all references to function-like macros
1583 > # that are alone on a line, have an all uppercase name, and do not end with a
1584 > # semicolon, because these will confuse the parser if not removed.
1585  
1586   SKIP_FUNCTION_MACROS   = YES
1587  
# Line 1353 | Line 1589 | SKIP_FUNCTION_MACROS   = YES
1589   # Configuration::additions related to external references
1590   #---------------------------------------------------------------------------
1591  
1592 < # The TAGFILES option can be used to specify one or more tagfiles.
1593 < # Optionally an initial location of the external documentation
1594 < # can be added for each tagfile. The format of a tag file without
1359 < # this location is as follows:
1592 > # The TAGFILES option can be used to specify one or more tagfiles. For each
1593 > # tag file the location of the external documentation should be added. The
1594 > # format of a tag file without this location is as follows:
1595   #
1596   # TAGFILES = file1 file2 ...
1597   # Adding location for the tag files is done as follows:
1598   #
1599   # TAGFILES = file1=loc1 "file2 = loc2" ...
1600 < # where "loc1" and "loc2" can be relative or absolute paths or
1601 < # URLs. If a location is present for each tag, the installdox tool
1602 < # does not have to be run to correct the links.
1603 < # Note that each tag file must have a unique name
1369 < # (where the name does NOT include the path)
1370 < # If a tag file is not located in the directory in which doxygen
1371 < # is run, you must also specify the path to the tagfile here.
1600 > # where "loc1" and "loc2" can be relative or absolute paths
1601 > # or URLs. Note that each tag file must have a unique name (where the name does
1602 > # NOT include the path). If a tag file is not located in the directory in which
1603 > # doxygen is run, you must also specify the path to the tagfile here.
1604  
1605   TAGFILES               =
1606  
# Line 1401 | Line 1633 | PERL_PATH              = /usr/bin/perl
1633   # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1634   # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1635   # or super classes. Setting the tag to NO turns the diagrams off. Note that
1636 < # this option is superseded by the HAVE_DOT option below. This is only a
1637 < # fallback. It is recommended to install and use dot, since it yields more
1406 < # powerful graphs.
1636 > # this option also works with HAVE_DOT disabled, but it is recommended to
1637 > # install and use dot, since it yields more powerful graphs.
1638  
1639   CLASS_DIAGRAMS         = YES
1640  
# Line 1429 | Line 1660 | HAVE_DOT               = NO
1660  
1661   HAVE_DOT               = NO
1662  
1663 < # By default doxygen will write a font called FreeSans.ttf to the output
1664 < # directory and reference it in all dot files that doxygen generates. This
1665 < # font does not include all possible unicode characters however, so when you need
1666 < # these (or just want a differently looking font) you can specify the font name
1667 < # using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1437 < # which can be done by putting it in a standard location or by setting the
1438 < # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1439 < # containing the font.
1663 > # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
1664 > # allowed to run in parallel. When set to 0 (the default) doxygen will
1665 > # base this on the number of processors available in the system. You can set it
1666 > # explicitly to a value larger than 0 to get control over the balance
1667 > # between CPU load and processing speed.
1668  
1669 + DOT_NUM_THREADS        = 0
1670 +
1671 + # By default doxygen will use the Helvetica font for all dot files that
1672 + # doxygen generates. When you want a differently looking font you can specify
1673 + # the font name using DOT_FONTNAME. You need to make sure dot is able to find
1674 + # the font, which can be done by putting it in a standard location or by setting
1675 + # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
1676 + # directory containing the font.
1677 +
1678   DOT_FONTNAME           = FreeSans
1679  
1680   # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
# Line 1445 | Line 1682 | DOT_FONTSIZE           = 10
1682  
1683   DOT_FONTSIZE           = 10
1684  
1685 < # By default doxygen will tell dot to use the output directory to look for the
1686 < # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1687 < # different font using DOT_FONTNAME you can set the path where dot
1451 < # can find it using this tag.
1685 > # By default doxygen will tell dot to use the Helvetica font.
1686 > # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to
1687 > # set the path where dot can find it.
1688  
1689   DOT_FONTPATH           =
1690  
1691   # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1692   # will generate a graph for each documented class showing the direct and
1693   # indirect inheritance relations. Setting this tag to YES will force the
1694 < # the CLASS_DIAGRAMS tag to NO.
1694 > # CLASS_DIAGRAMS tag to NO.
1695  
1696   CLASS_GRAPH            = YES
1697  
# Line 1477 | Line 1713 | UML_LOOK               = NO
1713  
1714   UML_LOOK               = NO
1715  
1716 + # If the UML_LOOK tag is enabled, the fields and methods are shown inside
1717 + # the class node. If there are many fields or methods and many nodes the
1718 + # graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS
1719 + # threshold limits the number of items for each type to make the size more
1720 + # managable. Set this to 0 for no limit. Note that the threshold may be
1721 + # exceeded by 50% before the limit is enforced.
1722 +
1723 + UML_LIMIT_NUM_FIELDS   = 10
1724 +
1725   # If set to YES, the inheritance and collaboration graphs will show the
1726   # relations between templates and their instances.
1727  
# Line 1513 | Line 1758 | CALLER_GRAPH           = YES
1758   CALLER_GRAPH           = YES
1759  
1760   # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1761 < # will graphical hierarchy of all classes instead of a textual one.
1761 > # will generate a graphical hierarchy of all classes instead of a textual one.
1762  
1763   GRAPHICAL_HIERARCHY    = YES
1764  
1765 < # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1765 > # If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES
1766   # then doxygen will show the dependencies a directory has on other directories
1767   # in a graphical way. The dependency relations are determined by the #include
1768   # relations between the files in the directories.
# Line 1525 | Line 1770 | DIRECTORY_GRAPH        = YES
1770   DIRECTORY_GRAPH        = YES
1771  
1772   # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1773 < # generated by dot. Possible values are png, jpg, or gif
1774 < # If left blank png will be used.
1773 > # generated by dot. Possible values are svg, png, jpg, or gif.
1774 > # If left blank png will be used. If you choose svg you need to set
1775 > # HTML_FILE_EXTENSION to xhtml in order to make the SVG files
1776 > # visible in IE 9+ (other browsers do not have this requirement).
1777  
1778   DOT_IMAGE_FORMAT       = png
1779  
1780 + # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
1781 + # enable generation of interactive SVG images that allow zooming and panning.
1782 + # Note that this requires a modern browser other than Internet Explorer.
1783 + # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
1784 + # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files
1785 + # visible. Older versions of IE do not have SVG support.
1786 +
1787 + INTERACTIVE_SVG        = NO
1788 +
1789   # The tag DOT_PATH can be used to specify the path where the dot tool can be
1790   # found. If left blank, it is assumed the dot tool can be found in the path.
1791  
# Line 1541 | Line 1797 | DOTFILE_DIRS           =
1797  
1798   DOTFILE_DIRS           =
1799  
1800 + # The MSCFILE_DIRS tag can be used to specify one or more directories that
1801 + # contain msc files that are included in the documentation (see the
1802 + # \mscfile command).
1803 +
1804 + MSCFILE_DIRS           =
1805 +
1806   # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1807   # nodes that will be shown in the graph. If the number of nodes in a graph
1808   # becomes larger than this value, doxygen will truncate the graph, which is

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines