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 # 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
195 # documentation from any documented member that it re-implements.
201 # new page for each member. If set to NO, the documentation of a member will be
214 # the documentation. An alias has the form:
219 # documentation, which will result in a user-defined paragraph with heading
277 # documentation. See http://daringfireball.net/projects/markdown/ for details.
286 # classes, or namespaces to their corresponding documentation. Such a link can
319 # doxygen to replace the get and set methods by a property in the documentation.
327 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
328 # tag is set to YES, then doxygen will reuse the documentation of the first
357 # the documentation of the scope in which they are defined (i.e. file,
358 # namespace, or group documentation), provided this scope is documented. If set
367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
394 # documentation are documented, even if no documentation was available. Private
404 # be included in the documentation.
410 # scope will be included in the documentation.
416 # included in the documentation.
422 # locally in source files will be included in the documentation. If set to NO
431 # included in the documentation. If set to NO only methods in the interface are
438 # extracted and appear in the documentation as a namespace called
448 # members will be included in the various overviews, but no documentation
464 # included in the documentation.
470 # documentation blocks found inside the body of a function. If set to NO these
471 # blocks will be appended to the function's detailed documentation block.
476 # The INTERNAL_DOCS tag determines if documentation that is typed after a
477 # \internal command is included. If the tag is set to NO then the documentation
478 # will be excluded. Set it to YES to include the internal documentation.
493 # their full class and namespace scopes in the documentation. If set to YES the
500 # the files that are included by a file in the documentation of that file.
506 # grouped member an include statement to the documentation, telling the reader
513 # files with double quotes in the documentation rather than with sharp brackets.
519 # documentation for inline members.
525 # (detailed) documentation of file and class members alphabetically by member
540 # (brief and detailed) documentation of class members so that constructors and
544 # member documentation.
546 # detailed member documentation.
580 # documentation.
587 # documentation.
593 # list. This list is created by putting \bug commands in the documentation.
600 # the documentation.
605 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
613 # documentation. If the initializer consists of more lines than specified here
617 # documentation regardless of this setting.
623 # the bottom of the documentation of classes and structs. If set to YES the list
624 # will mention the files that were used to generate the documentation.
649 # version. For an example see the documentation.
692 # Tip: Turn warnings on while writing the documentation.
705 # potential errors in the documentation, such as not documenting some parameters
713 # are documented, but have no documentation for their parameters or return
715 # documentation, but not about the absence of documentation.
760 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
840 # that contain images that are to be included in the documentation (see the
907 # classes and enums directly into the documentation.
934 # link to the documentation.
941 # brief description and links to the definition and documentation. Since this
1044 # of the possible markers and block names see the documentation.
1077 # see the documentation.
1131 # documentation will contain sections that can be hidden and shown after the
1154 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1165 # This tag determines the name of the docset feed. A documentation feed provides
1166 # an umbrella under which multiple documentation sets from a single provider
1173 # This tag specifies a string that should uniquely identify the documentation
1182 # the documentation publisher. This should be a reverse domain-name style
1183 # string, e.g. com.mycompany.MyDocSet.documentation.
1189 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1206 # words in the documentation. The HTML workshop also contains a viewer for
1249 # the table of contents of the HTML help documentation and to the tree view.
1258 # (.qch) of the generated HTML documentation.
1332 # name. Each documentation set should have its own identifier.
1367 # doxygen will group on one line in the generated HTML documentation.
1391 # the HTML documentation. When you change the font size after a successful
1454 # example see the documentation.
1539 # to a relative location where the documentation can be found. The format is:
1650 # higher quality PDF documentation.
1788 # captures the structure of the code including all documentation.
1846 # the code including all documentation. Note that this feature is still
1857 # file that captures the structure of the code including all documentation.
1973 # file the location of the external documentation should be added. The format of
1979 # section "Linking to external documentation" for more information about the use
1989 # external documentation" for more information about the usage of tag files.
2035 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2041 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2042 # then run dia to produce the diagram and insert it in the documentation. The
2236 # contain dot files that are included in the documentation (see the \dotfile
2243 # contain msc files that are included in the documentation (see the \mscfile
2249 # contain dia files that are included in the documentation (see the \diafile