Lines Matching full:documentation
3 # This file describes the settings to be used by the documentation system
32 # This could be handy for archiving the generated documentation or
44 # included in the documentation. The maximum height of the logo should not
51 # base path where the generated documentation will be put.
67 # documentation generated by doxygen is written. Doxygen will use this
81 # the file and class documentation (similar to JavaDoc).
112 # inherited members of a class in the documentation of that class as if those
134 # the path mentioned in the documentation of a class, which tells
173 # member inherits the documentation from any documented member that it
179 # a new page for each member. If set to NO, the documentation of a member will
190 # as commands in the documentation. An alias has the form "name=value".
192 # put the command \sideeffect (or @sideeffect) in the documentation, which
245 # documentation. See http://daringfireball.net/projects/markdown/ for details.
275 # documentation. This will only work if the methods are indeed getting or
281 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
282 # tag is set to YES, then doxygen will reuse the documentation of the first
304 # unions with only public data fields will be shown inline in the documentation
306 # documentation), provided this scope is documented. If set to NO (the default),
314 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
354 # documentationdocumentation was available.
361 # will be included in the documentation.
365 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation.
370 # will be included in the documentation.
375 # defined locally in source files will be included in the documentation.
382 # the interface are included in the documentation.
388 # extracted and appear in the documentation as a namespace called
398 # various overviews, but no documentation section is generated.
413 # documentation.
418 # documentation blocks found inside the body of a function.
420 # function's detailed documentation block.
424 # The INTERNAL_DOCS tag determines if documentation
426 # to NO (the default) then the documentation will be excluded.
427 # Set it to YES to include the internal documentation.
441 # documentation. If set to YES the scope will be hidden.
446 # will put a list of the files that are included by a file in the documentation
452 # will list include files with double quotes in the documentation
458 # is inserted in the documentation for inline members.
463 # will sort the (detailed) documentation of file and class members
470 # brief documentation of file, namespace and class members alphabetically
477 # will sort the (brief and detailed) documentation of class members so that
513 # commands in the documentation.
519 # commands in the documentation.
525 # commands in the documentation.
531 # \deprecated commands in the documentation.
536 # documentation sections, marked by \if sectionname ... \endif.
542 # the documentation. If the initializer consists of more lines than specified
545 # documentation can be controlled using \showinitializer or \hideinitializer
546 # command in the documentation regardless of this setting.
551 # at the bottom of the documentation of classes and structs. If set to YES the
552 # list will mention the files that were used to generate the documentation.
620 # potential errors in the documentation, such as not documenting some
627 # functions that are documented, but have no documentation for their parameters
629 # wrong or incomplete parameter documentation, but not about the absence of
630 # documentation.
736 # directories that contain image that are included in the documentation (see
789 # of functions and classes directly in the documentation.
815 # Otherwise they will link to the documentation.
946 # documentation will contain sections that can be hidden and shown after the
965 # To create a documentation set, doxygen will generate a Makefile in the
968 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
976 # feed. A documentation feed provides an umbrella under which multiple
977 # documentation sets from a single provider (such as a company or product suite)
983 # should uniquely identify the documentation set bundle. This should be a
990 # the documentation publisher. This should be a reverse domain-name style
991 # string, e.g. com.mycompany.MyDocSet.documentation.
995 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
1002 # of the generated HTML documentation.
1039 # to the contents of the HTML help documentation and to the tree view.
1046 # Qt Compressed Help (.qch) of the generated HTML documentation.
1135 # documentation. Note that a value of 0 will completely suppress the enum
1152 # as images in the HTML documentation. The default is 10. Note that
1282 # higher quality PDF documentation.
1388 # the code including all documentation.
1424 # documentation. Note that this feature is still experimental
1435 # the code including all documentation. Note that this
1535 documentation should be added. The
1586 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1737 # contain dot files that are included in the documentation (see the
1743 # contain msc files that are included in the documentation (see the
