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
46 # included in the documentation. The maximum height of the logo should not
53 # base path where the generated documentation will be put.
69 # documentation generated by doxygen is written. Doxygen will use this
83 # the file and class documentation (similar to JavaDoc).
124 # inherited members of a class in the documentation of that class as if those
146 # the path mentioned in the documentation of a class, which tells
185 # member inherits the documentation from any documented member that it
191 # a new page for each member. If set to NO, the documentation of a member will
202 # as commands in the documentation. An alias has the form "name=value".
204 # put the command \sideeffect (or @sideeffect) in the documentation, which
277 # documentation. See http://daringfireball.net/projects/markdown/ for details.
307 # documentation. This will only work if the methods are indeed getting or
313 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
314 # tag is set to YES, then doxygen will reuse the documentation of the first
336 # unions with only public data fields will be shown inline in the documentation
338 # documentation), provided this scope is documented. If set to NO (the default),
346 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
386 # documentation are documented, even if no documentation was available.
393 # will be included in the documentation.
397 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation.
402 # will be included in the documentation.
407 # defined locally in source files will be included in the documentation.
414 # the interface are included in the documentation.
420 # extracted and appear in the documentation as a namespace called
430 # various overviews, but no documentation section is generated.
445 # documentation.
450 # documentation blocks found inside the body of a function.
452 # function's detailed documentation block.
456 # The INTERNAL_DOCS tag determines if documentation
458 # to NO (the default) then the documentation will be excluded.
459 # Set it to YES to include the internal documentation.
473 # documentation. If set to YES the scope will be hidden.
478 # will put a list of the files that are included by a file in the documentation
484 # will list include files with double quotes in the documentation
490 # is inserted in the documentation for inline members.
495 # will sort the (detailed) documentation of file and class members
502 # brief documentation of file, namespace and class members alphabetically
509 # will sort the (brief and detailed) documentation of class members so that
545 # commands in the documentation.
551 # commands in the documentation.
557 # commands in the documentation.
563 # \deprecated commands in the documentation.
568 # documentation sections, marked by \if sectionname ... \endif.
574 # the documentation. If the initializer consists of more lines than specified
577 # documentation can be controlled using \showinitializer or \hideinitializer
578 # command in the documentation regardless of this setting.
583 # at the bottom of the documentation of classes and structs. If set to YES the
584 # list will mention the files that were used to generate the documentation.
652 # potential errors in the documentation, such as not documenting some
659 # functions that are documented, but have no documentation for their parameters
661 # wrong or incomplete parameter documentation, but not about the absence of
662 # documentation.
800 # directories that contain image that are included in the documentation (see
853 # of functions and classes directly in the documentation.
879 # Otherwise they will link to the documentation.
1011 # documentation will contain sections that can be hidden and shown after the
1030 # To create a documentation set, doxygen will generate a Makefile in the
1033 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
1041 # feed. A documentation feed provides an umbrella under which multiple
1042 # documentation sets from a single provider (such as a company or product suite)
1048 # should uniquely identify the documentation set bundle. This should be a
1055 # the documentation publisher. This should be a reverse domain-name style
1056 # string, e.g. com.mycompany.MyDocSet.documentation.
1060 documentation publisher.
1067 # of the generated HTML documentation.
1104 # to the contents of the HTML help documentation and to the tree view.
1111 # Qt Compressed Help (.qch) of the generated HTML documentation.
1200 # documentation. Note that a value of 0 will completely suppress the enum
1217 # as images in the HTML documentation. The default is 10. Note that
1348 # higher quality PDF documentation.
1454 # the code including all documentation.
1490 # documentation. Note that this feature is still experimental
1501 # the code including all documentation. Note that this
1616 # tag file the location of the external documentation should be added. The
1668 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1819 # contain dot files that are included in the documentation (see the
1825 # contain msc files that are included in the documentation (see the
