home
readme
diff
tree
note
docs
0commit 080f729e1c6cfc322235397ff7f0f058d6b5fd1b
1Author: Mason Wright <mason@lakefox.net>
2Date: Sun Aug 3 15:27:55 2025 -0600
3
4 Docs update
5
6diff --git a/Makefile b/Makefile
7index 8433da7..5c2f5b2 100644
8--- a/Makefile
9+++ b/Makefile
10@@ -2,7 +2,7 @@
11 CCFLAGS = -Wall -Wextra -std=c++23 -g
12 CC = clang++
13
14-.PHONY: all clean run docs run_tests serve
15+.PHONY: all clean run docs serve
16
17 all: main
18
19@@ -50,8 +50,14 @@ clean:
20 run:
21 clear && ./main
22
23-docs:
24- cd docs/ && evoke build && cd ../../build && ./tracker.sh
25+MD_FILES := $(shell find docs/content -name "*.md")
26+HTML_FILES := $(MD_FILES:docs/content/%.md=docs/dist/%.html)
27+
28+docs: $(HTML_FILES)
29+ cd ../build && ./tracker.sh
30+
31+docs/dist/%.html: docs/content/%.md docs/components/navbar.html
32+ pandoc $< | template docs/components/navbar.html --stdin docs/template.html > $@
33
34 serve:
35 cd docs/dist && python3 -m http.server 8000
36diff --git a/config b/config
37deleted file mode 100644
38index 34b3cfa..0000000
39--- a/config
40+++ /dev/null
41@@ -1,2863 +0,0 @@
42-# Doxyfile 1.9.8
43-
44-# This file describes the settings to be used by the documentation system
45-# doxygen (www.doxygen.org) for a project.
46-#
47-# All text after a double hash (##) is considered a comment and is placed in
48-# front of the TAG it is preceding.
49-#
50-# All text after a single hash (#) is considered a comment and will be ignored.
51-# The format is:
52-# TAG = value [value, ...]
53-# For lists, items can also be appended using:
54-# TAG += value [value, ...]
55-# Values that contain spaces should be placed between quotes (\" \").
56-#
57-# Note:
58-#
59-# Use doxygen to compare the used configuration file with the template
60-# configuration file:
61-# doxygen -x [configFile]
62-# Use doxygen to compare the used configuration file with the template
63-# configuration file without replacing the environment variables or CMake type
64-# replacement variables:
65-# doxygen -x_noenv [configFile]
66-
67-#---------------------------------------------------------------------------
68-# Project related configuration options
69-#---------------------------------------------------------------------------
70-
71-# This tag specifies the encoding used for all characters in the configuration
72-# file that follow. The default is UTF-8 which is also the encoding used for all
73-# text before the first occurrence of this tag. Doxygen uses libiconv (or the
74-# iconv built into libc) for the transcoding. See
75-# https://www.gnu.org/software/libiconv/ for the list of possible encodings.
76-# The default value is: UTF-8.
77-
78-DOXYFILE_ENCODING = UTF-8
79-
80-# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
81-# double-quotes, unless you are using Doxywizard) that should identify the
82-# project for which the documentation is generated. This name is used in the
83-# title of most generated pages and in a few other places.
84-# The default value is: My Project.
85-
86-PROJECT_NAME = "Grim"
87-
88-# The PROJECT_NUMBER tag can be used to enter a project or revision number. This
89-# could be handy for archiving the generated documentation or if some version
90-# control system is used.
91-
92-PROJECT_NUMBER =
93-
94-# Using the PROJECT_BRIEF tag one can provide an optional one line description
95-# for a project that appears at the top of each page and should give viewer a
96-# quick idea about the purpose of the project. Keep the description short.
97-
98-PROJECT_BRIEF = "A HTML/CSS rendering engine"
99-
100-# With the PROJECT_LOGO tag one can specify a logo or an icon that is included
101-# in the documentation. The maximum height of the logo should not exceed 55
102-# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
103-# the logo to the output directory.
104-
105-PROJECT_LOGO =
106-
107-# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
108-# into which the generated documentation will be written. If a relative path is
109-# entered, it will be relative to the location where doxygen was started. If
110-# left blank the current directory will be used.
111-
112-OUTPUT_DIRECTORY = "docs/"
113-
114-# If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096
115-# sub-directories (in 2 levels) under the output directory of each output format
116-# and will distribute the generated files over these directories. Enabling this
117-# option can be useful when feeding doxygen a huge amount of source files, where
118-# putting all generated files in the same directory would otherwise causes
119-# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to
120-# control the number of sub-directories.
121-# The default value is: NO.
122-
123-CREATE_SUBDIRS = NO
124-
125-# Controls the number of sub-directories that will be created when
126-# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every
127-# level increment doubles the number of directories, resulting in 4096
128-# directories at level 8 which is the default and also the maximum value. The
129-# sub-directories are organized in 2 levels, the first level always has a fixed
130-# number of 16 directories.
131-# Minimum value: 0, maximum value: 8, default value: 8.
132-# This tag requires that the tag CREATE_SUBDIRS is set to YES.
133-
134-CREATE_SUBDIRS_LEVEL = 8
135-
136-# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
137-# characters to appear in the names of generated files. If set to NO, non-ASCII
138-# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
139-# U+3044.
140-# The default value is: NO.
141-
142-ALLOW_UNICODE_NAMES = NO
143-
144-# The OUTPUT_LANGUAGE tag is used to specify the language in which all
145-# documentation generated by doxygen is written. Doxygen will use this
146-# information to generate all constant output in the proper language.
147-# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian,
148-# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English
149-# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek,
150-# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with
151-# English messages), Korean, Korean-en (Korean with English messages), Latvian,
152-# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese,
153-# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,
154-# Swedish, Turkish, Ukrainian and Vietnamese.
155-# The default value is: English.
156-
157-OUTPUT_LANGUAGE = English
158-
159-# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
160-# descriptions after the members that are listed in the file and class
161-# documentation (similar to Javadoc). Set to NO to disable this.
162-# The default value is: YES.
163-
164-BRIEF_MEMBER_DESC = YES
165-
166-# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
167-# description of a member or function before the detailed description
168-#
169-# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
170-# brief descriptions will be completely suppressed.
171-# The default value is: YES.
172-
173-REPEAT_BRIEF = YES
174-
175-# This tag implements a quasi-intelligent brief description abbreviator that is
176-# used to form the text in various listings. Each string in this list, if found
177-# as the leading text of the brief description, will be stripped from the text
178-# and the result, after processing the whole list, is used as the annotated
179-# text. Otherwise, the brief description is used as-is. If left blank, the
180-# following values are used ($name is automatically replaced with the name of
181-# the entity):The $name class, The $name widget, The $name file, is, provides,
182-# specifies, contains, represents, a, an and the.
183-
184-ABBREVIATE_BRIEF = "The $name class" \
185- "The $name widget" \
186- "The $name file" \
187- is \
188- provides \
189- specifies \
190- contains \
191- represents \
192- a \
193- an \
194- the
195-
196-# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
197-# doxygen will generate a detailed section even if there is only a brief
198-# description.
199-# The default value is: NO.
200-
201-ALWAYS_DETAILED_SEC = NO
202-
203-# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
204-# inherited members of a class in the documentation of that class as if those
205-# members were ordinary class members. Constructors, destructors and assignment
206-# operators of the base classes will not be shown.
207-# The default value is: NO.
208-
209-INLINE_INHERITED_MEMB = NO
210-
211-# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
212-# before files name in the file list and in the header files. If set to NO the
213-# shortest path that makes the file name unique will be used
214-# The default value is: YES.
215-
216-FULL_PATH_NAMES = YES
217-
218-# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
219-# Stripping is only done if one of the specified strings matches the left-hand
220-# part of the path. The tag can be used to show relative paths in the file list.
221-# If left blank the directory from which doxygen is run is used as the path to
222-# strip.
223-#
224-# Note that you can specify absolute paths here, but also relative paths, which
225-# will be relative from the directory where doxygen is started.
226-# This tag requires that the tag FULL_PATH_NAMES is set to YES.
227-
228-STRIP_FROM_PATH =
229-
230-# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
231-# path mentioned in the documentation of a class, which tells the reader which
232-# header file to include in order to use a class. If left blank only the name of
233-# the header file containing the class definition is used. Otherwise one should
234-# specify the list of include paths that are normally passed to the compiler
235-# using the -I flag.
236-
237-STRIP_FROM_INC_PATH =
238-
239-# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
240-# less readable) file names. This can be useful is your file systems doesn't
241-# support long names like on DOS, Mac, or CD-ROM.
242-# The default value is: NO.
243-
244-SHORT_NAMES = NO
245-
246-# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
247-# first line (until the first dot) of a Javadoc-style comment as the brief
248-# description. If set to NO, the Javadoc-style will behave just like regular Qt-
249-# style comments (thus requiring an explicit @brief command for a brief
250-# description.)
251-# The default value is: NO.
252-
253-JAVADOC_AUTOBRIEF = NO
254-
255-# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
256-# such as
257-# /***************
258-# as being the beginning of a Javadoc-style comment "banner". If set to NO, the
259-# Javadoc-style will behave just like regular comments and it will not be
260-# interpreted by doxygen.
261-# The default value is: NO.
262-
263-JAVADOC_BANNER = NO
264-
265-# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
266-# line (until the first dot) of a Qt-style comment as the brief description. If
267-# set to NO, the Qt-style will behave just like regular Qt-style comments (thus
268-# requiring an explicit \brief command for a brief description.)
269-# The default value is: NO.
270-
271-QT_AUTOBRIEF = NO
272-
273-# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
274-# multi-line C++ special comment block (i.e. a block of //! or /// comments) as
275-# a brief description. This used to be the default behavior. The new default is
276-# to treat a multi-line C++ comment block as a detailed description. Set this
277-# tag to YES if you prefer the old behavior instead.
278-#
279-# Note that setting this tag to YES also means that rational rose comments are
280-# not recognized any more.
281-# The default value is: NO.
282-
283-MULTILINE_CPP_IS_BRIEF = NO
284-
285-# By default Python docstrings are displayed as preformatted text and doxygen's
286-# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the
287-# doxygen's special commands can be used and the contents of the docstring
288-# documentation blocks is shown as doxygen documentation.
289-# The default value is: YES.
290-
291-PYTHON_DOCSTRING = YES
292-
293-# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
294-# documentation from any documented member that it re-implements.
295-# The default value is: YES.
296-
297-INHERIT_DOCS = YES
298-
299-# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
300-# page for each member. If set to NO, the documentation of a member will be part
301-# of the file/class/namespace that contains it.
302-# The default value is: NO.
303-
304-SEPARATE_MEMBER_PAGES = NO
305-
306-# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
307-# uses this value to replace tabs by spaces in code fragments.
308-# Minimum value: 1, maximum value: 16, default value: 4.
309-
310-TAB_SIZE = 4
311-
312-# This tag can be used to specify a number of aliases that act as commands in
313-# the documentation. An alias has the form:
314-# name=value
315-# For example adding
316-# "sideeffect=@par Side Effects:^^"
317-# will allow you to put the command \sideeffect (or @sideeffect) in the
318-# documentation, which will result in a user-defined paragraph with heading
319-# "Side Effects:". Note that you cannot put \n's in the value part of an alias
320-# to insert newlines (in the resulting output). You can put ^^ in the value part
321-# of an alias to insert a newline as if a physical newline was in the original
322-# file. When you need a literal { or } or , in the value part of an alias you
323-# have to escape them by means of a backslash (\), this can lead to conflicts
324-# with the commands \{ and \} for these it is advised to use the version @{ and
325-# @} or use a double escape (\\{ and \\})
326-
327-ALIASES =
328-
329-# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
330-# only. Doxygen will then generate output that is more tailored for C. For
331-# instance, some of the names that are used will be different. The list of all
332-# members will be omitted, etc.
333-# The default value is: NO.
334-
335-OPTIMIZE_OUTPUT_FOR_C = NO
336-
337-# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
338-# Python sources only. Doxygen will then generate output that is more tailored
339-# for that language. For instance, namespaces will be presented as packages,
340-# qualified scopes will look different, etc.
341-# The default value is: NO.
342-
343-OPTIMIZE_OUTPUT_JAVA = NO
344-
345-# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
346-# sources. Doxygen will then generate output that is tailored for Fortran.
347-# The default value is: NO.
348-
349-OPTIMIZE_FOR_FORTRAN = NO
350-
351-# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
352-# sources. Doxygen will then generate output that is tailored for VHDL.
353-# The default value is: NO.
354-
355-OPTIMIZE_OUTPUT_VHDL = NO
356-
357-# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
358-# sources only. Doxygen will then generate output that is more tailored for that
359-# language. For instance, namespaces will be presented as modules, types will be
360-# separated into more groups, etc.
361-# The default value is: NO.
362-
363-OPTIMIZE_OUTPUT_SLICE = NO
364-
365-# Doxygen selects the parser to use depending on the extension of the files it
366-# parses. With this tag you can assign which parser to use for a given
367-# extension. Doxygen has a built-in mapping, but you can override or extend it
368-# using this tag. The format is ext=language, where ext is a file extension, and
369-# language is one of the parsers supported by doxygen: IDL, Java, JavaScript,
370-# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,
371-# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
372-# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
373-# tries to guess whether the code is fixed or free formatted code, this is the
374-# default for Fortran type files). For instance to make doxygen treat .inc files
375-# as Fortran files (default is PHP), and .f files as C (default is Fortran),
376-# use: inc=Fortran f=C.
377-#
378-# Note: For files without extension you can use no_extension as a placeholder.
379-#
380-# Note that for custom extensions you also need to set FILE_PATTERNS otherwise
381-# the files are not read by doxygen. When specifying no_extension you should add
382-# * to the FILE_PATTERNS.
383-#
384-# Note see also the list of default file extension mappings.
385-
386-EXTENSION_MAPPING =
387-
388-# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
389-# according to the Markdown format, which allows for more readable
390-# documentation. See https://daringfireball.net/projects/markdown/ for details.
391-# The output of markdown processing is further processed by doxygen, so you can
392-# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
393-# case of backward compatibilities issues.
394-# The default value is: YES.
395-
396-MARKDOWN_SUPPORT = YES
397-
398-# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
399-# to that level are automatically included in the table of contents, even if
400-# they do not have an id attribute.
401-# Note: This feature currently applies only to Markdown headings.
402-# Minimum value: 0, maximum value: 99, default value: 5.
403-# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
404-
405-TOC_INCLUDE_HEADINGS = 5
406-
407-# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to
408-# generate identifiers for the Markdown headings. Note: Every identifier is
409-# unique.
410-# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a
411-# sequence number starting at 0 and GITHUB use the lower case version of title
412-# with any whitespace replaced by '-' and punctuation characters removed.
413-# The default value is: DOXYGEN.
414-# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
415-
416-MARKDOWN_ID_STYLE = DOXYGEN
417-
418-# When enabled doxygen tries to link words that correspond to documented
419-# classes, or namespaces to their corresponding documentation. Such a link can
420-# be prevented in individual cases by putting a % sign in front of the word or
421-# globally by setting AUTOLINK_SUPPORT to NO.
422-# The default value is: YES.
423-
424-AUTOLINK_SUPPORT = YES
425-
426-# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
427-# to include (a tag file for) the STL sources as input, then you should set this
428-# tag to YES in order to let doxygen match functions declarations and
429-# definitions whose arguments contain STL classes (e.g. func(std::string);
430-# versus func(std::string) {}). This also make the inheritance and collaboration
431-# diagrams that involve STL classes more complete and accurate.
432-# The default value is: NO.
433-
434-BUILTIN_STL_SUPPORT = NO
435-
436-# If you use Microsoft's C++/CLI language, you should set this option to YES to
437-# enable parsing support.
438-# The default value is: NO.
439-
440-CPP_CLI_SUPPORT = NO
441-
442-# Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
443-# https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen
444-# will parse them like normal C++ but will assume all classes use public instead
445-# of private inheritance when no explicit protection keyword is present.
446-# The default value is: NO.
447-
448-SIP_SUPPORT = NO
449-
450-# For Microsoft's IDL there are propget and propput attributes to indicate
451-# getter and setter methods for a property. Setting this option to YES will make
452-# doxygen to replace the get and set methods by a property in the documentation.
453-# This will only work if the methods are indeed getting or setting a simple
454-# type. If this is not the case, or you want to show the methods anyway, you
455-# should set this option to NO.
456-# The default value is: YES.
457-
458-IDL_PROPERTY_SUPPORT = YES
459-
460-# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
461-# tag is set to YES then doxygen will reuse the documentation of the first
462-# member in the group (if any) for the other members of the group. By default
463-# all members of a group must be documented explicitly.
464-# The default value is: NO.
465-
466-DISTRIBUTE_GROUP_DOC = NO
467-
468-# If one adds a struct or class to a group and this option is enabled, then also
469-# any nested class or struct is added to the same group. By default this option
470-# is disabled and one has to add nested compounds explicitly via \ingroup.
471-# The default value is: NO.
472-
473-GROUP_NESTED_COMPOUNDS = NO
474-
475-# Set the SUBGROUPING tag to YES to allow class member groups of the same type
476-# (for instance a group of public functions) to be put as a subgroup of that
477-# type (e.g. under the Public Functions section). Set it to NO to prevent
478-# subgrouping. Alternatively, this can be done per class using the
479-# \nosubgrouping command.
480-# The default value is: YES.
481-
482-SUBGROUPING = YES
483-
484-# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
485-# are shown inside the group in which they are included (e.g. using \ingroup)
486-# instead of on a separate page (for HTML and Man pages) or section (for LaTeX
487-# and RTF).
488-#
489-# Note that this feature does not work in combination with
490-# SEPARATE_MEMBER_PAGES.
491-# The default value is: NO.
492-
493-INLINE_GROUPED_CLASSES = NO
494-
495-# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
496-# with only public data fields or simple typedef fields will be shown inline in
497-# the documentation of the scope in which they are defined (i.e. file,
498-# namespace, or group documentation), provided this scope is documented. If set
499-# to NO, structs, classes, and unions are shown on a separate page (for HTML and
500-# Man pages) or section (for LaTeX and RTF).
501-# The default value is: NO.
502-
503-INLINE_SIMPLE_STRUCTS = NO
504-
505-# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
506-# enum is documented as struct, union, or enum with the name of the typedef. So
507-# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
508-# with name TypeT. When disabled the typedef will appear as a member of a file,
509-# namespace, or class. And the struct will be named TypeS. This can typically be
510-# useful for C code in case the coding convention dictates that all compound
511-# types are typedef'ed and only the typedef is referenced, never the tag name.
512-# The default value is: NO.
513-
514-TYPEDEF_HIDES_STRUCT = NO
515-
516-# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
517-# cache is used to resolve symbols given their name and scope. Since this can be
518-# an expensive process and often the same symbol appears multiple times in the
519-# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
520-# doxygen will become slower. If the cache is too large, memory is wasted. The
521-# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
522-# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
523-# symbols. At the end of a run doxygen will report the cache usage and suggest
524-# the optimal cache size from a speed point of view.
525-# Minimum value: 0, maximum value: 9, default value: 0.
526-
527-LOOKUP_CACHE_SIZE = 0
528-
529-# The NUM_PROC_THREADS specifies the number of threads doxygen is allowed to use
530-# during processing. When set to 0 doxygen will based this on the number of
531-# cores available in the system. You can set it explicitly to a value larger
532-# than 0 to get more control over the balance between CPU load and processing
533-# speed. At this moment only the input processing can be done using multiple
534-# threads. Since this is still an experimental feature the default is set to 1,
535-# which effectively disables parallel processing. Please report any issues you
536-# encounter. Generating dot graphs in parallel is controlled by the
537-# DOT_NUM_THREADS setting.
538-# Minimum value: 0, maximum value: 32, default value: 1.
539-
540-NUM_PROC_THREADS = 1
541-
542-# If the TIMESTAMP tag is set different from NO then each generated page will
543-# contain the date or date and time when the page was generated. Setting this to
544-# NO can help when comparing the output of multiple runs.
545-# Possible values are: YES, NO, DATETIME and DATE.
546-# The default value is: NO.
547-
548-TIMESTAMP = NO
549-
550-#---------------------------------------------------------------------------
551-# Build related configuration options
552-#---------------------------------------------------------------------------
553-
554-# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
555-# documentation are documented, even if no documentation was available. Private
556-# class members and static file members will be hidden unless the
557-# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
558-# Note: This will also disable the warnings about undocumented members that are
559-# normally produced when WARNINGS is set to YES.
560-# The default value is: NO.
561-
562-EXTRACT_ALL = NO
563-
564-# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
565-# be included in the documentation.
566-# The default value is: NO.
567-
568-EXTRACT_PRIVATE = NO
569-
570-# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual
571-# methods of a class will be included in the documentation.
572-# The default value is: NO.
573-
574-EXTRACT_PRIV_VIRTUAL = NO
575-
576-# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
577-# scope will be included in the documentation.
578-# The default value is: NO.
579-
580-EXTRACT_PACKAGE = NO
581-
582-# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
583-# included in the documentation.
584-# The default value is: NO.
585-
586-EXTRACT_STATIC = NO
587-
588-# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
589-# locally in source files will be included in the documentation. If set to NO,
590-# only classes defined in header files are included. Does not have any effect
591-# for Java sources.
592-# The default value is: YES.
593-
594-EXTRACT_LOCAL_CLASSES = YES
595-
596-# This flag is only useful for Objective-C code. If set to YES, local methods,
597-# which are defined in the implementation section but not in the interface are
598-# included in the documentation. If set to NO, only methods in the interface are
599-# included.
600-# The default value is: NO.
601-
602-EXTRACT_LOCAL_METHODS = NO
603-
604-# If this flag is set to YES, the members of anonymous namespaces will be
605-# extracted and appear in the documentation as a namespace called
606-# 'anonymous_namespace{file}', where file will be replaced with the base name of
607-# the file that contains the anonymous namespace. By default anonymous namespace
608-# are hidden.
609-# The default value is: NO.
610-
611-EXTRACT_ANON_NSPACES = NO
612-
613-# If this flag is set to YES, the name of an unnamed parameter in a declaration
614-# will be determined by the corresponding definition. By default unnamed
615-# parameters remain unnamed in the output.
616-# The default value is: YES.
617-
618-RESOLVE_UNNAMED_PARAMS = YES
619-
620-# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
621-# undocumented members inside documented classes or files. If set to NO these
622-# members will be included in the various overviews, but no documentation
623-# section is generated. This option has no effect if EXTRACT_ALL is enabled.
624-# The default value is: NO.
625-
626-HIDE_UNDOC_MEMBERS = NO
627-
628-# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
629-# undocumented classes that are normally visible in the class hierarchy. If set
630-# to NO, these classes will be included in the various overviews. This option
631-# will also hide undocumented C++ concepts if enabled. This option has no effect
632-# if EXTRACT_ALL is enabled.
633-# The default value is: NO.
634-
635-HIDE_UNDOC_CLASSES = NO
636-
637-# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
638-# declarations. If set to NO, these declarations will be included in the
639-# documentation.
640-# The default value is: NO.
641-
642-HIDE_FRIEND_COMPOUNDS = NO
643-
644-# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
645-# documentation blocks found inside the body of a function. If set to NO, these
646-# blocks will be appended to the function's detailed documentation block.
647-# The default value is: NO.
648-
649-HIDE_IN_BODY_DOCS = NO
650-
651-# The INTERNAL_DOCS tag determines if documentation that is typed after a
652-# \internal command is included. If the tag is set to NO then the documentation
653-# will be excluded. Set it to YES to include the internal documentation.
654-# The default value is: NO.
655-
656-INTERNAL_DOCS = NO
657-
658-# With the correct setting of option CASE_SENSE_NAMES doxygen will better be
659-# able to match the capabilities of the underlying filesystem. In case the
660-# filesystem is case sensitive (i.e. it supports files in the same directory
661-# whose names only differ in casing), the option must be set to YES to properly
662-# deal with such files in case they appear in the input. For filesystems that
663-# are not case sensitive the option should be set to NO to properly deal with
664-# output files written for symbols that only differ in casing, such as for two
665-# classes, one named CLASS and the other named Class, and to also support
666-# references to files without having to specify the exact matching casing. On
667-# Windows (including Cygwin) and MacOS, users should typically set this option
668-# to NO, whereas on Linux or other Unix flavors it should typically be set to
669-# YES.
670-# Possible values are: SYSTEM, NO and YES.
671-# The default value is: SYSTEM.
672-
673-CASE_SENSE_NAMES = SYSTEM
674-
675-# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
676-# their full class and namespace scopes in the documentation. If set to YES, the
677-# scope will be hidden.
678-# The default value is: NO.
679-
680-HIDE_SCOPE_NAMES = NO
681-
682-# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
683-# append additional text to a page's title, such as Class Reference. If set to
684-# YES the compound reference will be hidden.
685-# The default value is: NO.
686-
687-HIDE_COMPOUND_REFERENCE= NO
688-
689-# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class
690-# will show which file needs to be included to use the class.
691-# The default value is: YES.
692-
693-SHOW_HEADERFILE = YES
694-
695-# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
696-# the files that are included by a file in the documentation of that file.
697-# The default value is: YES.
698-
699-SHOW_INCLUDE_FILES = YES
700-
701-# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
702-# grouped member an include statement to the documentation, telling the reader
703-# which file to include in order to use the member.
704-# The default value is: NO.
705-
706-SHOW_GROUPED_MEMB_INC = NO
707-
708-# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
709-# files with double quotes in the documentation rather than with sharp brackets.
710-# The default value is: NO.
711-
712-FORCE_LOCAL_INCLUDES = NO
713-
714-# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
715-# documentation for inline members.
716-# The default value is: YES.
717-
718-INLINE_INFO = YES
719-
720-# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
721-# (detailed) documentation of file and class members alphabetically by member
722-# name. If set to NO, the members will appear in declaration order.
723-# The default value is: YES.
724-
725-SORT_MEMBER_DOCS = YES
726-
727-# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
728-# descriptions of file, namespace and class members alphabetically by member
729-# name. If set to NO, the members will appear in declaration order. Note that
730-# this will also influence the order of the classes in the class list.
731-# The default value is: NO.
732-
733-SORT_BRIEF_DOCS = NO
734-
735-# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
736-# (brief and detailed) documentation of class members so that constructors and
737-# destructors are listed first. If set to NO the constructors will appear in the
738-# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
739-# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
740-# member documentation.
741-# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
742-# detailed member documentation.
743-# The default value is: NO.
744-
745-SORT_MEMBERS_CTORS_1ST = NO
746-
747-# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
748-# of group names into alphabetical order. If set to NO the group names will
749-# appear in their defined order.
750-# The default value is: NO.
751-
752-SORT_GROUP_NAMES = NO
753-
754-# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
755-# fully-qualified names, including namespaces. If set to NO, the class list will
756-# be sorted only by class name, not including the namespace part.
757-# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
758-# Note: This option applies only to the class list, not to the alphabetical
759-# list.
760-# The default value is: NO.
761-
762-SORT_BY_SCOPE_NAME = NO
763-
764-# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
765-# type resolution of all parameters of a function it will reject a match between
766-# the prototype and the implementation of a member function even if there is
767-# only one candidate or it is obvious which candidate to choose by doing a
768-# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
769-# accept a match between prototype and implementation in such cases.
770-# The default value is: NO.
771-
772-STRICT_PROTO_MATCHING = NO
773-
774-# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
775-# list. This list is created by putting \todo commands in the documentation.
776-# The default value is: YES.
777-
778-GENERATE_TODOLIST = YES
779-
780-# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
781-# list. This list is created by putting \test commands in the documentation.
782-# The default value is: YES.
783-
784-GENERATE_TESTLIST = YES
785-
786-# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
787-# list. This list is created by putting \bug commands in the documentation.
788-# The default value is: YES.
789-
790-GENERATE_BUGLIST = YES
791-
792-# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
793-# the deprecated list. This list is created by putting \deprecated commands in
794-# the documentation.
795-# The default value is: YES.
796-
797-GENERATE_DEPRECATEDLIST= YES
798-
799-# The ENABLED_SECTIONS tag can be used to enable conditional documentation
800-# sections, marked by \if <section_label> ... \endif and \cond <section_label>
801-# ... \endcond blocks.
802-
803-ENABLED_SECTIONS =
804-
805-# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
806-# initial value of a variable or macro / define can have for it to appear in the
807-# documentation. If the initializer consists of more lines than specified here
808-# it will be hidden. Use a value of 0 to hide initializers completely. The
809-# appearance of the value of individual variables and macros / defines can be
810-# controlled using \showinitializer or \hideinitializer command in the
811-# documentation regardless of this setting.
812-# Minimum value: 0, maximum value: 10000, default value: 30.
813-
814-MAX_INITIALIZER_LINES = 30
815-
816-# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
817-# the bottom of the documentation of classes and structs. If set to YES, the
818-# list will mention the files that were used to generate the documentation.
819-# The default value is: YES.
820-
821-SHOW_USED_FILES = YES
822-
823-# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
824-# will remove the Files entry from the Quick Index and from the Folder Tree View
825-# (if specified).
826-# The default value is: YES.
827-
828-SHOW_FILES = YES
829-
830-# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
831-# page. This will remove the Namespaces entry from the Quick Index and from the
832-# Folder Tree View (if specified).
833-# The default value is: YES.
834-
835-SHOW_NAMESPACES = YES
836-
837-# The FILE_VERSION_FILTER tag can be used to specify a program or script that
838-# doxygen should invoke to get the current version for each file (typically from
839-# the version control system). Doxygen will invoke the program by executing (via
840-# popen()) the command command input-file, where command is the value of the
841-# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
842-# by doxygen. Whatever the program writes to standard output is used as the file
843-# version. For an example see the documentation.
844-
845-FILE_VERSION_FILTER =
846-
847-# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
848-# by doxygen. The layout file controls the global structure of the generated
849-# output files in an output format independent way. To create the layout file
850-# that represents doxygen's defaults, run doxygen with the -l option. You can
851-# optionally specify a file name after the option, if omitted DoxygenLayout.xml
852-# will be used as the name of the layout file. See also section "Changing the
853-# layout of pages" for information.
854-#
855-# Note that if you run doxygen from a directory containing a file called
856-# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
857-# tag is left empty.
858-
859-LAYOUT_FILE =
860-
861-# The CITE_BIB_FILES tag can be used to specify one or more bib files containing
862-# the reference definitions. This must be a list of .bib files. The .bib
863-# extension is automatically appended if omitted. This requires the bibtex tool
864-# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
865-# For LaTeX the style of the bibliography can be controlled using
866-# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
867-# search path. See also \cite for info how to create references.
868-
869-CITE_BIB_FILES =
870-
871-#---------------------------------------------------------------------------
872-# Configuration options related to warning and progress messages
873-#---------------------------------------------------------------------------
874-
875-# The QUIET tag can be used to turn on/off the messages that are generated to
876-# standard output by doxygen. If QUIET is set to YES this implies that the
877-# messages are off.
878-# The default value is: NO.
879-
880-QUIET = NO
881-
882-# The WARNINGS tag can be used to turn on/off the warning messages that are
883-# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
884-# this implies that the warnings are on.
885-#
886-# Tip: Turn warnings on while writing the documentation.
887-# The default value is: YES.
888-
889-WARNINGS = YES
890-
891-# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
892-# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
893-# will automatically be disabled.
894-# The default value is: YES.
895-
896-WARN_IF_UNDOCUMENTED = YES
897-
898-# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
899-# potential errors in the documentation, such as documenting some parameters in
900-# a documented function twice, or documenting parameters that don't exist or
901-# using markup commands wrongly.
902-# The default value is: YES.
903-
904-WARN_IF_DOC_ERROR = YES
905-
906-# If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete
907-# function parameter documentation. If set to NO, doxygen will accept that some
908-# parameters have no documentation without warning.
909-# The default value is: YES.
910-
911-WARN_IF_INCOMPLETE_DOC = YES
912-
913-# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
914-# are documented, but have no documentation for their parameters or return
915-# value. If set to NO, doxygen will only warn about wrong parameter
916-# documentation, but not about the absence of documentation. If EXTRACT_ALL is
917-# set to YES then this flag will automatically be disabled. See also
918-# WARN_IF_INCOMPLETE_DOC
919-# The default value is: NO.
920-
921-WARN_NO_PARAMDOC = NO
922-
923-# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, doxygen will warn about
924-# undocumented enumeration values. If set to NO, doxygen will accept
925-# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag
926-# will automatically be disabled.
927-# The default value is: NO.
928-
929-WARN_IF_UNDOC_ENUM_VAL = NO
930-
931-# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
932-# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS
933-# then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but
934-# at the end of the doxygen process doxygen will return with a non-zero status.
935-# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then doxygen behaves
936-# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined doxygen will not
937-# write the warning messages in between other messages but write them at the end
938-# of a run, in case a WARN_LOGFILE is defined the warning messages will be
939-# besides being in the defined file also be shown at the end of a run, unless
940-# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case
941-# the behavior will remain as with the setting FAIL_ON_WARNINGS.
942-# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT.
943-# The default value is: NO.
944-
945-WARN_AS_ERROR = NO
946-
947-# The WARN_FORMAT tag determines the format of the warning messages that doxygen
948-# can produce. The string should contain the $file, $line, and $text tags, which
949-# will be replaced by the file and line number from which the warning originated
950-# and the warning text. Optionally the format may contain $version, which will
951-# be replaced by the version of the file (if it could be obtained via
952-# FILE_VERSION_FILTER)
953-# See also: WARN_LINE_FORMAT
954-# The default value is: $file:$line: $text.
955-
956-WARN_FORMAT = "$file:$line: $text"
957-
958-# In the $text part of the WARN_FORMAT command it is possible that a reference
959-# to a more specific place is given. To make it easier to jump to this place
960-# (outside of doxygen) the user can define a custom "cut" / "paste" string.
961-# Example:
962-# WARN_LINE_FORMAT = "'vi $file +$line'"
963-# See also: WARN_FORMAT
964-# The default value is: at line $line of file $file.
965-
966-WARN_LINE_FORMAT = "at line $line of file $file"
967-
968-# The WARN_LOGFILE tag can be used to specify a file to which warning and error
969-# messages should be written. If left blank the output is written to standard
970-# error (stderr). In case the file specified cannot be opened for writing the
971-# warning and error messages are written to standard error. When as file - is
972-# specified the warning and error messages are written to standard output
973-# (stdout).
974-
975-WARN_LOGFILE =
976-
977-#---------------------------------------------------------------------------
978-# Configuration options related to the input files
979-#---------------------------------------------------------------------------
980-
981-# The INPUT tag is used to specify the files and/or directories that contain
982-# documented source files. You may enter file names like myfile.cpp or
983-# directories like /usr/src/myproject. Separate the files or directories with
984-# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
985-# Note: If this tag is empty the current directory is searched.
986-
987-INPUT =
988-
989-# This tag can be used to specify the character encoding of the source files
990-# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
991-# libiconv (or the iconv built into libc) for the transcoding. See the libiconv
992-# documentation (see:
993-# https://www.gnu.org/software/libiconv/) for the list of possible encodings.
994-# See also: INPUT_FILE_ENCODING
995-# The default value is: UTF-8.
996-
997-INPUT_ENCODING = UTF-8
998-
999-# This tag can be used to specify the character encoding of the source files
1000-# that doxygen parses The INPUT_FILE_ENCODING tag can be used to specify
1001-# character encoding on a per file pattern basis. Doxygen will compare the file
1002-# name with each pattern and apply the encoding instead of the default
1003-# INPUT_ENCODING) if there is a match. The character encodings are a list of the
1004-# form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding
1005-# "INPUT_ENCODING" for further information on supported encodings.
1006-
1007-INPUT_FILE_ENCODING =
1008-
1009-# If the value of the INPUT tag contains directories, you can use the
1010-# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
1011-# *.h) to filter out the source-files in the directories.
1012-#
1013-# Note that for custom extensions or not directly supported extensions you also
1014-# need to set EXTENSION_MAPPING for the extension otherwise the files are not
1015-# read by doxygen.
1016-#
1017-# Note the list of default checked file patterns might differ from the list of
1018-# default file extension mappings.
1019-#
1020-# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,
1021-# *.cpp, *.cppm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl,
1022-# *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.ixx, *.l, *.cs, *.d, *.php,
1023-# *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be
1024-# provided as doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,
1025-# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.
1026-
1027-FILE_PATTERNS = *.c \
1028- *.cc \
1029- *.cxx \
1030- *.cxxm \
1031- *.cpp \
1032- *.cppm \
1033- *.c++ \
1034- *.c++m \
1035- *.java \
1036- *.ii \
1037- *.ixx \
1038- *.ipp \
1039- *.i++ \
1040- *.inl \
1041- *.idl \
1042- *.ddl \
1043- *.odl \
1044- *.h \
1045- *.hh \
1046- *.hxx \
1047- *.hpp \
1048- *.h++ \
1049- *.ixx \
1050- *.l \
1051- *.cs \
1052- *.d \
1053- *.php \
1054- *.php4 \
1055- *.php5 \
1056- *.phtml \
1057- *.inc \
1058- *.m \
1059- *.markdown \
1060- *.md \
1061- *.mm \
1062- *.dox \
1063- *.py \
1064- *.pyw \
1065- *.f90 \
1066- *.f95 \
1067- *.f03 \
1068- *.f08 \
1069- *.f18 \
1070- *.f \
1071- *.for \
1072- *.vhd \
1073- *.vhdl \
1074- *.ucf \
1075- *.qsf \
1076- *.ice
1077-
1078-# The RECURSIVE tag can be used to specify whether or not subdirectories should
1079-# be searched for input files as well.
1080-# The default value is: NO.
1081-
1082-RECURSIVE = NO
1083-
1084-# The EXCLUDE tag can be used to specify files and/or directories that should be
1085-# excluded from the INPUT source files. This way you can easily exclude a
1086-# subdirectory from a directory tree whose root is specified with the INPUT tag.
1087-#
1088-# Note that relative paths are relative to the directory from which doxygen is
1089-# run.
1090-
1091-EXCLUDE =
1092-
1093-# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
1094-# directories that are symbolic links (a Unix file system feature) are excluded
1095-# from the input.
1096-# The default value is: NO.
1097-
1098-EXCLUDE_SYMLINKS = NO
1099-
1100-# If the value of the INPUT tag contains directories, you can use the
1101-# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1102-# certain files from those directories.
1103-#
1104-# Note that the wildcards are matched against the file with absolute path, so to
1105-# exclude all test directories for example use the pattern */test/*
1106-
1107-EXCLUDE_PATTERNS =
1108-
1109-# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
1110-# (namespaces, classes, functions, etc.) that should be excluded from the
1111-# output. The symbol name can be a fully qualified name, a word, or if the
1112-# wildcard * is used, a substring. Examples: ANamespace, AClass,
1113-# ANamespace::AClass, ANamespace::*Test
1114-
1115-EXCLUDE_SYMBOLS =
1116-
1117-# The EXAMPLE_PATH tag can be used to specify one or more files or directories
1118-# that contain example code fragments that are included (see the \include
1119-# command).
1120-
1121-EXAMPLE_PATH =
1122-
1123-# If the value of the EXAMPLE_PATH tag contains directories, you can use the
1124-# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
1125-# *.h) to filter out the source-files in the directories. If left blank all
1126-# files are included.
1127-
1128-EXAMPLE_PATTERNS = *
1129-
1130-# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
1131-# searched for input files to be used with the \include or \dontinclude commands
1132-# irrespective of the value of the RECURSIVE tag.
1133-# The default value is: NO.
1134-
1135-EXAMPLE_RECURSIVE = NO
1136-
1137-# The IMAGE_PATH tag can be used to specify one or more files or directories
1138-# that contain images that are to be included in the documentation (see the
1139-# \image command).
1140-
1141-IMAGE_PATH =
1142-
1143-# The INPUT_FILTER tag can be used to specify a program that doxygen should
1144-# invoke to filter for each input file. Doxygen will invoke the filter program
1145-# by executing (via popen()) the command:
1146-#
1147-# <filter> <input-file>
1148-#
1149-# where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1150-# name of an input file. Doxygen will then use the output that the filter
1151-# program writes to standard output. If FILTER_PATTERNS is specified, this tag
1152-# will be ignored.
1153-#
1154-# Note that the filter must not add or remove lines; it is applied before the
1155-# code is scanned, but not when the output code is generated. If lines are added
1156-# or removed, the anchors will not be placed correctly.
1157-#
1158-# Note that doxygen will use the data processed and written to standard output
1159-# for further processing, therefore nothing else, like debug statements or used
1160-# commands (so in case of a Windows batch file always use @echo OFF), should be
1161-# written to standard output.
1162-#
1163-# Note that for custom extensions or not directly supported extensions you also
1164-# need to set EXTENSION_MAPPING for the extension otherwise the files are not
1165-# properly processed by doxygen.
1166-
1167-INPUT_FILTER =
1168-
1169-# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1170-# basis. Doxygen will compare the file name with each pattern and apply the
1171-# filter if there is a match. The filters are a list of the form: pattern=filter
1172-# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
1173-# filters are used. If the FILTER_PATTERNS tag is empty or if none of the
1174-# patterns match the file name, INPUT_FILTER is applied.
1175-#
1176-# Note that for custom extensions or not directly supported extensions you also
1177-# need to set EXTENSION_MAPPING for the extension otherwise the files are not
1178-# properly processed by doxygen.
1179-
1180-FILTER_PATTERNS =
1181-
1182-# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1183-# INPUT_FILTER) will also be used to filter the input files that are used for
1184-# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
1185-# The default value is: NO.
1186-
1187-FILTER_SOURCE_FILES = NO
1188-
1189-# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
1190-# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
1191-# it is also possible to disable source filtering for a specific pattern using
1192-# *.ext= (so without naming a filter).
1193-# This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
1194-
1195-FILTER_SOURCE_PATTERNS =
1196-
1197-# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1198-# is part of the input, its contents will be placed on the main page
1199-# (index.html). This can be useful if you have a project on for instance GitHub
1200-# and want to reuse the introduction page also for the doxygen output.
1201-
1202-USE_MDFILE_AS_MAINPAGE =
1203-
1204-# The Fortran standard specifies that for fixed formatted Fortran code all
1205-# characters from position 72 are to be considered as comment. A common
1206-# extension is to allow longer lines before the automatic comment starts. The
1207-# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can
1208-# be processed before the automatic comment starts.
1209-# Minimum value: 7, maximum value: 10000, default value: 72.
1210-
1211-FORTRAN_COMMENT_AFTER = 72
1212-
1213-#---------------------------------------------------------------------------
1214-# Configuration options related to source browsing
1215-#---------------------------------------------------------------------------
1216-
1217-# If the SOURCE_BROWSER tag is set to YES then a list of source files will be
1218-# generated. Documented entities will be cross-referenced with these sources.
1219-#
1220-# Note: To get rid of all source code in the generated output, make sure that
1221-# also VERBATIM_HEADERS is set to NO.
1222-# The default value is: NO.
1223-
1224-SOURCE_BROWSER = NO
1225-
1226-# Setting the INLINE_SOURCES tag to YES will include the body of functions,
1227-# classes and enums directly into the documentation.
1228-# The default value is: NO.
1229-
1230-INLINE_SOURCES = NO
1231-
1232-# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
1233-# special comment blocks from generated source code fragments. Normal C, C++ and
1234-# Fortran comments will always remain visible.
1235-# The default value is: YES.
1236-
1237-STRIP_CODE_COMMENTS = YES
1238-
1239-# If the REFERENCED_BY_RELATION tag is set to YES then for each documented
1240-# entity all documented functions referencing it will be listed.
1241-# The default value is: NO.
1242-
1243-REFERENCED_BY_RELATION = NO
1244-
1245-# If the REFERENCES_RELATION tag is set to YES then for each documented function
1246-# all documented entities called/used by that function will be listed.
1247-# The default value is: NO.
1248-
1249-REFERENCES_RELATION = NO
1250-
1251-# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
1252-# to YES then the hyperlinks from functions in REFERENCES_RELATION and
1253-# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1254-# link to the documentation.
1255-# The default value is: YES.
1256-
1257-REFERENCES_LINK_SOURCE = YES
1258-
1259-# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1260-# source code will show a tooltip with additional information such as prototype,
1261-# brief description and links to the definition and documentation. Since this
1262-# will make the HTML file larger and loading of large files a bit slower, you
1263-# can opt to disable this feature.
1264-# The default value is: YES.
1265-# This tag requires that the tag SOURCE_BROWSER is set to YES.
1266-
1267-SOURCE_TOOLTIPS = YES
1268-
1269-# If the USE_HTAGS tag is set to YES then the references to source code will
1270-# point to the HTML generated by the htags(1) tool instead of doxygen built-in
1271-# source browser. The htags tool is part of GNU's global source tagging system
1272-# (see https://www.gnu.org/software/global/global.html). You will need version
1273-# 4.8.6 or higher.
1274-#
1275-# To use it do the following:
1276-# - Install the latest version of global
1277-# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1278-# - Make sure the INPUT points to the root of the source tree
1279-# - Run doxygen as normal
1280-#
1281-# Doxygen will invoke htags (and that will in turn invoke gtags), so these
1282-# tools must be available from the command line (i.e. in the search path).
1283-#
1284-# The result: instead of the source browser generated by doxygen, the links to
1285-# source code will now point to the output of htags.
1286-# The default value is: NO.
1287-# This tag requires that the tag SOURCE_BROWSER is set to YES.
1288-
1289-USE_HTAGS = NO
1290-
1291-# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1292-# verbatim copy of the header file for each class for which an include is
1293-# specified. Set to NO to disable this.
1294-# See also: Section \class.
1295-# The default value is: YES.
1296-
1297-VERBATIM_HEADERS = YES
1298-
1299-# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the
1300-# clang parser (see:
1301-# http://clang.llvm.org/) for more accurate parsing at the cost of reduced
1302-# performance. This can be particularly helpful with template rich C++ code for
1303-# which doxygen's built-in parser lacks the necessary type information.
1304-# Note: The availability of this option depends on whether or not doxygen was
1305-# generated with the -Duse_libclang=ON option for CMake.
1306-# The default value is: NO.
1307-
1308-CLANG_ASSISTED_PARSING = NO
1309-
1310-# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS
1311-# tag is set to YES then doxygen will add the directory of each input to the
1312-# include path.
1313-# The default value is: YES.
1314-# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
1315-
1316-CLANG_ADD_INC_PATHS = YES
1317-
1318-# If clang assisted parsing is enabled you can provide the compiler with command
1319-# line options that you would normally use when invoking the compiler. Note that
1320-# the include paths will already be set by doxygen for the files and directories
1321-# specified with INPUT and INCLUDE_PATH.
1322-# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
1323-
1324-CLANG_OPTIONS =
1325-
1326-# If clang assisted parsing is enabled you can provide the clang parser with the
1327-# path to the directory containing a file called compile_commands.json. This
1328-# file is the compilation database (see:
1329-# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the
1330-# options used when the source files were built. This is equivalent to
1331-# specifying the -p option to a clang tool, such as clang-check. These options
1332-# will then be passed to the parser. Any options specified with CLANG_OPTIONS
1333-# will be added as well.
1334-# Note: The availability of this option depends on whether or not doxygen was
1335-# generated with the -Duse_libclang=ON option for CMake.
1336-
1337-CLANG_DATABASE_PATH =
1338-
1339-#---------------------------------------------------------------------------
1340-# Configuration options related to the alphabetical class index
1341-#---------------------------------------------------------------------------
1342-
1343-# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
1344-# compounds will be generated. Enable this if the project contains a lot of
1345-# classes, structs, unions or interfaces.
1346-# The default value is: YES.
1347-
1348-ALPHABETICAL_INDEX = YES
1349-
1350-# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)
1351-# that should be ignored while generating the index headers. The IGNORE_PREFIX
1352-# tag works for classes, function and member names. The entity will be placed in
1353-# the alphabetical list under the first letter of the entity name that remains
1354-# after removing the prefix.
1355-# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1356-
1357-IGNORE_PREFIX =
1358-
1359-#---------------------------------------------------------------------------
1360-# Configuration options related to the HTML output
1361-#---------------------------------------------------------------------------
1362-
1363-# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
1364-# The default value is: YES.
1365-
1366-GENERATE_HTML = YES
1367-
1368-# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1369-# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1370-# it.
1371-# The default directory is: html.
1372-# This tag requires that the tag GENERATE_HTML is set to YES.
1373-
1374-HTML_OUTPUT = html
1375-
1376-# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1377-# generated HTML page (for example: .htm, .php, .asp).
1378-# The default value is: .html.
1379-# This tag requires that the tag GENERATE_HTML is set to YES.
1380-
1381-HTML_FILE_EXTENSION = .html
1382-
1383-# The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1384-# each generated HTML page. If the tag is left blank doxygen will generate a
1385-# standard header.
1386-#
1387-# To get valid HTML the header file that includes any scripts and style sheets
1388-# that doxygen needs, which is dependent on the configuration options used (e.g.
1389-# the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1390-# default header using
1391-# doxygen -w html new_header.html new_footer.html new_stylesheet.css
1392-# YourConfigFile
1393-# and then modify the file new_header.html. See also section "Doxygen usage"
1394-# for information on how to generate the default header that doxygen normally
1395-# uses.
1396-# Note: The header is subject to change so you typically have to regenerate the
1397-# default header when upgrading to a newer version of doxygen. For a description
1398-# of the possible markers and block names see the documentation.
1399-# This tag requires that the tag GENERATE_HTML is set to YES.
1400-
1401-HTML_HEADER =
1402-
1403-# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1404-# generated HTML page. If the tag is left blank doxygen will generate a standard
1405-# footer. See HTML_HEADER for more information on how to generate a default
1406-# footer and what special commands can be used inside the footer. See also
1407-# section "Doxygen usage" for information on how to generate the default footer
1408-# that doxygen normally uses.
1409-# This tag requires that the tag GENERATE_HTML is set to YES.
1410-
1411-HTML_FOOTER =
1412-
1413-# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1414-# sheet that is used by each HTML page. It can be used to fine-tune the look of
1415-# the HTML output. If left blank doxygen will generate a default style sheet.
1416-# See also section "Doxygen usage" for information on how to generate the style
1417-# sheet that doxygen normally uses.
1418-# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1419-# it is more robust and this tag (HTML_STYLESHEET) will in the future become
1420-# obsolete.
1421-# This tag requires that the tag GENERATE_HTML is set to YES.
1422-
1423-HTML_STYLESHEET =
1424-
1425-# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1426-# cascading style sheets that are included after the standard style sheets
1427-# created by doxygen. Using this option one can overrule certain style aspects.
1428-# This is preferred over using HTML_STYLESHEET since it does not replace the
1429-# standard style sheet and is therefore more robust against future updates.
1430-# Doxygen will copy the style sheet files to the output directory.
1431-# Note: The order of the extra style sheet files is of importance (e.g. the last
1432-# style sheet in the list overrules the setting of the previous ones in the
1433-# list).
1434-# Note: Since the styling of scrollbars can currently not be overruled in
1435-# Webkit/Chromium, the styling will be left out of the default doxygen.css if
1436-# one or more extra stylesheets have been specified. So if scrollbar
1437-# customization is desired it has to be added explicitly. For an example see the
1438-# documentation.
1439-# This tag requires that the tag GENERATE_HTML is set to YES.
1440-
1441-HTML_EXTRA_STYLESHEET =
1442-
1443-# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1444-# other source files which should be copied to the HTML output directory. Note
1445-# that these files will be copied to the base HTML output directory. Use the
1446-# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1447-# files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1448-# files will be copied as-is; there are no commands or markers available.
1449-# This tag requires that the tag GENERATE_HTML is set to YES.
1450-
1451-HTML_EXTRA_FILES =
1452-
1453-# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output
1454-# should be rendered with a dark or light theme.
1455-# Possible values are: LIGHT always generate light mode output, DARK always
1456-# generate dark mode output, AUTO_LIGHT automatically set the mode according to
1457-# the user preference, use light mode if no preference is set (the default),
1458-# AUTO_DARK automatically set the mode according to the user preference, use
1459-# dark mode if no preference is set and TOGGLE allow to user to switch between
1460-# light and dark mode via a button.
1461-# The default value is: AUTO_LIGHT.
1462-# This tag requires that the tag GENERATE_HTML is set to YES.
1463-
1464-HTML_COLORSTYLE = AUTO_LIGHT
1465-
1466-# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1467-# will adjust the colors in the style sheet and background images according to
1468-# this color. Hue is specified as an angle on a color-wheel, see
1469-# https://en.wikipedia.org/wiki/Hue for more information. For instance the value
1470-# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1471-# purple, and 360 is red again.
1472-# Minimum value: 0, maximum value: 359, default value: 220.
1473-# This tag requires that the tag GENERATE_HTML is set to YES.
1474-
1475-HTML_COLORSTYLE_HUE = 220
1476-
1477-# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1478-# in the HTML output. For a value of 0 the output will use gray-scales only. A
1479-# value of 255 will produce the most vivid colors.
1480-# Minimum value: 0, maximum value: 255, default value: 100.
1481-# This tag requires that the tag GENERATE_HTML is set to YES.
1482-
1483-HTML_COLORSTYLE_SAT = 100
1484-
1485-# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1486-# luminance component of the colors in the HTML output. Values below 100
1487-# gradually make the output lighter, whereas values above 100 make the output
1488-# darker. The value divided by 100 is the actual gamma applied, so 80 represents
1489-# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1490-# change the gamma.
1491-# Minimum value: 40, maximum value: 240, default value: 80.
1492-# This tag requires that the tag GENERATE_HTML is set to YES.
1493-
1494-HTML_COLORSTYLE_GAMMA = 80
1495-
1496-# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
1497-# documentation will contain a main index with vertical navigation menus that
1498-# are dynamically created via JavaScript. If disabled, the navigation index will
1499-# consists of multiple levels of tabs that are statically embedded in every HTML
1500-# page. Disable this option to support browsers that do not have JavaScript,
1501-# like the Qt help browser.
1502-# The default value is: YES.
1503-# This tag requires that the tag GENERATE_HTML is set to YES.
1504-
1505-HTML_DYNAMIC_MENUS = YES
1506-
1507-# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1508-# documentation will contain sections that can be hidden and shown after the
1509-# page has loaded.
1510-# The default value is: NO.
1511-# This tag requires that the tag GENERATE_HTML is set to YES.
1512-
1513-HTML_DYNAMIC_SECTIONS = NO
1514-
1515-# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be
1516-# dynamically folded and expanded in the generated HTML source code.
1517-# The default value is: YES.
1518-# This tag requires that the tag GENERATE_HTML is set to YES.
1519-
1520-HTML_CODE_FOLDING = YES
1521-
1522-# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1523-# shown in the various tree structured indices initially; the user can expand
1524-# and collapse entries dynamically later on. Doxygen will expand the tree to
1525-# such a level that at most the specified number of entries are visible (unless
1526-# a fully collapsed tree already exceeds this amount). So setting the number of
1527-# entries 1 will produce a full collapsed tree by default. 0 is a special value
1528-# representing an infinite number of entries and will result in a full expanded
1529-# tree by default.
1530-# Minimum value: 0, maximum value: 9999, default value: 100.
1531-# This tag requires that the tag GENERATE_HTML is set to YES.
1532-
1533-HTML_INDEX_NUM_ENTRIES = 100
1534-
1535-# If the GENERATE_DOCSET tag is set to YES, additional index files will be
1536-# generated that can be used as input for Apple's Xcode 3 integrated development
1537-# environment (see:
1538-# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To
1539-# create a documentation set, doxygen will generate a Makefile in the HTML
1540-# output directory. Running make will produce the docset in that directory and
1541-# running make install will install the docset in
1542-# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1543-# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
1544-# genXcode/_index.html for more information.
1545-# The default value is: NO.
1546-# This tag requires that the tag GENERATE_HTML is set to YES.
1547-
1548-GENERATE_DOCSET = NO
1549-
1550-# This tag determines the name of the docset feed. A documentation feed provides
1551-# an umbrella under which multiple documentation sets from a single provider
1552-# (such as a company or product suite) can be grouped.
1553-# The default value is: Doxygen generated docs.
1554-# This tag requires that the tag GENERATE_DOCSET is set to YES.
1555-
1556-DOCSET_FEEDNAME = "Doxygen generated docs"
1557-
1558-# This tag determines the URL of the docset feed. A documentation feed provides
1559-# an umbrella under which multiple documentation sets from a single provider
1560-# (such as a company or product suite) can be grouped.
1561-# This tag requires that the tag GENERATE_DOCSET is set to YES.
1562-
1563-DOCSET_FEEDURL =
1564-
1565-# This tag specifies a string that should uniquely identify the documentation
1566-# set bundle. This should be a reverse domain-name style string, e.g.
1567-# com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1568-# The default value is: org.doxygen.Project.
1569-# This tag requires that the tag GENERATE_DOCSET is set to YES.
1570-
1571-DOCSET_BUNDLE_ID = org.doxygen.Project
1572-
1573-# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1574-# the documentation publisher. This should be a reverse domain-name style
1575-# string, e.g. com.mycompany.MyDocSet.documentation.
1576-# The default value is: org.doxygen.Publisher.
1577-# This tag requires that the tag GENERATE_DOCSET is set to YES.
1578-
1579-DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1580-
1581-# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1582-# The default value is: Publisher.
1583-# This tag requires that the tag GENERATE_DOCSET is set to YES.
1584-
1585-DOCSET_PUBLISHER_NAME = Publisher
1586-
1587-# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1588-# additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1589-# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1590-# on Windows. In the beginning of 2021 Microsoft took the original page, with
1591-# a.o. the download links, offline the HTML help workshop was already many years
1592-# in maintenance mode). You can download the HTML help workshop from the web
1593-# archives at Installation executable (see:
1594-# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo
1595-# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).
1596-#
1597-# The HTML Help Workshop contains a compiler that can convert all HTML output
1598-# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1599-# files are now used as the Windows 98 help format, and will replace the old
1600-# Windows help format (.hlp) on all Windows platforms in the future. Compressed
1601-# HTML files also contain an index, a table of contents, and you can search for
1602-# words in the documentation. The HTML workshop also contains a viewer for
1603-# compressed HTML files.
1604-# The default value is: NO.
1605-# This tag requires that the tag GENERATE_HTML is set to YES.
1606-
1607-GENERATE_HTMLHELP = NO
1608-
1609-# The CHM_FILE tag can be used to specify the file name of the resulting .chm
1610-# file. You can add a path in front of the file if the result should not be
1611-# written to the html output directory.
1612-# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1613-
1614-CHM_FILE =
1615-
1616-# The HHC_LOCATION tag can be used to specify the location (absolute path
1617-# including file name) of the HTML help compiler (hhc.exe). If non-empty,
1618-# doxygen will try to run the HTML help compiler on the generated index.hhp.
1619-# The file has to be specified with full path.
1620-# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1621-
1622-HHC_LOCATION =
1623-
1624-# The GENERATE_CHI flag controls if a separate .chi index file is generated
1625-# (YES) or that it should be included in the main .chm file (NO).
1626-# The default value is: NO.
1627-# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1628-
1629-GENERATE_CHI = NO
1630-
1631-# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
1632-# and project file content.
1633-# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1634-
1635-CHM_INDEX_ENCODING =
1636-
1637-# The BINARY_TOC flag controls whether a binary table of contents is generated
1638-# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1639-# enables the Previous and Next buttons.
1640-# The default value is: NO.
1641-# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1642-
1643-BINARY_TOC = NO
1644-
1645-# The TOC_EXPAND flag can be set to YES to add extra items for group members to
1646-# the table of contents of the HTML help documentation and to the tree view.
1647-# The default value is: NO.
1648-# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1649-
1650-TOC_EXPAND = NO
1651-
1652-# The SITEMAP_URL tag is used to specify the full URL of the place where the
1653-# generated documentation will be placed on the server by the user during the
1654-# deployment of the documentation. The generated sitemap is called sitemap.xml
1655-# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL
1656-# is specified no sitemap is generated. For information about the sitemap
1657-# protocol see https://www.sitemaps.org
1658-# This tag requires that the tag GENERATE_HTML is set to YES.
1659-
1660-SITEMAP_URL =
1661-
1662-# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1663-# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1664-# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1665-# (.qch) of the generated HTML documentation.
1666-# The default value is: NO.
1667-# This tag requires that the tag GENERATE_HTML is set to YES.
1668-
1669-GENERATE_QHP = NO
1670-
1671-# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1672-# the file name of the resulting .qch file. The path specified is relative to
1673-# the HTML output folder.
1674-# This tag requires that the tag GENERATE_QHP is set to YES.
1675-
1676-QCH_FILE =
1677-
1678-# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1679-# Project output. For more information please see Qt Help Project / Namespace
1680-# (see:
1681-# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
1682-# The default value is: org.doxygen.Project.
1683-# This tag requires that the tag GENERATE_QHP is set to YES.
1684-
1685-QHP_NAMESPACE = org.doxygen.Project
1686-
1687-# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1688-# Help Project output. For more information please see Qt Help Project / Virtual
1689-# Folders (see:
1690-# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
1691-# The default value is: doc.
1692-# This tag requires that the tag GENERATE_QHP is set to YES.
1693-
1694-QHP_VIRTUAL_FOLDER = doc
1695-
1696-# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1697-# filter to add. For more information please see Qt Help Project / Custom
1698-# Filters (see:
1699-# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1700-# This tag requires that the tag GENERATE_QHP is set to YES.
1701-
1702-QHP_CUST_FILTER_NAME =
1703-
1704-# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1705-# custom filter to add. For more information please see Qt Help Project / Custom
1706-# Filters (see:
1707-# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1708-# This tag requires that the tag GENERATE_QHP is set to YES.
1709-
1710-QHP_CUST_FILTER_ATTRS =
1711-
1712-# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1713-# project's filter section matches. Qt Help Project / Filter Attributes (see:
1714-# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
1715-# This tag requires that the tag GENERATE_QHP is set to YES.
1716-
1717-QHP_SECT_FILTER_ATTRS =
1718-
1719-# The QHG_LOCATION tag can be used to specify the location (absolute path
1720-# including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
1721-# run qhelpgenerator on the generated .qhp file.
1722-# This tag requires that the tag GENERATE_QHP is set to YES.
1723-
1724-QHG_LOCATION =
1725-
1726-# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1727-# generated, together with the HTML files, they form an Eclipse help plugin. To
1728-# install this plugin and make it available under the help contents menu in
1729-# Eclipse, the contents of the directory containing the HTML and XML files needs
1730-# to be copied into the plugins directory of eclipse. The name of the directory
1731-# within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1732-# After copying Eclipse needs to be restarted before the help appears.
1733-# The default value is: NO.
1734-# This tag requires that the tag GENERATE_HTML is set to YES.
1735-
1736-GENERATE_ECLIPSEHELP = NO
1737-
1738-# A unique identifier for the Eclipse help plugin. When installing the plugin
1739-# the directory name containing the HTML and XML files should also have this
1740-# name. Each documentation set should have its own identifier.
1741-# The default value is: org.doxygen.Project.
1742-# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1743-
1744-ECLIPSE_DOC_ID = org.doxygen.Project
1745-
1746-# If you want full control over the layout of the generated HTML pages it might
1747-# be necessary to disable the index and replace it with your own. The
1748-# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1749-# of each HTML page. A value of NO enables the index and the value YES disables
1750-# it. Since the tabs in the index contain the same information as the navigation
1751-# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1752-# The default value is: NO.
1753-# This tag requires that the tag GENERATE_HTML is set to YES.
1754-
1755-DISABLE_INDEX = NO
1756-
1757-# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1758-# structure should be generated to display hierarchical information. If the tag
1759-# value is set to YES, a side panel will be generated containing a tree-like
1760-# index structure (just like the one that is generated for HTML Help). For this
1761-# to work a browser that supports JavaScript, DHTML, CSS and frames is required
1762-# (i.e. any modern browser). Windows users are probably better off using the
1763-# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
1764-# further fine tune the look of the index (see "Fine-tuning the output"). As an
1765-# example, the default style sheet generated by doxygen has an example that
1766-# shows how to put an image at the root of the tree instead of the PROJECT_NAME.
1767-# Since the tree basically has the same information as the tab index, you could
1768-# consider setting DISABLE_INDEX to YES when enabling this option.
1769-# The default value is: NO.
1770-# This tag requires that the tag GENERATE_HTML is set to YES.
1771-
1772-GENERATE_TREEVIEW = NO
1773-
1774-# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the
1775-# FULL_SIDEBAR option determines if the side bar is limited to only the treeview
1776-# area (value NO) or if it should extend to the full height of the window (value
1777-# YES). Setting this to YES gives a layout similar to
1778-# https://docs.readthedocs.io with more room for contents, but less room for the
1779-# project logo, title, and description. If either GENERATE_TREEVIEW or
1780-# DISABLE_INDEX is set to NO, this option has no effect.
1781-# The default value is: NO.
1782-# This tag requires that the tag GENERATE_HTML is set to YES.
1783-
1784-FULL_SIDEBAR = NO
1785-
1786-# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1787-# doxygen will group on one line in the generated HTML documentation.
1788-#
1789-# Note that a value of 0 will completely suppress the enum values from appearing
1790-# in the overview section.
1791-# Minimum value: 0, maximum value: 20, default value: 4.
1792-# This tag requires that the tag GENERATE_HTML is set to YES.
1793-
1794-ENUM_VALUES_PER_LINE = 4
1795-
1796-# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1797-# to set the initial width (in pixels) of the frame in which the tree is shown.
1798-# Minimum value: 0, maximum value: 1500, default value: 250.
1799-# This tag requires that the tag GENERATE_HTML is set to YES.
1800-
1801-TREEVIEW_WIDTH = 250
1802-
1803-# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
1804-# external symbols imported via tag files in a separate window.
1805-# The default value is: NO.
1806-# This tag requires that the tag GENERATE_HTML is set to YES.
1807-
1808-EXT_LINKS_IN_WINDOW = NO
1809-
1810-# If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email
1811-# addresses.
1812-# The default value is: YES.
1813-# This tag requires that the tag GENERATE_HTML is set to YES.
1814-
1815-OBFUSCATE_EMAILS = YES
1816-
1817-# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg
1818-# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see
1819-# https://inkscape.org) to generate formulas as SVG images instead of PNGs for
1820-# the HTML output. These images will generally look nicer at scaled resolutions.
1821-# Possible values are: png (the default) and svg (looks nicer but requires the
1822-# pdf2svg or inkscape tool).
1823-# The default value is: png.
1824-# This tag requires that the tag GENERATE_HTML is set to YES.
1825-
1826-HTML_FORMULA_FORMAT = png
1827-
1828-# Use this tag to change the font size of LaTeX formulas included as images in
1829-# the HTML documentation. When you change the font size after a successful
1830-# doxygen run you need to manually remove any form_*.png images from the HTML
1831-# output directory to force them to be regenerated.
1832-# Minimum value: 8, maximum value: 50, default value: 10.
1833-# This tag requires that the tag GENERATE_HTML is set to YES.
1834-
1835-FORMULA_FONTSIZE = 10
1836-
1837-# The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands
1838-# to create new LaTeX commands to be used in formulas as building blocks. See
1839-# the section "Including formulas" for details.
1840-
1841-FORMULA_MACROFILE =
1842-
1843-# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1844-# https://www.mathjax.org) which uses client side JavaScript for the rendering
1845-# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1846-# installed or if you want to formulas look prettier in the HTML output. When
1847-# enabled you may also need to install MathJax separately and configure the path
1848-# to it using the MATHJAX_RELPATH option.
1849-# The default value is: NO.
1850-# This tag requires that the tag GENERATE_HTML is set to YES.
1851-
1852-USE_MATHJAX = NO
1853-
1854-# With MATHJAX_VERSION it is possible to specify the MathJax version to be used.
1855-# Note that the different versions of MathJax have different requirements with
1856-# regards to the different settings, so it is possible that also other MathJax
1857-# settings have to be changed when switching between the different MathJax
1858-# versions.
1859-# Possible values are: MathJax_2 and MathJax_3.
1860-# The default value is: MathJax_2.
1861-# This tag requires that the tag USE_MATHJAX is set to YES.
1862-
1863-MATHJAX_VERSION = MathJax_2
1864-
1865-# When MathJax is enabled you can set the default output format to be used for
1866-# the MathJax output. For more details about the output format see MathJax
1867-# version 2 (see:
1868-# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3
1869-# (see:
1870-# http://docs.mathjax.org/en/latest/web/components/output.html).
1871-# Possible values are: HTML-CSS (which is slower, but has the best
1872-# compatibility. This is the name for Mathjax version 2, for MathJax version 3
1873-# this will be translated into chtml), NativeMML (i.e. MathML. Only supported
1874-# for NathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This
1875-# is the name for Mathjax version 3, for MathJax version 2 this will be
1876-# translated into HTML-CSS) and SVG.
1877-# The default value is: HTML-CSS.
1878-# This tag requires that the tag USE_MATHJAX is set to YES.
1879-
1880-MATHJAX_FORMAT = HTML-CSS
1881-
1882-# When MathJax is enabled you need to specify the location relative to the HTML
1883-# output directory using the MATHJAX_RELPATH option. The destination directory
1884-# should contain the MathJax.js script. For instance, if the mathjax directory
1885-# is located at the same level as the HTML output directory, then
1886-# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1887-# Content Delivery Network so you can quickly see the result without installing
1888-# MathJax. However, it is strongly recommended to install a local copy of
1889-# MathJax from https://www.mathjax.org before deployment. The default value is:
1890-# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2
1891-# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3
1892-# This tag requires that the tag USE_MATHJAX is set to YES.
1893-
1894-MATHJAX_RELPATH =
1895-
1896-# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1897-# extension names that should be enabled during MathJax rendering. For example
1898-# for MathJax version 2 (see
1899-# https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):
1900-# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1901-# For example for MathJax version 3 (see
1902-# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html):
1903-# MATHJAX_EXTENSIONS = ams
1904-# This tag requires that the tag USE_MATHJAX is set to YES.
1905-
1906-MATHJAX_EXTENSIONS =
1907-
1908-# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1909-# of code that will be used on startup of the MathJax code. See the MathJax site
1910-# (see:
1911-# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
1912-# example see the documentation.
1913-# This tag requires that the tag USE_MATHJAX is set to YES.
1914-
1915-MATHJAX_CODEFILE =
1916-
1917-# When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1918-# the HTML output. The underlying search engine uses javascript and DHTML and
1919-# should work on any modern browser. Note that when using HTML help
1920-# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1921-# there is already a search function so this one should typically be disabled.
1922-# For large projects the javascript based search engine can be slow, then
1923-# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1924-# search using the keyboard; to jump to the search box use <access key> + S
1925-# (what the <access key> is depends on the OS and browser, but it is typically
1926-# <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1927-# key> to jump into the search results window, the results can be navigated
1928-# using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1929-# the search. The filter options can be selected when the cursor is inside the
1930-# search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1931-# to select a filter and <Enter> or <escape> to activate or cancel the filter
1932-# option.
1933-# The default value is: YES.
1934-# This tag requires that the tag GENERATE_HTML is set to YES.
1935-
1936-SEARCHENGINE = YES
1937-
1938-# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1939-# implemented using a web server instead of a web client using JavaScript. There
1940-# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1941-# setting. When disabled, doxygen will generate a PHP script for searching and
1942-# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1943-# and searching needs to be provided by external tools. See the section
1944-# "External Indexing and Searching" for details.
1945-# The default value is: NO.
1946-# This tag requires that the tag SEARCHENGINE is set to YES.
1947-
1948-SERVER_BASED_SEARCH = NO
1949-
1950-# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1951-# script for searching. Instead the search results are written to an XML file
1952-# which needs to be processed by an external indexer. Doxygen will invoke an
1953-# external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1954-# search results.
1955-#
1956-# Doxygen ships with an example indexer (doxyindexer) and search engine
1957-# (doxysearch.cgi) which are based on the open source search engine library
1958-# Xapian (see:
1959-# https://xapian.org/).
1960-#
1961-# See the section "External Indexing and Searching" for details.
1962-# The default value is: NO.
1963-# This tag requires that the tag SEARCHENGINE is set to YES.
1964-
1965-EXTERNAL_SEARCH = NO
1966-
1967-# The SEARCHENGINE_URL should point to a search engine hosted by a web server
1968-# which will return the search results when EXTERNAL_SEARCH is enabled.
1969-#
1970-# Doxygen ships with an example indexer (doxyindexer) and search engine
1971-# (doxysearch.cgi) which are based on the open source search engine library
1972-# Xapian (see:
1973-# https://xapian.org/). See the section "External Indexing and Searching" for
1974-# details.
1975-# This tag requires that the tag SEARCHENGINE is set to YES.
1976-
1977-SEARCHENGINE_URL =
1978-
1979-# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1980-# search data is written to a file for indexing by an external tool. With the
1981-# SEARCHDATA_FILE tag the name of this file can be specified.
1982-# The default file is: searchdata.xml.
1983-# This tag requires that the tag SEARCHENGINE is set to YES.
1984-
1985-SEARCHDATA_FILE = searchdata.xml
1986-
1987-# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1988-# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1989-# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1990-# projects and redirect the results back to the right project.
1991-# This tag requires that the tag SEARCHENGINE is set to YES.
1992-
1993-EXTERNAL_SEARCH_ID =
1994-
1995-# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1996-# projects other than the one defined by this configuration file, but that are
1997-# all added to the same external search index. Each project needs to have a
1998-# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1999-# to a relative location where the documentation can be found. The format is:
2000-# EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
2001-# This tag requires that the tag SEARCHENGINE is set to YES.
2002-
2003-EXTRA_SEARCH_MAPPINGS =
2004-
2005-#---------------------------------------------------------------------------
2006-# Configuration options related to the LaTeX output
2007-#---------------------------------------------------------------------------
2008-
2009-# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
2010-# The default value is: YES.
2011-
2012-GENERATE_LATEX = YES
2013-
2014-# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
2015-# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2016-# it.
2017-# The default directory is: latex.
2018-# This tag requires that the tag GENERATE_LATEX is set to YES.
2019-
2020-LATEX_OUTPUT = latex
2021-
2022-# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
2023-# invoked.
2024-#
2025-# Note that when not enabling USE_PDFLATEX the default is latex when enabling
2026-# USE_PDFLATEX the default is pdflatex and when in the later case latex is
2027-# chosen this is overwritten by pdflatex. For specific output languages the
2028-# default can have been set differently, this depends on the implementation of
2029-# the output language.
2030-# This tag requires that the tag GENERATE_LATEX is set to YES.
2031-
2032-LATEX_CMD_NAME =
2033-
2034-# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
2035-# index for LaTeX.
2036-# Note: This tag is used in the Makefile / make.bat.
2037-# See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
2038-# (.tex).
2039-# The default file is: makeindex.
2040-# This tag requires that the tag GENERATE_LATEX is set to YES.
2041-
2042-MAKEINDEX_CMD_NAME = makeindex
2043-
2044-# The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
2045-# generate index for LaTeX. In case there is no backslash (\) as first character
2046-# it will be automatically added in the LaTeX code.
2047-# Note: This tag is used in the generated output file (.tex).
2048-# See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
2049-# The default value is: makeindex.
2050-# This tag requires that the tag GENERATE_LATEX is set to YES.
2051-
2052-LATEX_MAKEINDEX_CMD = makeindex
2053-
2054-# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
2055-# documents. This may be useful for small projects and may help to save some
2056-# trees in general.
2057-# The default value is: NO.
2058-# This tag requires that the tag GENERATE_LATEX is set to YES.
2059-
2060-COMPACT_LATEX = NO
2061-
2062-# The PAPER_TYPE tag can be used to set the paper type that is used by the
2063-# printer.
2064-# Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
2065-# 14 inches) and executive (7.25 x 10.5 inches).
2066-# The default value is: a4.
2067-# This tag requires that the tag GENERATE_LATEX is set to YES.
2068-
2069-PAPER_TYPE = a4
2070-
2071-# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
2072-# that should be included in the LaTeX output. The package can be specified just
2073-# by its name or with the correct syntax as to be used with the LaTeX
2074-# \usepackage command. To get the times font for instance you can specify :
2075-# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
2076-# To use the option intlimits with the amsmath package you can specify:
2077-# EXTRA_PACKAGES=[intlimits]{amsmath}
2078-# If left blank no extra packages will be included.
2079-# This tag requires that the tag GENERATE_LATEX is set to YES.
2080-
2081-EXTRA_PACKAGES =
2082-
2083-# The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for
2084-# the generated LaTeX document. The header should contain everything until the
2085-# first chapter. If it is left blank doxygen will generate a standard header. It
2086-# is highly recommended to start with a default header using
2087-# doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty
2088-# and then modify the file new_header.tex. See also section "Doxygen usage" for
2089-# information on how to generate the default header that doxygen normally uses.
2090-#
2091-# Note: Only use a user-defined header if you know what you are doing!
2092-# Note: The header is subject to change so you typically have to regenerate the
2093-# default header when upgrading to a newer version of doxygen. The following
2094-# commands have a special meaning inside the header (and footer): For a
2095-# description of the possible markers and block names see the documentation.
2096-# This tag requires that the tag GENERATE_LATEX is set to YES.
2097-
2098-LATEX_HEADER =
2099-
2100-# The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for
2101-# the generated LaTeX document. The footer should contain everything after the
2102-# last chapter. If it is left blank doxygen will generate a standard footer. See
2103-# LATEX_HEADER for more information on how to generate a default footer and what
2104-# special commands can be used inside the footer. See also section "Doxygen
2105-# usage" for information on how to generate the default footer that doxygen
2106-# normally uses. Note: Only use a user-defined footer if you know what you are
2107-# doing!
2108-# This tag requires that the tag GENERATE_LATEX is set to YES.
2109-
2110-LATEX_FOOTER =
2111-
2112-# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
2113-# LaTeX style sheets that are included after the standard style sheets created
2114-# by doxygen. Using this option one can overrule certain style aspects. Doxygen
2115-# will copy the style sheet files to the output directory.
2116-# Note: The order of the extra style sheet files is of importance (e.g. the last
2117-# style sheet in the list overrules the setting of the previous ones in the
2118-# list).
2119-# This tag requires that the tag GENERATE_LATEX is set to YES.
2120-
2121-LATEX_EXTRA_STYLESHEET =
2122-
2123-# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
2124-# other source files which should be copied to the LATEX_OUTPUT output
2125-# directory. Note that the files will be copied as-is; there are no commands or
2126-# markers available.
2127-# This tag requires that the tag GENERATE_LATEX is set to YES.
2128-
2129-LATEX_EXTRA_FILES =
2130-
2131-# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
2132-# prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
2133-# contain links (just like the HTML output) instead of page references. This
2134-# makes the output suitable for online browsing using a PDF viewer.
2135-# The default value is: YES.
2136-# This tag requires that the tag GENERATE_LATEX is set to YES.
2137-
2138-PDF_HYPERLINKS = YES
2139-
2140-# If the USE_PDFLATEX tag is set to YES, doxygen will use the engine as
2141-# specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX
2142-# files. Set this option to YES, to get a higher quality PDF documentation.
2143-#
2144-# See also section LATEX_CMD_NAME for selecting the engine.
2145-# The default value is: YES.
2146-# This tag requires that the tag GENERATE_LATEX is set to YES.
2147-
2148-USE_PDFLATEX = YES
2149-
2150-# The LATEX_BATCHMODE tag signals the behavior of LaTeX in case of an error.
2151-# Possible values are: NO same as ERROR_STOP, YES same as BATCH, BATCH In batch
2152-# mode nothing is printed on the terminal, errors are scrolled as if <return> is
2153-# hit at every error; missing files that TeX tries to input or request from
2154-# keyboard input (\read on a not open input stream) cause the job to abort,
2155-# NON_STOP In nonstop mode the diagnostic message will appear on the terminal,
2156-# but there is no possibility of user interaction just like in batch mode,
2157-# SCROLL In scroll mode, TeX will stop only for missing files to input or if
2158-# keyboard input is necessary and ERROR_STOP In errorstop mode, TeX will stop at
2159-# each error, asking for user intervention.
2160-# The default value is: NO.
2161-# This tag requires that the tag GENERATE_LATEX is set to YES.
2162-
2163-LATEX_BATCHMODE = NO
2164-
2165-# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
2166-# index chapters (such as File Index, Compound Index, etc.) in the output.
2167-# The default value is: NO.
2168-# This tag requires that the tag GENERATE_LATEX is set to YES.
2169-
2170-LATEX_HIDE_INDICES = NO
2171-
2172-# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
2173-# bibliography, e.g. plainnat, or ieeetr. See
2174-# https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
2175-# The default value is: plain.
2176-# This tag requires that the tag GENERATE_LATEX is set to YES.
2177-
2178-LATEX_BIB_STYLE = plain
2179-
2180-# The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
2181-# path from which the emoji images will be read. If a relative path is entered,
2182-# it will be relative to the LATEX_OUTPUT directory. If left blank the
2183-# LATEX_OUTPUT directory will be used.
2184-# This tag requires that the tag GENERATE_LATEX is set to YES.
2185-
2186-LATEX_EMOJI_DIRECTORY =
2187-
2188-#---------------------------------------------------------------------------
2189-# Configuration options related to the RTF output
2190-#---------------------------------------------------------------------------
2191-
2192-# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
2193-# RTF output is optimized for Word 97 and may not look too pretty with other RTF
2194-# readers/editors.
2195-# The default value is: NO.
2196-
2197-GENERATE_RTF = NO
2198-
2199-# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
2200-# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2201-# it.
2202-# The default directory is: rtf.
2203-# This tag requires that the tag GENERATE_RTF is set to YES.
2204-
2205-RTF_OUTPUT = rtf
2206-
2207-# If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
2208-# documents. This may be useful for small projects and may help to save some
2209-# trees in general.
2210-# The default value is: NO.
2211-# This tag requires that the tag GENERATE_RTF is set to YES.
2212-
2213-COMPACT_RTF = NO
2214-
2215-# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
2216-# contain hyperlink fields. The RTF file will contain links (just like the HTML
2217-# output) instead of page references. This makes the output suitable for online
2218-# browsing using Word or some other Word compatible readers that support those
2219-# fields.
2220-#
2221-# Note: WordPad (write) and others do not support links.
2222-# The default value is: NO.
2223-# This tag requires that the tag GENERATE_RTF is set to YES.
2224-
2225-RTF_HYPERLINKS = NO
2226-
2227-# Load stylesheet definitions from file. Syntax is similar to doxygen's
2228-# configuration file, i.e. a series of assignments. You only have to provide
2229-# replacements, missing definitions are set to their default value.
2230-#
2231-# See also section "Doxygen usage" for information on how to generate the
2232-# default style sheet that doxygen normally uses.
2233-# This tag requires that the tag GENERATE_RTF is set to YES.
2234-
2235-RTF_STYLESHEET_FILE =
2236-
2237-# Set optional variables used in the generation of an RTF document. Syntax is
2238-# similar to doxygen's configuration file. A template extensions file can be
2239-# generated using doxygen -e rtf extensionFile.
2240-# This tag requires that the tag GENERATE_RTF is set to YES.
2241-
2242-RTF_EXTENSIONS_FILE =
2243-
2244-#---------------------------------------------------------------------------
2245-# Configuration options related to the man page output
2246-#---------------------------------------------------------------------------
2247-
2248-# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
2249-# classes and files.
2250-# The default value is: NO.
2251-
2252-GENERATE_MAN = NO
2253-
2254-# The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
2255-# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2256-# it. A directory man3 will be created inside the directory specified by
2257-# MAN_OUTPUT.
2258-# The default directory is: man.
2259-# This tag requires that the tag GENERATE_MAN is set to YES.
2260-
2261-MAN_OUTPUT = man
2262-
2263-# The MAN_EXTENSION tag determines the extension that is added to the generated
2264-# man pages. In case the manual section does not start with a number, the number
2265-# 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
2266-# optional.
2267-# The default value is: .3.
2268-# This tag requires that the tag GENERATE_MAN is set to YES.
2269-
2270-MAN_EXTENSION = .3
2271-
2272-# The MAN_SUBDIR tag determines the name of the directory created within
2273-# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
2274-# MAN_EXTENSION with the initial . removed.
2275-# This tag requires that the tag GENERATE_MAN is set to YES.
2276-
2277-MAN_SUBDIR =
2278-
2279-# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
2280-# will generate one additional man file for each entity documented in the real
2281-# man page(s). These additional files only source the real man page, but without
2282-# them the man command would be unable to find the correct page.
2283-# The default value is: NO.
2284-# This tag requires that the tag GENERATE_MAN is set to YES.
2285-
2286-MAN_LINKS = NO
2287-
2288-#---------------------------------------------------------------------------
2289-# Configuration options related to the XML output
2290-#---------------------------------------------------------------------------
2291-
2292-# If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
2293-# captures the structure of the code including all documentation.
2294-# The default value is: NO.
2295-
2296-GENERATE_XML = NO
2297-
2298-# The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
2299-# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2300-# it.
2301-# The default directory is: xml.
2302-# This tag requires that the tag GENERATE_XML is set to YES.
2303-
2304-XML_OUTPUT = xml
2305-
2306-# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
2307-# listings (including syntax highlighting and cross-referencing information) to
2308-# the XML output. Note that enabling this will significantly increase the size
2309-# of the XML output.
2310-# The default value is: YES.
2311-# This tag requires that the tag GENERATE_XML is set to YES.
2312-
2313-XML_PROGRAMLISTING = YES
2314-
2315-# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
2316-# namespace members in file scope as well, matching the HTML output.
2317-# The default value is: NO.
2318-# This tag requires that the tag GENERATE_XML is set to YES.
2319-
2320-XML_NS_MEMB_FILE_SCOPE = NO
2321-
2322-#---------------------------------------------------------------------------
2323-# Configuration options related to the DOCBOOK output
2324-#---------------------------------------------------------------------------
2325-
2326-# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
2327-# that can be used to generate PDF.
2328-# The default value is: NO.
2329-
2330-GENERATE_DOCBOOK = NO
2331-
2332-# The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
2333-# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2334-# front of it.
2335-# The default directory is: docbook.
2336-# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
2337-
2338-DOCBOOK_OUTPUT = docbook
2339-
2340-#---------------------------------------------------------------------------
2341-# Configuration options for the AutoGen Definitions output
2342-#---------------------------------------------------------------------------
2343-
2344-# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
2345-# AutoGen Definitions (see https://autogen.sourceforge.net/) file that captures
2346-# the structure of the code including all documentation. Note that this feature
2347-# is still experimental and incomplete at the moment.
2348-# The default value is: NO.
2349-
2350-GENERATE_AUTOGEN_DEF = NO
2351-
2352-#---------------------------------------------------------------------------
2353-# Configuration options related to Sqlite3 output
2354-#---------------------------------------------------------------------------
2355-
2356-# If the GENERATE_SQLITE3 tag is set to YES doxygen will generate a Sqlite3
2357-# database with symbols found by doxygen stored in tables.
2358-# The default value is: NO.
2359-
2360-GENERATE_SQLITE3 = NO
2361-
2362-# The SQLITE3_OUTPUT tag is used to specify where the Sqlite3 database will be
2363-# put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put
2364-# in front of it.
2365-# The default directory is: sqlite3.
2366-# This tag requires that the tag GENERATE_SQLITE3 is set to YES.
2367-
2368-SQLITE3_OUTPUT = sqlite3
2369-
2370-# The SQLITE3_OVERWRITE_DB tag is set to YES, the existing doxygen_sqlite3.db
2371-# database file will be recreated with each doxygen run. If set to NO, doxygen
2372-# will warn if an a database file is already found and not modify it.
2373-# The default value is: YES.
2374-# This tag requires that the tag GENERATE_SQLITE3 is set to YES.
2375-
2376-SQLITE3_RECREATE_DB = YES
2377-
2378-#---------------------------------------------------------------------------
2379-# Configuration options related to the Perl module output
2380-#---------------------------------------------------------------------------
2381-
2382-# If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
2383-# file that captures the structure of the code including all documentation.
2384-#
2385-# Note that this feature is still experimental and incomplete at the moment.
2386-# The default value is: NO.
2387-
2388-GENERATE_PERLMOD = NO
2389-
2390-# If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
2391-# Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2392-# output from the Perl module output.
2393-# The default value is: NO.
2394-# This tag requires that the tag GENERATE_PERLMOD is set to YES.
2395-
2396-PERLMOD_LATEX = NO
2397-
2398-# If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
2399-# formatted so it can be parsed by a human reader. This is useful if you want to
2400-# understand what is going on. On the other hand, if this tag is set to NO, the
2401-# size of the Perl module output will be much smaller and Perl will parse it
2402-# just the same.
2403-# The default value is: YES.
2404-# This tag requires that the tag GENERATE_PERLMOD is set to YES.
2405-
2406-PERLMOD_PRETTY = YES
2407-
2408-# The names of the make variables in the generated doxyrules.make file are
2409-# prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2410-# so different doxyrules.make files included by the same Makefile don't
2411-# overwrite each other's variables.
2412-# This tag requires that the tag GENERATE_PERLMOD is set to YES.
2413-
2414-PERLMOD_MAKEVAR_PREFIX =
2415-
2416-#---------------------------------------------------------------------------
2417-# Configuration options related to the preprocessor
2418-#---------------------------------------------------------------------------
2419-
2420-# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
2421-# C-preprocessor directives found in the sources and include files.
2422-# The default value is: YES.
2423-
2424-ENABLE_PREPROCESSING = YES
2425-
2426-# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
2427-# in the source code. If set to NO, only conditional compilation will be
2428-# performed. Macro expansion can be done in a controlled way by setting
2429-# EXPAND_ONLY_PREDEF to YES.
2430-# The default value is: NO.
2431-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2432-
2433-MACRO_EXPANSION = NO
2434-
2435-# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
2436-# the macro expansion is limited to the macros specified with the PREDEFINED and
2437-# EXPAND_AS_DEFINED tags.
2438-# The default value is: NO.
2439-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2440-
2441-EXPAND_ONLY_PREDEF = NO
2442-
2443-# If the SEARCH_INCLUDES tag is set to YES, the include files in the
2444-# INCLUDE_PATH will be searched if a #include is found.
2445-# The default value is: YES.
2446-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2447-
2448-SEARCH_INCLUDES = YES
2449-
2450-# The INCLUDE_PATH tag can be used to specify one or more directories that
2451-# contain include files that are not input files but should be processed by the
2452-# preprocessor. Note that the INCLUDE_PATH is not recursive, so the setting of
2453-# RECURSIVE has no effect here.
2454-# This tag requires that the tag SEARCH_INCLUDES is set to YES.
2455-
2456-INCLUDE_PATH =
2457-
2458-# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2459-# patterns (like *.h and *.hpp) to filter out the header-files in the
2460-# directories. If left blank, the patterns specified with FILE_PATTERNS will be
2461-# used.
2462-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2463-
2464-INCLUDE_FILE_PATTERNS =
2465-
2466-# The PREDEFINED tag can be used to specify one or more macro names that are
2467-# defined before the preprocessor is started (similar to the -D option of e.g.
2468-# gcc). The argument of the tag is a list of macros of the form: name or
2469-# name=definition (no spaces). If the definition and the "=" are omitted, "=1"
2470-# is assumed. To prevent a macro definition from being undefined via #undef or
2471-# recursively expanded use the := operator instead of the = operator.
2472-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2473-
2474-PREDEFINED =
2475-
2476-# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2477-# tag can be used to specify a list of macro names that should be expanded. The
2478-# macro definition that is found in the sources will be used. Use the PREDEFINED
2479-# tag if you want to use a different macro definition that overrules the
2480-# definition found in the source code.
2481-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2482-
2483-EXPAND_AS_DEFINED =
2484-
2485-# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2486-# remove all references to function-like macros that are alone on a line, have
2487-# an all uppercase name, and do not end with a semicolon. Such function macros
2488-# are typically used for boiler-plate code, and will confuse the parser if not
2489-# removed.
2490-# The default value is: YES.
2491-# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2492-
2493-SKIP_FUNCTION_MACROS = YES
2494-
2495-#---------------------------------------------------------------------------
2496-# Configuration options related to external references
2497-#---------------------------------------------------------------------------
2498-
2499-# The TAGFILES tag can be used to specify one or more tag files. For each tag
2500-# file the location of the external documentation should be added. The format of
2501-# a tag file without this location is as follows:
2502-# TAGFILES = file1 file2 ...
2503-# Adding location for the tag files is done as follows:
2504-# TAGFILES = file1=loc1 "file2 = loc2" ...
2505-# where loc1 and loc2 can be relative or absolute paths or URLs. See the
2506-# section "Linking to external documentation" for more information about the use
2507-# of tag files.
2508-# Note: Each tag file must have a unique name (where the name does NOT include
2509-# the path). If a tag file is not located in the directory in which doxygen is
2510-# run, you must also specify the path to the tagfile here.
2511-
2512-TAGFILES =
2513-
2514-# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2515-# tag file that is based on the input files it reads. See section "Linking to
2516-# external documentation" for more information about the usage of tag files.
2517-
2518-GENERATE_TAGFILE =
2519-
2520-# If the ALLEXTERNALS tag is set to YES, all external classes and namespaces
2521-# will be listed in the class and namespace index. If set to NO, only the
2522-# inherited external classes will be listed.
2523-# The default value is: NO.
2524-
2525-ALLEXTERNALS = NO
2526-
2527-# If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
2528-# in the topic index. If set to NO, only the current project's groups will be
2529-# listed.
2530-# The default value is: YES.
2531-
2532-EXTERNAL_GROUPS = YES
2533-
2534-# If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2535-# the related pages index. If set to NO, only the current project's pages will
2536-# be listed.
2537-# The default value is: YES.
2538-
2539-EXTERNAL_PAGES = YES
2540-
2541-#---------------------------------------------------------------------------
2542-# Configuration options related to diagram generator tools
2543-#---------------------------------------------------------------------------
2544-
2545-# If set to YES the inheritance and collaboration graphs will hide inheritance
2546-# and usage relations if the target is undocumented or is not a class.
2547-# The default value is: YES.
2548-
2549-HIDE_UNDOC_RELATIONS = YES
2550-
2551-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2552-# available from the path. This tool is part of Graphviz (see:
2553-# https://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2554-# Bell Labs. The other options in this section have no effect if this option is
2555-# set to NO
2556-# The default value is: YES.
2557-
2558-HAVE_DOT = YES
2559-
2560-# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2561-# to run in parallel. When set to 0 doxygen will base this on the number of
2562-# processors available in the system. You can set it explicitly to a value
2563-# larger than 0 to get control over the balance between CPU load and processing
2564-# speed.
2565-# Minimum value: 0, maximum value: 32, default value: 0.
2566-# This tag requires that the tag HAVE_DOT is set to YES.
2567-
2568-DOT_NUM_THREADS = 0
2569-
2570-# DOT_COMMON_ATTR is common attributes for nodes, edges and labels of
2571-# subgraphs. When you want a differently looking font in the dot files that
2572-# doxygen generates you can specify fontname, fontcolor and fontsize attributes.
2573-# For details please see <a href=https://graphviz.org/doc/info/attrs.html>Node,
2574-# Edge and Graph Attributes specification</a> You need to make sure dot is able
2575-# to find the font, which can be done by putting it in a standard location or by
2576-# setting the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
2577-# directory containing the font. Default graphviz fontsize is 14.
2578-# The default value is: fontname=Helvetica,fontsize=10.
2579-# This tag requires that the tag HAVE_DOT is set to YES.
2580-
2581-DOT_COMMON_ATTR = "fontname=Helvetica,fontsize=10"
2582-
2583-# DOT_EDGE_ATTR is concatenated with DOT_COMMON_ATTR. For elegant style you can
2584-# add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. <a
2585-# href=https://graphviz.org/doc/info/arrows.html>Complete documentation about
2586-# arrows shapes.</a>
2587-# The default value is: labelfontname=Helvetica,labelfontsize=10.
2588-# This tag requires that the tag HAVE_DOT is set to YES.
2589-
2590-DOT_EDGE_ATTR = "labelfontname=Helvetica,labelfontsize=10"
2591-
2592-# DOT_NODE_ATTR is concatenated with DOT_COMMON_ATTR. For view without boxes
2593-# around nodes set 'shape=plain' or 'shape=plaintext' <a
2594-# href=https://www.graphviz.org/doc/info/shapes.html>Shapes specification</a>
2595-# The default value is: shape=box,height=0.2,width=0.4.
2596-# This tag requires that the tag HAVE_DOT is set to YES.
2597-
2598-DOT_NODE_ATTR = "shape=box,height=0.2,width=0.4"
2599-
2600-# You can set the path where dot can find font specified with fontname in
2601-# DOT_COMMON_ATTR and others dot attributes.
2602-# This tag requires that the tag HAVE_DOT is set to YES.
2603-
2604-DOT_FONTPATH =
2605-
2606-# If the CLASS_GRAPH tag is set to YES or GRAPH or BUILTIN then doxygen will
2607-# generate a graph for each documented class showing the direct and indirect
2608-# inheritance relations. In case the CLASS_GRAPH tag is set to YES or GRAPH and
2609-# HAVE_DOT is enabled as well, then dot will be used to draw the graph. In case
2610-# the CLASS_GRAPH tag is set to YES and HAVE_DOT is disabled or if the
2611-# CLASS_GRAPH tag is set to BUILTIN, then the built-in generator will be used.
2612-# If the CLASS_GRAPH tag is set to TEXT the direct and indirect inheritance
2613-# relations will be shown as texts / links.
2614-# Possible values are: NO, YES, TEXT, GRAPH and BUILTIN.
2615-# The default value is: YES.
2616-
2617-CLASS_GRAPH = YES
2618-
2619-# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2620-# graph for each documented class showing the direct and indirect implementation
2621-# dependencies (inheritance, containment, and class references variables) of the
2622-# class with other documented classes. Explicit enabling a collaboration graph,
2623-# when COLLABORATION_GRAPH is set to NO, can be accomplished by means of the
2624-# command \collaborationgraph. Disabling a collaboration graph can be
2625-# accomplished by means of the command \hidecollaborationgraph.
2626-# The default value is: YES.
2627-# This tag requires that the tag HAVE_DOT is set to YES.
2628-
2629-COLLABORATION_GRAPH = YES
2630-
2631-# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2632-# groups, showing the direct groups dependencies. Explicit enabling a group
2633-# dependency graph, when GROUP_GRAPHS is set to NO, can be accomplished by means
2634-# of the command \groupgraph. Disabling a directory graph can be accomplished by
2635-# means of the command \hidegroupgraph. See also the chapter Grouping in the
2636-# manual.
2637-# The default value is: YES.
2638-# This tag requires that the tag HAVE_DOT is set to YES.
2639-
2640-GROUP_GRAPHS = YES
2641-
2642-# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
2643-# collaboration diagrams in a style similar to the OMG's Unified Modeling
2644-# Language.
2645-# The default value is: NO.
2646-# This tag requires that the tag HAVE_DOT is set to YES.
2647-
2648-UML_LOOK = NO
2649-
2650-# If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2651-# class node. If there are many fields or methods and many nodes the graph may
2652-# become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2653-# number of items for each type to make the size more manageable. Set this to 0
2654-# for no limit. Note that the threshold may be exceeded by 50% before the limit
2655-# is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2656-# but if the number exceeds 15, the total amount of fields shown is limited to
2657-# 10.
2658-# Minimum value: 0, maximum value: 100, default value: 10.
2659-# This tag requires that the tag UML_LOOK is set to YES.
2660-
2661-UML_LIMIT_NUM_FIELDS = 10
2662-
2663-# If the DOT_UML_DETAILS tag is set to NO, doxygen will show attributes and
2664-# methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS
2665-# tag is set to YES, doxygen will add type and arguments for attributes and
2666-# methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, doxygen
2667-# will not generate fields with class member information in the UML graphs. The
2668-# class diagrams will look similar to the default class diagrams but using UML
2669-# notation for the relationships.
2670-# Possible values are: NO, YES and NONE.
2671-# The default value is: NO.
2672-# This tag requires that the tag UML_LOOK is set to YES.
2673-
2674-DOT_UML_DETAILS = NO
2675-
2676-# The DOT_WRAP_THRESHOLD tag can be used to set the maximum number of characters
2677-# to display on a single line. If the actual line length exceeds this threshold
2678-# significantly it will wrapped across multiple lines. Some heuristics are apply
2679-# to avoid ugly line breaks.
2680-# Minimum value: 0, maximum value: 1000, default value: 17.
2681-# This tag requires that the tag HAVE_DOT is set to YES.
2682-
2683-DOT_WRAP_THRESHOLD = 17
2684-
2685-# If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2686-# collaboration graphs will show the relations between templates and their
2687-# instances.
2688-# The default value is: NO.
2689-# This tag requires that the tag HAVE_DOT is set to YES.
2690-
2691-TEMPLATE_RELATIONS = NO
2692-
2693-# If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2694-# YES then doxygen will generate a graph for each documented file showing the
2695-# direct and indirect include dependencies of the file with other documented
2696-# files. Explicit enabling an include graph, when INCLUDE_GRAPH is is set to NO,
2697-# can be accomplished by means of the command \includegraph. Disabling an
2698-# include graph can be accomplished by means of the command \hideincludegraph.
2699-# The default value is: YES.
2700-# This tag requires that the tag HAVE_DOT is set to YES.
2701-
2702-INCLUDE_GRAPH = YES
2703-
2704-# If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2705-# set to YES then doxygen will generate a graph for each documented file showing
2706-# the direct and indirect include dependencies of the file with other documented
2707-# files. Explicit enabling an included by graph, when INCLUDED_BY_GRAPH is set
2708-# to NO, can be accomplished by means of the command \includedbygraph. Disabling
2709-# an included by graph can be accomplished by means of the command
2710-# \hideincludedbygraph.
2711-# The default value is: YES.
2712-# This tag requires that the tag HAVE_DOT is set to YES.
2713-
2714-INCLUDED_BY_GRAPH = YES
2715-
2716-# If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2717-# dependency graph for every global function or class method.
2718-#
2719-# Note that enabling this option will significantly increase the time of a run.
2720-# So in most cases it will be better to enable call graphs for selected
2721-# functions only using the \callgraph command. Disabling a call graph can be
2722-# accomplished by means of the command \hidecallgraph.
2723-# The default value is: NO.
2724-# This tag requires that the tag HAVE_DOT is set to YES.
2725-
2726-CALL_GRAPH = NO
2727-
2728-# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2729-# dependency graph for every global function or class method.
2730-#
2731-# Note that enabling this option will significantly increase the time of a run.
2732-# So in most cases it will be better to enable caller graphs for selected
2733-# functions only using the \callergraph command. Disabling a caller graph can be
2734-# accomplished by means of the command \hidecallergraph.
2735-# The default value is: NO.
2736-# This tag requires that the tag HAVE_DOT is set to YES.
2737-
2738-CALLER_GRAPH = NO
2739-
2740-# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2741-# hierarchy of all classes instead of a textual one.
2742-# The default value is: YES.
2743-# This tag requires that the tag HAVE_DOT is set to YES.
2744-
2745-GRAPHICAL_HIERARCHY = YES
2746-
2747-# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2748-# dependencies a directory has on other directories in a graphical way. The
2749-# dependency relations are determined by the #include relations between the
2750-# files in the directories. Explicit enabling a directory graph, when
2751-# DIRECTORY_GRAPH is set to NO, can be accomplished by means of the command
2752-# \directorygraph. Disabling a directory graph can be accomplished by means of
2753-# the command \hidedirectorygraph.
2754-# The default value is: YES.
2755-# This tag requires that the tag HAVE_DOT is set to YES.
2756-
2757-DIRECTORY_GRAPH = YES
2758-
2759-# The DIR_GRAPH_MAX_DEPTH tag can be used to limit the maximum number of levels
2760-# of child directories generated in directory dependency graphs by dot.
2761-# Minimum value: 1, maximum value: 25, default value: 1.
2762-# This tag requires that the tag DIRECTORY_GRAPH is set to YES.
2763-
2764-DIR_GRAPH_MAX_DEPTH = 1
2765-
2766-# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2767-# generated by dot. For an explanation of the image formats see the section
2768-# output formats in the documentation of the dot tool (Graphviz (see:
2769-# https://www.graphviz.org/)).
2770-# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2771-# to make the SVG files visible in IE 9+ (other browsers do not have this
2772-# requirement).
2773-# Possible values are: png, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd,
2774-# gif, gif:cairo, gif:cairo:gd, gif:gd, gif:gd:gd, svg, png:gd, png:gd:gd,
2775-# png:cairo, png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
2776-# png:gdiplus:gdiplus.
2777-# The default value is: png.
2778-# This tag requires that the tag HAVE_DOT is set to YES.
2779-
2780-DOT_IMAGE_FORMAT = png
2781-
2782-# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2783-# enable generation of interactive SVG images that allow zooming and panning.
2784-#
2785-# Note that this requires a modern browser other than Internet Explorer. Tested
2786-# and working are Firefox, Chrome, Safari, and Opera.
2787-# Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2788-# the SVG files visible. Older versions of IE do not have SVG support.
2789-# The default value is: NO.
2790-# This tag requires that the tag HAVE_DOT is set to YES.
2791-
2792-INTERACTIVE_SVG = NO
2793-
2794-# The DOT_PATH tag can be used to specify the path where the dot tool can be
2795-# found. If left blank, it is assumed the dot tool can be found in the path.
2796-# This tag requires that the tag HAVE_DOT is set to YES.
2797-
2798-DOT_PATH =
2799-
2800-# The DOTFILE_DIRS tag can be used to specify one or more directories that
2801-# contain dot files that are included in the documentation (see the \dotfile
2802-# command).
2803-# This tag requires that the tag HAVE_DOT is set to YES.
2804-
2805-DOTFILE_DIRS =
2806-
2807-# You can include diagrams made with dia in doxygen documentation. Doxygen will
2808-# then run dia to produce the diagram and insert it in the documentation. The
2809-# DIA_PATH tag allows you to specify the directory where the dia binary resides.
2810-# If left empty dia is assumed to be found in the default search path.
2811-
2812-DIA_PATH =
2813-
2814-# The DIAFILE_DIRS tag can be used to specify one or more directories that
2815-# contain dia files that are included in the documentation (see the \diafile
2816-# command).
2817-
2818-DIAFILE_DIRS =
2819-
2820-# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2821-# path where java can find the plantuml.jar file or to the filename of jar file
2822-# to be used. If left blank, it is assumed PlantUML is not used or called during
2823-# a preprocessing step. Doxygen will generate a warning when it encounters a
2824-# \startuml command in this case and will not generate output for the diagram.
2825-
2826-PLANTUML_JAR_PATH =
2827-
2828-# When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2829-# configuration file for plantuml.
2830-
2831-PLANTUML_CFG_FILE =
2832-
2833-# When using plantuml, the specified paths are searched for files specified by
2834-# the !include statement in a plantuml block.
2835-
2836-PLANTUML_INCLUDE_PATH =
2837-
2838-# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2839-# that will be shown in the graph. If the number of nodes in a graph becomes
2840-# larger than this value, doxygen will truncate the graph, which is visualized
2841-# by representing a node as a red box. Note that doxygen if the number of direct
2842-# children of the root node in a graph is already larger than
2843-# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2844-# the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2845-# Minimum value: 0, maximum value: 10000, default value: 50.
2846-# This tag requires that the tag HAVE_DOT is set to YES.
2847-
2848-DOT_GRAPH_MAX_NODES = 50
2849-
2850-# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2851-# generated by dot. A depth value of 3 means that only nodes reachable from the
2852-# root by following a path via at most 3 edges will be shown. Nodes that lay
2853-# further from the root node will be omitted. Note that setting this option to 1
2854-# or 2 may greatly reduce the computation time needed for large code bases. Also
2855-# note that the size of a graph can be further restricted by
2856-# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2857-# Minimum value: 0, maximum value: 1000, default value: 0.
2858-# This tag requires that the tag HAVE_DOT is set to YES.
2859-
2860-MAX_DOT_GRAPH_DEPTH = 0
2861-
2862-# Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
2863-# files in one run (i.e. multiple -o and -T options on the command line). This
2864-# makes dot run faster, but since only newer versions of dot (>1.8.10) support
2865-# this, this feature is disabled by default.
2866-# The default value is: NO.
2867-# This tag requires that the tag HAVE_DOT is set to YES.
2868-
2869-DOT_MULTI_TARGETS = NO
2870-
2871-# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2872-# explaining the meaning of the various boxes and arrows in the dot generated
2873-# graphs.
2874-# Note: This tag requires that UML_LOOK isn't set, i.e. the doxygen internal
2875-# graphical representation for inheritance and collaboration diagrams is used.
2876-# The default value is: YES.
2877-# This tag requires that the tag HAVE_DOT is set to YES.
2878-
2879-GENERATE_LEGEND = YES
2880-
2881-# If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate
2882-# files that are used to generate the various graphs.
2883-#
2884-# Note: This setting is not only used for dot files but also for msc temporary
2885-# files.
2886-# The default value is: YES.
2887-
2888-DOT_CLEANUP = YES
2889-
2890-# You can define message sequence charts within doxygen comments using the \msc
2891-# command. If the MSCGEN_TOOL tag is left empty (the default), then doxygen will
2892-# use a built-in version of mscgen tool to produce the charts. Alternatively,
2893-# the MSCGEN_TOOL tag can also specify the name an external tool. For instance,
2894-# specifying prog as the value, doxygen will call the tool as prog -T
2895-# <outfile_format> -o <outputfile> <inputfile>. The external tool should support
2896-# output file formats "png", "eps", "svg", and "ismap".
2897-
2898-MSCGEN_TOOL =
2899-
2900-# The MSCFILE_DIRS tag can be used to specify one or more directories that
2901-# contain msc files that are included in the documentation (see the \mscfile
2902-# command).
2903-
2904-MSCFILE_DIRS =
2905diff --git a/docs/content/_layout.html b/docs/content/_layout.html
2906deleted file mode 100644
2907index 58a1838..0000000
2908--- a/docs/content/_layout.html
2909+++ /dev/null
2910@@ -1,33 +0,0 @@
2911-<!DOCTYPE html>
2912-<html lang="en">
2913- <head>
2914- <meta charset="UTF-8" />
2915- <meta name="viewport" content="width=device-width, initial-scale=1.0" />
2916- <title>{{ .Global.siteName }}</title>
2917- <style>
2918- table {
2919- width: 100%;
2920- border-collapse: collapse;
2921- }
2922- th,
2923- td {
2924- text-align: center;
2925- border: 1px solid #ddd;
2926- padding: 8px;
2927- }
2928- th {
2929- background-color: #f2f2f2;
2930- }
2931- </style>
2932- </head>
2933- <body>
2934- <main style="margin: 0 4rem 0 4rem">
2935- <div style="display: flex; gap: 1rem">
2936- {{ template "navbar.html" . }}
2937- <div style="width: 100%">
2938- <section>{{ .Content }}</section>
2939- </div>
2940- </div>
2941- </main>
2942- </body>
2943-</html>
2944diff --git a/docs/content/features/supported-css-selectors.md b/docs/content/features/supported-css-selectors.md
2945index 51f8f2a..f92cb2e 100644
2946--- a/docs/content/features/supported-css-selectors.md
2947+++ b/docs/content/features/supported-css-selectors.md
2948@@ -1,21 +1,26 @@
2949 # Supported Selectors
2950
2951+## Support
2952+* (\*) parsing supported, not implemented
2953+* \(X\) fully supported, implemented
2954+* (/) No support planned
2955+
2956 ## Selectors
2957 | Name | Support | Test Case | Section | Test File |
2958 |-|-|-|-| - |
2959 | Type | X | testSelector | testSelector can match a element given it's tagName | tests/css_selector.cc |
2960 | Attribute | X | testSelector | testSelector can match a element by it's attributes only | tests/css_selector.cc |
2961 | ID | X | testSelector | testSelector can match a element by it's id only | tests/css_selector.cc |
2962-| Class | X | testSelector | testSelector can match a element by it's class and not matach on a non class | tests/css_selector.cc |
2963+| Class | X | testSelector | testSelector can match a element by it's class and not match on a non class | tests/css_selector.cc |
2964 | Universal | X | testSelector | testSelector can match a universal selector | tests/css_selector.cc |
2965-| Nesting | X | parseCSS can parse a CSS sheet | parseCSS can parse a nested CSS rule without a &, parseCSS can parse a the parent of a nested CSS rule, parseCSS can parse a nested CSS rule with a pseudo element, parseCSS can parse a parent CSS rule with a property in between sub-classes | tests/css_parser.cc |
2966-| & Nesting | X | parseCSS can parse a CSS sheet | parseCSS can parse a nested CSS rule without a &, parseCSS can parse a the parent of a nested CSS rule, parseCSS can parse a nested CSS rule with a pseudo element, parseCSS can parse a double nested CSS rule with a pseudo element and &, parseCSS can parse a nested CSS rule with a &, parseCSS can parse a parent CSS rule with a property in between sub-classes | tests/css_parser.cc |
2967+| Nesting | X | parseCSS can parse a CSS sheet, parseCSS can parse multiple selectors nested | parseCSS can parse a nested CSS rule without a &, parseCSS can parse a the parent of a nested CSS rule, parseCSS can parse a nested CSS rule with a pseudo element, parseCSS can parse a parent CSS rule with a property in between sub-classes, multi selector test | tests/css_parser.cc |
2968+| & Nesting | X | parseCSS can parse a CSS sheet, parseCSS can parse multiple selectors nested | parseCSS can parse a nested CSS rule without a &, parseCSS can parse a the parent of a nested CSS rule, parseCSS can parse a nested CSS rule with a pseudo element, parseCSS can parse a double nested CSS rule with a pseudo element and &, parseCSS can parse a nested CSS rule with a &, parseCSS can parse a parent CSS rule with a property in between sub-classes, multi selector test | tests/css_parser.cc |
2969
2970-## Combinators
2971+## Combined
2972 | Name | Support | Test Case | Section | Test File |
2973 |-|-|-|-| - |
2974-| Child Combinator | X | testSelector | testSelector can match a child combinator | tests/css_selector.cc |
2975-| Next-Sibling Combinator | X | testSelector | testSelector can match a next sibling combinator | tests/css_selector.cc |
2976+| Child Combined | X | testSelector | testSelector can match a child combined | tests/css_selector.cc |
2977+| Next-Sibling Combined | X | testSelector | testSelector can match a next sibling combined | tests/css_selector.cc |
2978 | Descendant Combinator | X | testSelector | testSelector can match a descendant combinator | tests/css_selector.cc |
2979 | Subsequent-Sibling Combinator | X | testSelector | testSelector can match a subsequent-sibling combinator | tests/css_selector.cc |
2980
2981@@ -37,7 +42,7 @@
2982 | :first-child | X | testSelector | testSelector can match a element with first-child | tests/css_selector.cc | |
2983 | :first-of-type | X | testSelector | testSelector can match a element with first-of-type | tests/css_selector.cc | |
2984 | :focus | | | | | |
2985-| :focus-visable | | | | | |
2986+| :focus-visible | | | | | |
2987 | :focus-within | | | | | |
2988 | :fullscreen | | | | | Videos are not currently supported |
2989 | :future | | | | | |
2990@@ -59,7 +64,7 @@
2991 | :modal | | | | | |
2992 | :muted | | | | | Videos are not currently supported |
2993 | :not() | X | testSelector | testSelector can match :not() selectors | tests/css_selector.cc | |
2994-| :nth-child() | X | testSelector | testSelector can match a :nth-child(even\|odd), testSelector can match a :nth-child(A), testSelector can match a :nth-child(An), testSelector can match a :nth-child(An+B), testSelector can match a :nth-child(An+B of type), testSelector can match a :nth-child(n+B), testSelector can match a :nth-child(A of type), testSelector can match a :nth-child(An of type), testSelector can match a :nth-child(n+B of type) | tests/css_selector.cc | when A is 0 it is changed to a 1, the only case this will cause breaking behavour is if you are trying :nth-child(0n+B) which is the same as calling :nth-child(B). This behavour applys to all nth-*|
2995+| :nth-child() | X | testSelector | testSelector can match a :nth-child(even\|odd), testSelector can match a :nth-child(A), testSelector can match a :nth-child(An), testSelector can match a :nth-child(An+B), testSelector can match a :nth-child(An+B of type), testSelector can match a :nth-child(n+B), testSelector can match a :nth-child(A of type), testSelector can match a :nth-child(An of type), testSelector can match a :nth-child(n+B of type) | tests/css_selector.cc | when A is 0 it is changed to a 1, the only case this will cause breaking behavior is if you are trying :nth-child(0n+B) which is the same as calling :nth-child(B). This behavior applies to all nth-*|
2996 | :nth-last-child() | X | testSelector | testSelector can match a :nth-last-child(even\|odd), testSelector can match a :nth-last-child(A), testSelector can match a :nth-last-child(An), testSelector can match a :nth-last-child(An+B), testSelector can match a :nth-last-child(n+B), testSelector can match a :nth-last-child(An+B of type), testSelector can match a :nth-last-child(A of type), testSelector can match a :nth-last-child(An of type), testSelector can match a :nth-last-child(n+B of type) | tests/css_selector.cc | |
2997 | :nth-last-of-type() | X | testSelector | testSelector can match a :nth-last-of-type(even\|odd), testSelector can match a :nth-last-of-type(A), testSelector can match a :nth-last-of-type(An), testSelector can match a :nth-last-of-type(An+B), testSelector can match a :nth-last-of-type(n+B), | tests/css_selector.cc | |
2998 | :nth-of-type() | X | testSelector | testSelector can match a :nth-of-type(even\|odd), testSelector can match a :nth-of-type(A), testSelector can match a :nth-of-type(An), testSelector can match a :nth-of-type(An+B), testSelector can match a :nth-of-type(n+B), | tests/css_selector.cc | |
2999@@ -92,12 +97,61 @@
3000 | :visited | | | | | |
3001 | :volume-locked | | | | | Video and Audio are not currently supported |
3002 | :where() | X | testSelector |testSelector can match :where() selectors | tests/css_selector.cc | |
3003-
3004-
3005-
3006-
3007-
3008 ## Pseudo Elements
3009+
3010 ## At-rules
3011+| Name | Support | Test Case | Section | Test File | Note |
3012+|-|-|-|-|-|-|
3013+| @charset | / |||| UTF-8/ASCII are the only encodings supported |
3014+| @color-profile | / |||| Too new to support |
3015+| @container ||||||
3016+| @counter-style ||||||
3017+| @font-face ||||||
3018+| @font-feature-values ||||||
3019+| @font-palette-values ||||||
3020+| @import ||||| <string> and <url> support only |
3021+| @keyframes ||||||
3022+| @layer ||||||
3023+| @media ||||||
3024+| @namespace ||||||
3025+| @page | / |||| Will not be supported, currently there are no plans to support printing |
3026+| @position-try ||||| Use this document to check support of features |
3027+| @property ||||||
3028+| @scope ||||| Implementing this would cause some overhead |
3029+| @starting-style ||||||
3030+| @supports | / |||| Use this document to check support of features |
3031+| @view-transition ||||| This is useful but will not be implemented until later |
3032 ## Functions
3033 ## Types
3034+
3035+### Media Queries
3036+| Name | Support | Usage | Note |
3037+|-|-|-|-|
3038+| any-hover | X | window.setMouse("none") | Options "none", "coarse", "fine". If not "none" then any-hover will be set to "hover". |
3039+| any-pointer | X | window.setMouse("fine") | Options "none", "coarse", "fine". |
3040+| aspect-ratio | X | window.getAspectRatio() | Derived from width and height, returned as a double |
3041+| color | * | | All colors are stored as RGBA values |
3042+| color-gamut | * | | Only matches on "srgb" |
3043+| color-index | * | | Only matches on 0 |
3044+| device-posture | * | | Only matches on "continuous" |
3045+| display-mode | * | | All applications will be "standalone" |
3046+| dynamic-range | * | | Only matches on "standard" |
3047+| forced-colors | * | | Only matches on "none" |
3048+| grid | * | | Only matches on 0 |
3049+| height | X | window.setHeight(int) | Supports height, min-height, max-height |
3050+| hover | X | window.setMouse("fine") | Will match any-hover |
3051+| inverted-colors | * | | Only matches on "none" |
3052+| monochrome | * | | Only matches on 0 |
3053+| orientation | X | window.setOrientation("portrait") | Defaults to "landscape" |
3054+| overflow-block | * | | Only matches on "scroll" |
3055+| overflow-inline | * | | Only matches on "scroll" |
3056+| pointer | X | window.setMouse("fine") | Will match any-pointer |
3057+| prefers-color-scheme | X | window.setColorScheme("light" \|\| "dark") | Defaults to "light" |
3058+| prefers-contrast | X | window.setContrast("more" \|\| "less" \|\| "no-preference") | Defaults to "no-preference" |
3059+| prefers-reduced-motion | X | window.setReducedMotion("reduce" \|\| "no-preference") | Defaults to "no-preference" |
3060+| prefers-reduced-transparency | X | window.setReducedTransparency("reduce" \|\| "no-preference") | Defaults to "no-preference" |
3061+| resolution | X | window.setResolution(int) | Defaults to 72dpi, accepts a int in dpi |
3062+| scripting | / | | Not needed |
3063+| update | X | window.setUpdate("fast" \|\| "slow" \|\| "none") | Defaults to "fast" |
3064+| video-dynamic-range | * | | Only matches on "standard" |
3065+| width | X | window.setWidth(int) | Supports width, min-width, max-width |
3066diff --git a/docs/evoke.yaml b/docs/evoke.yaml
3067deleted file mode 100644
3068index 1f23f5d..0000000
3069--- a/docs/evoke.yaml
3070+++ /dev/null
3071@@ -1 +0,0 @@
3072-siteName: Grim
3073diff --git a/docs/partials/navbar.html b/docs/partials/navbar.html
3074deleted file mode 100644
3075index 666d5d0..0000000
3076--- a/docs/partials/navbar.html
3077+++ /dev/null
3078@@ -1,23 +0,0 @@
3079-<aside style="min-width: 200px">
3080- <img src="/logo.webp"/ width="150px">
3081- <ul>
3082- <li>
3083- <strong><a href="/">Home</a></strong>
3084- </li>
3085- </ul>
3086- <details open>
3087- <summary>Links</summary>
3088- <ul>
3089- <li><a href="https://src.grimui.com">Source</a></li>
3090- <li><a href="https://tracker.grimui.com">Trackers</a></li>
3091- </ul>
3092- </details>
3093- <details open>
3094- <summary>Feature Support</summary>
3095- <ul>
3096- <li><a href="/features/supported-css-selectors.html">CSS Selectors</a></li>
3097- <li><a href="/features/supported-html-tags.html">HTML Tags</a></li>
3098- <li><a href="/features/supported-dom-apis.html">DOM APIs</a></li>
3099- </ul>
3100- </details>
3101-</aside>