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
98 # documentation (similar to Javadoc). Set to NO to disable this.
141 # inherited members of a class in the documentation of that class as if those
168 # path mentioned in the documentation of a class, which tells the reader which
213 # documentation from any documented member that it re-implements.
219 # page for each member. If set to NO, the documentation of a member will be part
232 # the documentation. An alias has the form:
237 # documentation, which will result in a user-defined paragraph with heading
298 # documentation. See http://daringfireball.net/projects/markdown/ for details.
307 # classes, or namespaces to their corresponding documentation. Such a link can
340 # doxygen to replace the get and set methods by a property in the documentation.
348 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
349 # tag is set to YES then doxygen will reuse the documentation of the first
385 # the documentation of the scope in which they are defined (i.e. file,
386 # namespace, or group documentation), provided this scope is documented. If set
395 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
422 # documentation are documented, even if no documentation was available. Private
432 # be included in the documentation.
438 # scope will be included in the documentation.
444 # included in the documentation.
450 # locally in source files will be included in the documentation. If set to NO,
459 # included in the documentation. If set to NO, only methods in the interface are
466 # extracted and appear in the documentation as a namespace called
476 # members will be included in the various overviews, but no documentation
492 # included in the documentation.
498 # documentation blocks found inside the body of a function. If set to NO, these
499 # blocks will be appended to the function's detailed documentation block.
504 # The INTERNAL_DOCS tag determines if documentation that is typed after a
505 # \internal command is included. If the tag is set to NO then the documentation
506 # will be excluded. Set it to YES to include the internal documentation.
521 # their full class and namespace scopes in the documentation. If set to YES, the
535 # the files that are included by a file in the documentation of that file.
541 # grouped member an include statement to the documentation, telling the reader
548 # files with double quotes in the documentation rather than with sharp brackets.
554 # documentation for inline members.
560 # (detailed) documentation of file and class members alphabetically by member
575 # (brief and detailed) documentation of class members so that constructors and
579 # member documentation.
581 # detailed member documentation.
614 # list. This list is created by putting \todo commands in the documentation.
620 # list. This list is created by putting \test commands in the documentation.
626 # list. This list is created by putting \bug commands in the documentation.
633 # the documentation.
638 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
646 # documentation. If the initializer consists of more lines than specified here
650 # documentation regardless of this setting.
656 # the bottom of the documentation of classes and structs. If set to YES, the
657 # list will mention the files that were used to generate the documentation.
682 # version. For an example see the documentation.
724 # Tip: Turn warnings on while writing the documentation.
737 # potential errors in the documentation, such as not documenting some parameters
745 # are documented, but have no documentation for their parameters or return
747 # parameter documentation, but not about the absence of documentation.
789 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
876 # that contain images that are to be included in the documentation (see the
951 # classes and enums directly into the documentation.
978 # link to the documentation.
985 # brief description and links to the definition and documentation. Since this
1107 # of the possible markers and block names see the documentation.
1142 # list). For an example see the documentation.
1190 # documentation is up to date.
1197 # documentation will contain sections that can be hidden and shown after the
1220 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1231 # This tag determines the name of the docset feed. A documentation feed provides
1232 # an umbrella under which multiple documentation sets from a single provider
1239 # This tag specifies a string that should uniquely identify the documentation
1248 # the documentation publisher. This should be a reverse domain-name style
1249 # string, e.g. com.mycompany.MyDocSet.documentation.
1255 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1272 # words in the documentation. The HTML workshop also contains a viewer for
1316 # the table of contents of the HTML help documentation and to the tree view.
1325 # (.qch) of the generated HTML documentation.
1399 # name. Each documentation set should have its own identifier.
1434 # doxygen will group on one line in the generated HTML documentation.
1458 # the HTML documentation. When you change the font size after a successful
1521 # example see the documentation.
1606 # to a relative location where the documentation can be found. The format is:
1733 # higher quality PDF documentation.
1896 # captures the structure of the code including all documentation.
1951 # structure of the code including all documentation. Note that this feature is
1962 # file that captures the structure of the code including all documentation.
2087 # file the location of the external documentation should be added. The format of
2093 # section "Linking to external documentation" for more information about the use
2103 # external documentation" for more information about the usage of tag files.
2150 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2156 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2157 # then run dia to produce the diagram and insert it in the documentation. The
2325 # output formats in the documentation of the dot tool (Graphviz (see:
2357 # contain dot files that are included in the documentation (see the \dotfile
2364 # contain msc files that are included in the documentation (see the \mscfile
2370 # contain dia files that are included in the documentation (see the \diafile