Lines Matching full: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
223 # documentation blocks is shown as doxygen documentation.
229 # documentation from any documented member that it re-implements.
235 # page for each member. If set to NO, the documentation of a member will be part
248 # the documentation. An alias has the form:
253 # documentation, which will result in a user-defined paragraph with heading
325 # documentation. See https://daringfireball.net/projects/markdown/ for details.
343 # classes, or namespaces to their corresponding documentation. Such a link can
376 # doxygen to replace the get and set methods by a property in the documentation.
384 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
385 # tag is set to YES then doxygen will reuse the documentation of the first
421 # the documentation of the scope in which they are defined (i.e. file,
422 # namespace, or group documentation), provided this scope is documented. If set
431 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
471 # documentation are documented, even if no documentation was available. Private
481 # be included in the documentation.
487 # methods of a class will be included in the documentation.
493 # scope will be included in the documentation.
499 # included in the documentation.
505 # locally in source files will be included in the documentation. If set to NO,
514 # included in the documentation. If set to NO, only methods in the interface are
521 # extracted and appear in the documentation as a namespace called
538 # members will be included in the various overviews, but no documentation
554 # documentation.
560 # documentation blocks found inside the body of a function. If set to NO, these
561 # blocks will be appended to the function's detailed documentation block.
566 # The INTERNAL_DOCS tag determines if documentation that is typed after a
567 # \internal command is included. If the tag is set to NO then the documentation
568 # will be excluded. Set it to YES to include the internal documentation.
590 # their full class and namespace scopes in the documentation. If set to YES, the
604 # the files that are included by a file in the documentation of that file.
610 # grouped member an include statement to the documentation, telling the reader
617 # files with double quotes in the documentation rather than with sharp brackets.
623 # documentation for inline members.
629 # (detailed) documentation of file and class members alphabetically by member
644 # (brief and detailed) documentation of class members so that constructors and
648 # member documentation.
650 # detailed member documentation.
683 # list. This list is created by putting \todo commands in the documentation.
689 # list. This list is created by putting \test commands in the documentation.
695 # list. This list is created by putting \bug commands in the documentation.
702 # the documentation.
707 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
715 # documentation. If the initializer consists of more lines than specified here
719 # documentation regardless of this setting.
725 # the bottom of the documentation of classes and structs. If set to YES, the
726 # list will mention the files that were used to generate the documentation.
751 # version. For an example see the documentation.
793 # Tip: Turn warnings on while writing the documentation.
806 # potential errors in the documentation, such as not documenting some parameters
814 # are documented, but have no documentation for their parameters or return
816 # parameter documentation, but not about the absence of documentation. If
867 # documentation (see:
956 # that contain images that are to be included in the documentation (see the
1031 # classes and enums directly into the documentation.
1058 # link to the documentation.
1065 # brief description and links to the definition and documentation. Since this
1199 # of the possible markers and block names see the documentation.
1234 # list). For an example see the documentation.
1282 # documentation is up to date.
1289 # documentation will contain a main index with vertical navigation menus that
1300 # documentation will contain sections that can be hidden and shown after the
1324 # create a documentation set, doxygen will generate a Makefile in the HTML
1327 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1335 # This tag determines the name of the docset feed. A documentation feed provides
1336 # an umbrella under which multiple documentation sets from a single provider
1343 # This tag specifies a string that should uniquely identify the documentation
1352 # the documentation publisher. This should be a reverse domain-name style
1353 # string, e.g. com.mycompany.MyDocSet.documentation.
1359 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1376 # words in the documentation. The HTML workshop also contains a viewer for
1420 # the table of contents of the HTML help documentation and to the tree view.
1429 # (.qch) of the generated HTML documentation.
1504 # name. Each documentation set should have its own identifier.
1539 # doxygen will group on one line in the generated HTML documentation.
1574 # the HTML documentation. When you change the font size after a successful
1644 # example see the documentation.
1731 # to a relative location where the documentation can be found. The format is:
1872 # files. Set this option to YES, to get a higher quality PDF documentation.
2045 # captures the structure of the code including all documentation.
2107 # the structure of the code including all documentation. Note that this feature
2118 # file that captures the structure of the code including all documentation.
2234 # file the location of the external documentation should be added. The format of
2240 # section "Linking to external documentation" for more information about the use
2250 # external documentation" for more information about the usage of tag files.
2288 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2289 # then run dia to produce the diagram and insert it in the documentation. The
2479 # output formats in the documentation of the dot tool (Graphviz (see:
2513 # contain dot files that are included in the documentation (see the \dotfile
2520 # contain msc files that are included in the documentation (see the \mscfile
2526 # contain dia files that are included in the documentation (see the \diafile