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
136 # the path mentioned in the documentation of a class, which tells
175 # member inherits the documentation from any documented member that it
181 # a new page for each member. If set to NO, the documentation of a member will
192 # as commands in the documentation. An alias has the form "name=value".
194 # put the command \sideeffect (or @sideeffect) in the documentation, which
248 # documentation. See http://daringfireball.net/projects/markdown/ for details.
256 # or namespaces to their corresponding documentation. Such a link can be
285 # set methods by a property in the documentation. This will only work
292 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
293 # tag is set to YES, then doxygen will reuse the documentation of the first
315 # unions with only public data fields will be shown inline in the documentation
317 # documentation), provided this scope is documented. If set to NO (the default),
325 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
365 # documentation are documented, even if no documentation was available.
372 # will be included in the documentation.
377 # scope will be included in the documentation.
382 # will be included in the documentation.
387 # defined locally in source files will be included in the documentation.
394 # the interface are included in the documentation.
400 # extracted and appear in the documentation as a namespace called
410 # various overviews, but no documentation section is generated.
425 # documentation.
430 # documentation blocks found inside the body of a function.
432 # function's detailed documentation block.
436 # The INTERNAL_DOCS tag determines if documentation
438 # to NO (the default) then the documentation will be excluded.
439 # Set it to YES to include the internal documentation.
453 # documentation. If set to YES the scope will be hidden.
458 # will put a list of the files that are included by a file in the documentation
464 # will list include files with double quotes in the documentation
470 # is inserted in the documentation for inline members.
475 # will sort the (detailed) documentation of file and class members
482 # brief documentation of file, namespace and class members alphabetically
489 # will sort the (brief and detailed) documentation of class members so that
525 # commands in the documentation.
531 # commands in the documentation.
537 # commands in the documentation.
543 # \deprecated commands in the documentation.
548 # documentation sections, marked by \if sectionname ... \endif.
554 # the documentation. If the initializer consists of more lines than specified
557 # documentation can be controlled using \showinitializer or \hideinitializer
558 # command in the documentation regardless of this setting.
563 # at the bottom of the documentation of classes and structs. If set to YES the
564 # list will mention the files that were used to generate the documentation.
572 # We probably will want this, but we have no file documentation yet so it's simpler to remove
634 # potential errors in the documentation, such as not documenting some
641 # functions that are documented, but have no documentation for their parameters
643 # wrong or incomplete parameter documentation, but not about the absence of
644 # documentation.
673 # The ittnotify code also has doxygen documentation, but if we include it here
695 # doxygen doesn't see the content, just the documentation...
755 # directories that contain image that are included in the documentation (see
808 # of functions and classes directly in the documentation.
834 # Otherwise they will link to the documentation.
975 # documentation will contain sections that can be hidden and shown after the
994 # To create a documentation set, doxygen will generate a Makefile in the
997 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
1005 # feed. A documentation feed provides an umbrella under which multiple
1006 # documentation sets from a single provider (such as a company or product suite)
1012 # should uniquely identify the documentation set bundle. This should be a
1019 # identify the documentation publisher. This should be a reverse domain-name
1020 # style string, e.g. com.mycompany.MyDocSet.documentation.
1024 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
1031 # of the generated HTML documentation.
1068 # to the contents of the HTML help documentation and to the tree view.
1075 # Qt Compressed Help (.qch) of the generated HTML documentation.
1164 # documentation. Note that a value of 0 will completely suppress the enum
1181 # as images in the HTML documentation. The default is 10. Note that
1311 # higher quality PDF documentation.
1417 # the code including all documentation.
1453 # documentation. Note that this feature is still experimental
1464 # the code including all documentation. Note that this
1564 # tag file the location of the external documentation should be added. The
1615 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1766 # contain dot files that are included in the documentation (see the
1772 # contain msc files that are included in the documentation (see the