Lines Matching full:documentation
3 # This file describes the settings to be used by the documentation system
31 # This could be handy for archiving the generated documentation or
41 # included in the documentation. The maximum height of the logo should not
48 # base path where the generated documentation will be put.
64 # documentation generated by doxygen is written. Doxygen will use this
78 # the file and class documentation (similar to JavaDoc).
109 # inherited members of a class in the documentation of that class as if those
131 # the path mentioned in the documentation of a class, which tells
170 # member inherits the documentation from any documented member that it
176 # a new page for each member. If set to NO, the documentation of a member will
187 # as commands in the documentation. An alias has the form "name=value".
189 # put the command \sideeffect (or @sideeffect) in the documentation, which
256 # documentation. This will only work if the methods are indeed getting or
262 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
263 # tag is set to YES, then doxygen will reuse the documentation of the first
279 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
308 # documentation are documented, even if no documentation was available.
315 # will be included in the documentation.
320 # will be included in the documentation.
325 # defined locally in source files will be included in the documentation.
332 # the interface are included in the documentation.
338 # extracted and appear in the documentation as a namespace called
348 # various overviews, but no documentation section is generated.
363 # documentation.
368 # documentation blocks found inside the body of a function.
370 # function's detailed documentation block.
374 # The INTERNAL_DOCS tag determines if documentation
376 # to NO (the default) then the documentation will be excluded.
377 # Set it to YES to include the internal documentation.
391 # documentation. If set to YES the scope will be hidden.
396 # will put a list of the files that are included by a file in the documentation
402 # will list include files with double quotes in the documentation
408 # is inserted in the documentation for inline members.
413 # will sort the (detailed) documentation of file and class members
420 # brief documentation of file, namespace and class members alphabetically
427 # will sort the (brief and detailed) documentation of class members so that
460 # commands in the documentation.
466 # commands in the documentation.
472 # commands in the documentation.
478 # \deprecated commands in the documentation.
483 # documentation sections, marked by \if sectionname ... \endif.
489 # the documentation. If the initializer consists of more lines than specified
492 # documentation can be controlled using \showinitializer or \hideinitializer
493 # command in the documentation regardless of this setting.
498 # at the bottom of the documentation of classes and structs. If set to YES the
499 # list will mention the files that were used to generate the documentation.
505 # in the documentation. The default is NO.
563 # potential errors in the documentation, such as not documenting some
570 # functions that are documented, but have no documentation for their parameters
572 # wrong or incomplete parameter documentation, but not about the absence of
573 # documentation.
676 # directories that contain image that are included in the documentation (see
729 # of functions and classes directly in the documentation.
755 # Otherwise they will link to the documentation.
876 # documentation will contain sections that can be hidden and shown after the
886 # To create a documentation set, doxygen will generate a Makefile in the
889 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
897 # feed. A documentation feed provides an umbrella under which multiple
898 # documentation sets from a single provider (such as a company or product suite)
904 # should uniquely identify the documentation set bundle. This should be a
911 # the documentation publisher. This should be a reverse domain-name style
912 # string, e.g. com.mycompany.MyDocSet.documentation.
916 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
923 # of the generated HTML documentation.
960 # to the contents of the HTML help documentation and to the tree view.
967 # Qt Compressed Help (.qch) of the generated HTML documentation.
1041 # that doxygen will group on one line in the generated HTML documentation.
1073 # as images in the HTML documentation. The default is 10. Note that
1189 # higher quality PDF documentation.
1289 # the code including all documentation.
1325 # documentation. Note that this feature is still experimental
1336 # the code including all documentation. Note that this
1435 # Optionally an initial location of the external documentation
1490 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1623 # contain dot files that are included in the documentation (see the
1629 # contain msc files that are included in the documentation (see the
