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 # the documentation. The maximum height of the logo should not exceed 55 pixels
57 # into which the generated documentation will be written. If a relative path is
74 # documentation generated by doxygen is written. Doxygen will use this
90 # documentation (similar to Javadoc). Set to NO to disable this.
123 # inherited members of a class in the documentation of that class as if those
150 # path mentioned in the documentation of a class, which tells the reader which
196 # documentation from any documented member that it re-implements.
202 # new page for each member. If set to NO, the documentation of a member will be
215 # the documentation. An alias has the form:
220 # documentation, which will result in a user-defined paragraph with heading
278 # documentation. See http://daringfireball.net/projects/markdown/ for details.
287 # classes, or namespaces to their corresponding documentation. Such a link can
320 # doxygen to replace the get and set methods by a property in the documentation.
328 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
329 # tag is set to YES, then doxygen will reuse the documentation of the first
358 # the documentation of the scope in which they are defined (i.e. file,
359 # namespace, or group documentation), provided this scope is documented. If set
368 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
395 # documentation are documented, even if no documentation was available. Private
405 # be included in the documentation.
411 # scope will be included in the documentation.
417 # included in the documentation.
423 # locally in source files will be included in the documentation. If set to NO
432 # included in the documentation. If set to NO only methods in the interface are
439 # extracted and appear in the documentation as a namespace called
449 # members will be included in the various overviews, but no documentation
465 # included in the documentation.
471 # documentation blocks found inside the body of a function. If set to NO these
472 # blocks will be appended to the function's detailed documentation block.
477 # The INTERNAL_DOCS tag determines if documentation that is typed after a
478 # \internal command is included. If the tag is set to NO then the documentation
479 # will be excluded. Set it to YES to include the internal documentation.
494 # their full class and namespace scopes in the documentation. If set to YES the
501 # the files that are included by a file in the documentation of that file.
507 # grouped member an include statement to the documentation, telling the reader
514 # files with double quotes in the documentation rather than with sharp brackets.
520 # documentation for inline members.
526 # (detailed) documentation of file and class members alphabetically by member
541 # (brief and detailed) documentation of class members so that constructors and
545 # member documentation.
547 # detailed member documentation.
581 # documentation.
588 # documentation.
594 # list. This list is created by putting \bug commands in the documentation.
601 # the documentation.
606 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
614 # documentation. If the initializer consists of more lines than specified here
618 # documentation regardless of this setting.
624 # the bottom of the documentation of classes and structs. If set to YES the list
625 # will mention the files that were used to generate the documentation.
650 # version. For an example see the documentation.
693 # Tip: Turn warnings on while writing the documentation.
706 # potential errors in the documentation, such as not documenting some parameters
714 # are documented, but have no documentation for their parameters or return
716 # documentation, but not about the absence of documentation.
754 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
834 # that contain images that are to be included in the documentation (see the
901 # classes and enums directly into the documentation.
928 # link to the documentation.
935 # brief description and links to the definition and documentation. Since this
1038 # of the possible markers and block names see the documentation.
1071 # see the documentation.
1125 # documentation will contain sections that can be hidden and shown after the
1148 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1151 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1159 # This tag determines the name of the docset feed. A documentation feed provides
1160 # an umbrella under which multiple documentation sets from a single provider
1167 # This tag specifies a string that should uniquely identify the documentation
1176 # the documentation publisher. This should be a reverse domain-name style
1177 # string, e.g. com.mycompany.MyDocSet.documentation.
1183 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1200 # words in the documentation. The HTML workshop also contains a viewer for
1243 # the table of contents of the HTML help documentation and to the tree view.
1252 # (.qch) of the generated HTML documentation.
1326 # name. Each documentation set should have its own identifier.
1361 # doxygen will group on one line in the generated HTML documentation.
1385 # the HTML documentation. When you change the font size after a successful
1448 # example see the documentation.
1533 # to a relative location where the documentation can be found. The format is:
1644 # higher quality PDF documentation.
1782 # captures the structure of the code including all documentation.
1828 # the code including all documentation. Note that this feature is still
1839 # file that captures the structure of the code including all documentation.
1955 # file the location of the external documentation should be added. The format of
1961 # section "Linking to external documentation" for more information about the use
1971 # external documentation" for more information about the usage of tag files.
2017 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2023 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2024 # then run dia to produce the diagram and insert it in the documentation. The
2218 # contain dot files that are included in the documentation (see the \dotfile
2225 # contain msc files that are included in the documentation (see the \mscfile
2231 # contain dia files that are included in the documentation (see the \diafile