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
37 # base path where the generated documentation will be put.
53 # documentation generated by doxygen is written. Doxygen will use this
67 # the file and class documentation (similar to JavaDoc).
108 # inherited members of a class in the documentation of that class as if those
130 # the path mentioned in the documentation of a class, which tells
169 # member inherits the documentation from any documented member that it
175 # a new page for each member. If set to NO, the documentation of a member will
186 # as commands in the documentation. An alias has the form "name=value".
188 # put the command \sideeffect (or @sideeffect) in the documentation, which
255 # documentation. This will only work if the methods are indeed getting or
261 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
262 # tag is set to YES, then doxygen will reuse the documentation of the first
278 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
307 # documentation are documented, even if no documentation was available.
314 # will be included in the documentation.
319 # will be included in the documentation.
324 # defined locally in source files will be included in the documentation.
331 # the interface are included in the documentation.
337 # extracted and appear in the documentation as a namespace called
347 # various overviews, but no documentation section is generated.
362 # documentation.
367 # documentation blocks found inside the body of a function.
369 # function's detailed documentation block.
373 # The INTERNAL_DOCS tag determines if documentation
375 # to NO (the default) then the documentation will be excluded.
376 # Set it to YES to include the internal documentation.
390 # documentation. If set to YES the scope will be hidden.
395 # will put a list of the files that are included by a file in the documentation
401 # will list include files with double quotes in the documentation
407 # is inserted in the documentation for inline members.
412 # will sort the (detailed) documentation of file and class members
419 # brief documentation of file, namespace and class members alphabetically
426 # will sort the (brief and detailed) documentation of class members so that
453 # commands in the documentation.
459 # commands in the documentation.
465 # commands in the documentation.
471 # \deprecated commands in the documentation.
476 # documentation sections, marked by \if sectionname ... \endif.
482 # the documentation. If the initializer consists of more lines than specified
485 # documentation can be controlled using \showinitializer or \hideinitializer
486 # command in the documentation regardless of this setting.
491 # at the bottom of the documentation of classes and structs. If set to YES the
492 # list will mention the files that were used to generate the documentation.
498 # in the documentation. The default is NO.
555 # potential errors in the documentation, such as not documenting some
562 # functions that are documented, but have no documentation for their parameters
564 # wrong or incomplete parameter documentation, but not about the absence of
565 # documentation.
695 # directories that contain image that are included in the documentation (see
737 # of functions and classes directly in the documentation.
762 # link to the source code. Otherwise they will link to the documentation.
883 # documentation will contain sections that can be hidden and shown after the
893 # To create a documentation set, doxygen will generate a Makefile in the
896 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
904 # feed. A documentation feed provides an umbrella under which multiple
905 # documentation sets from a single provider (such as a company or product suite)
911 # should uniquely identify the documentation set bundle. This should be a
918 # the documentation publisher. This should be a reverse domain-name style
919 # string, e.g. com.mycompany.MyDocSet.documentation.
923 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
930 # of the generated HTML documentation.
967 # to the contents of the HTML help documentation and to the tree view.
974 # Qt Compressed Help (.qch) of the generated HTML documentation.
1048 # that doxygen will group on one line in the generated HTML documentation.
1079 # as images in the HTML documentation. The default is 10. Note that
1176 # higher quality PDF documentation.
1276 # the code including all documentation.
1312 # documentation. Note that this feature is still experimental
1323 # the code including all documentation. Note that this
1421 # Optionally an initial location of the external documentation
1475 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1609 # contain dot files that are included in the documentation (see the