Lines Matching refs:documentation

3 # This file describes the settings to be used by the documentation system
32 # This could be handy for archiving the generated documentation or
44 # included in the documentation. The maximum height of the logo should not
51 # base path where the generated documentation will be put.
67 # documentation generated by doxygen is written. Doxygen will use this
81 # the file and class documentation (similar to JavaDoc).
122 # inherited members of a class in the documentation of that class as if those
146 # the path mentioned in the documentation of a class, which tells
185 # member inherits the documentation from any documented member that it
191 # a new page for each member. If set to NO, the documentation of a member will
202 # as commands in the documentation. An alias has the form "name=value".
204 # put the command \sideeffect (or @sideeffect) in the documentation, which
258 # documentation. See http://daringfireball.net/projects/markdown/ for details.
266 # or namespaces to their corresponding documentation. Such a link can be
295 # the documentation. This will only work if the methods are indeed getting or
301 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
302 # tag is set to YES, then doxygen will reuse the documentation of the first
324 # unions with only public data fields will be shown inline in the documentation
326 # documentation), provided this scope is documented. If set to NO (the default),
334 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
374 # documentation are documented, even if no documentation was available.
381 # will be included in the documentation.
386 # scope will be included in the documentation.
391 # will be included in the documentation.
396 # defined locally in source files will be included in the documentation.
403 # the interface are included in the documentation.
409 # extracted and appear in the documentation as a namespace called
419 # various overviews, but no documentation section is generated.
434 # documentation.
439 # documentation blocks found inside the body of a function.
441 # function's detailed documentation block.
445 # The INTERNAL_DOCS tag determines if documentation
447 # to NO (the default) then the documentation will be excluded.
448 # Set it to YES to include the internal documentation.
462 # documentation. If set to YES the scope will be hidden.
467 # will put a list of the files that are included by a file in the documentation
473 # will list include files with double quotes in the documentation
479 # is inserted in the documentation for inline members.
484 # will sort the (detailed) documentation of file and class members
491 # brief documentation of file, namespace and class members alphabetically
498 # will sort the (brief and detailed) documentation of class members so that
534 # commands in the documentation.
540 # commands in the documentation.
546 # commands in the documentation.
552 # \deprecated commands in the documentation.
557 # documentation sections, marked by \if section-label ... \endif
564 # the documentation. If the initializer consists of more lines than specified
567 # documentation can be controlled using \showinitializer or \hideinitializer
568 # command in the documentation regardless of this setting.
573 # at the bottom of the documentation of classes and structs. If set to YES the
574 # list will mention the files that were used to generate the documentation.
642 # potential errors in the documentation, such as not documenting some
649 # functions that are documented, but have no documentation for their parameters
651 # wrong or incomplete parameter documentation, but not about the absence of
652 # documentation.
790 # directories that contain image that are included in the documentation (see
847 # of functions and classes directly in the documentation.
872 # link to the source code.  Otherwise they will link to the documentation.
1013 # documentation will contain sections that can be hidden and shown after the
1032 # To create a documentation set, doxygen will generate a Makefile in the
1043 # feed. A documentation feed provides an umbrella under which multiple
1044 # documentation sets from a single provider (such as a company or product suite)
1050 # should uniquely identify the documentation set bundle. This should be a
1057 # identify the documentation publisher. This should be a reverse domain-name
1058 # style string, e.g. com.mycompany.MyDocSet.documentation.
1062 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
1069 # of the generated HTML documentation.
1106 # to the contents of the HTML help documentation and to the tree view.
1113 # Qt Compressed Help (.qch) of the generated HTML documentation.
1202 # documentation. Note that a value of 0 will completely suppress the enum
1219 # as images in the HTML documentation. The default is 10. Note that
1321 # of to a relative location where the documentation can be found.
1395 # higher quality PDF documentation.
1501 # the code including all documentation.
1537 # documentation. Note that this feature is still experimental
1548 # the code including all documentation. Note that this
1662 # tag file the location of the external documentation should be added. The
1711 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1862 # contain dot files that are included in the documentation (see the
1868 # contain msc files that are included in the documentation (see the