Lines Matching refs:documentation

3 # This file describes the settings to be used by the documentation system
31 # project for which the documentation is generated. This name is used in the
38 # could be handy for archiving the generated documentation or if some version
50 # in the documentation. The maximum height of the logo should not exceed 55
57 # into which the generated documentation will be written. If a relative path is
82 # documentation generated by doxygen is written. Doxygen will use this
97 # documentation generated by doxygen is written. Doxygen will use this
106 # documentation (similar to Javadoc). Set to NO to disable this.
139 # inherited members of a class in the documentation of that class as if those
166 # path mentioned in the documentation of a class, which tells the reader which
221 # documentation from any documented member that it re-implements.
227 # page for each member. If set to NO, the documentation of a member will be part
240 # the documentation. An alias has the form:
245 # documentation, which will result in a user-defined paragraph with heading
320 # documentation. See https://daringfireball.net/projects/markdown/ for details.
338 # classes, or namespaces to their corresponding documentation. Such a link can
371 # doxygen to replace the get and set methods by a property in the documentation.
379 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
380 # tag is set to YES then doxygen will reuse the documentation of the first
416 # the documentation of the scope in which they are defined (i.e. file,
417 # namespace, or group documentation), provided this scope is documented. If set
426 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
453 # documentation are documented, even if no documentation was available. Private
463 # be included in the documentation.
469 # methods of a class will be included in the documentation.
475 # scope will be included in the documentation.
481 # included in the documentation.
487 # locally in source files will be included in the documentation. If set to NO,
496 # included in the documentation. If set to NO, only methods in the interface are
503 # extracted and appear in the documentation as a namespace called
513 # members will be included in the various overviews, but no documentation
529 # included in the documentation.
535 # documentation blocks found inside the body of a function. If set to NO, these
536 # blocks will be appended to the function's detailed documentation block.
541 # The INTERNAL_DOCS tag determines if documentation that is typed after a
542 # \internal command is included. If the tag is set to NO then the documentation
543 # will be excluded. Set it to YES to include the internal documentation.
558 # their full class and namespace scopes in the documentation. If set to YES, the
572 # the files that are included by a file in the documentation of that file.
578 # grouped member an include statement to the documentation, telling the reader
585 # files with double quotes in the documentation rather than with sharp brackets.
591 # documentation for inline members.
597 # (detailed) documentation of file and class members alphabetically by member
612 # (brief and detailed) documentation of class members so that constructors and
616 # member documentation.
618 # detailed member documentation.
651 # list. This list is created by putting \todo commands in the documentation.
657 # list. This list is created by putting \test commands in the documentation.
663 # list. This list is created by putting \bug commands in the documentation.
670 # the documentation.
675 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
683 # documentation. If the initializer consists of more lines than specified here
687 # documentation regardless of this setting.
693 # the bottom of the documentation of classes and structs. If set to YES, the
694 # list will mention the files that were used to generate the documentation.
719 # version. For an example see the documentation.
761 # Tip: Turn warnings on while writing the documentation.
774 # potential errors in the documentation, such as not documenting some parameters
782 # are documented, but have no documentation for their parameters or return
784 # parameter documentation, but not about the absence of documentation. If
828 # documentation (see: https://www.gnu.org/software/libiconv/) for the list of
913 # that contain images that are to be included in the documentation (see the
988 # classes and enums directly into the documentation.
1015 # link to the documentation.
1022 # brief description and links to the definition and documentation. Since this
1154 # of the possible markers and block names see the documentation.
1189 # list). For an example see the documentation.
1237 # documentation is up to date.
1244 # documentation will contain a main index with vertical navigation menus that
1255 # documentation will contain sections that can be hidden and shown after the
1278 # 10.5 (Leopard). To create a documentation set, doxygen will generate a
1289 # This tag determines the name of the docset feed. A documentation feed provides
1290 # an umbrella under which multiple documentation sets from a single provider
1297 # This tag specifies a string that should uniquely identify the documentation
1306 # the documentation publisher. This should be a reverse domain-name style
1307 # string, e.g. com.mycompany.MyDocSet.documentation.
1313 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1330 # words in the documentation. The HTML workshop also contains a viewer for
1374 # the table of contents of the HTML help documentation and to the tree view.
1383 # (.qch) of the generated HTML documentation.
1457 # name. Each documentation set should have its own identifier.
1492 # doxygen will group on one line in the generated HTML documentation.
1516 # the HTML documentation. When you change the font size after a successful
1579 # example see the documentation.
1664 # to a relative location where the documentation can be found. The format is:
1805 # higher quality PDF documentation.
1976 # captures the structure of the code including all documentation.
2038 # the structure of the code including all documentation. Note that this feature
2049 # file that captures the structure of the code including all documentation.
2165 # file the location of the external documentation should be added. The format of
2171 # section "Linking to external documentation" for more information about the use
2181 # external documentation" for more information about the usage of tag files.
2219 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2220 # then run dia to produce the diagram and insert it in the documentation. The
2388 # output formats in the documentation of the dot tool (Graphviz (see:
2422 # contain dot files that are included in the documentation (see the \dotfile
2429 # contain msc files that are included in the documentation (see the \mscfile
2435 # contain dia files that are included in the documentation (see the \diafile