From b65d549e64438eb06c4bd4a09efde7f41ded698b Mon Sep 17 00:00:00 2001
From: Oliver Bock <oliver.bock@aei.mpg.de>
Date: Wed, 9 Apr 2008 11:55:46 +0200
Subject: [PATCH] Setup and generic files for doxygen documentation
---
Doxyfile | 1294 ++++++++++++++++++++++++++++++++++++
doc/default/aei_full.png | Bin 0 -> 7675 bytes
doc/default/footer.html | 10 +
doc/default/header.html | 6 +
doc/default/stylesheet.css | 358 ++++++++++
5 files changed, 1668 insertions(+)
create mode 100644 Doxyfile
create mode 100644 doc/default/aei_full.png
create mode 100644 doc/default/footer.html
create mode 100644 doc/default/header.html
create mode 100644 doc/default/stylesheet.css
diff --git a/Doxyfile b/Doxyfile
new file mode 100644
index 0000000..7f083be
--- /dev/null
+++ b/Doxyfile
@@ -0,0 +1,1294 @@
+# Doxyfile 1.5.3
+
+# This file describes the settings to be used by the documentation system
+# doxygen (www.doxygen.org) for a project
+#
+# All text after a hash (#) is considered a comment and will be ignored
+# The format is:
+# TAG = value [value, ...]
+# For lists items can also be appended using:
+# TAG += value [value, ...]
+# Values that contain spaces should be placed between quotes (" ")
+
+#---------------------------------------------------------------------------
+# Project related configuration options
+#---------------------------------------------------------------------------
+
+# This tag specifies the encoding used for all characters in the config file that
+# follow. The default is UTF-8 which is also the encoding used for all text before
+# the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into
+# libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of
+# possible encodings.
+
+DOXYFILE_ENCODING = UTF-8
+
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
+# by quotes) that should identify the project.
+
+PROJECT_NAME = "Einstein@Home Graphics Application"
+
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.
+# This could be handy for archiving the generated documentation or
+# if some version control system is used.
+
+PROJECT_NUMBER = 0.2.0
+
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
+# base path where the generated documentation will be put.
+# If a relative path is entered, it will be relative to the location
+# where doxygen was started. If left blank the current directory will be used.
+
+OUTPUT_DIRECTORY = doc
+
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
+# 4096 sub-directories (in 2 levels) under the output directory of each output
+# format and will distribute the generated files over these directories.
+# Enabling this option can be useful when feeding doxygen a huge amount of
+# source files, where putting all generated files in the same directory would
+# otherwise cause performance problems for the file system.
+
+CREATE_SUBDIRS = NO
+
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
+# documentation generated by doxygen is written. Doxygen will use this
+# information to generate all constant output in the proper language.
+# The default language is English, other supported languages are:
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
+# Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian,
+# Italian, Japanese, Japanese-en (Japanese with English messages), Korean,
+# Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian,
+# Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
+
+OUTPUT_LANGUAGE = English
+
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
+# include brief member descriptions after the members that are listed in
+# the file and class documentation (similar to JavaDoc).
+# Set to NO to disable this.
+
+BRIEF_MEMBER_DESC = YES
+
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
+# the brief description of a member or function before the detailed description.
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
+# brief descriptions will be completely suppressed.
+
+REPEAT_BRIEF = YES
+
+# This tag implements a quasi-intelligent brief description abbreviator
+# that is used to form the text in various listings. Each string
+# in this list, if found as the leading text of the brief description, will be
+# stripped from the text and the result after processing the whole list, is
+# used as the annotated text. Otherwise, the brief description is used as-is.
+# If left blank, the following values are used ("$name" is automatically
+# replaced with the name of the entity): "The $name class" "The $name widget"
+# "The $name file" "is" "provides" "specifies" "contains"
+# "represents" "a" "an" "the"
+
+ABBREVIATE_BRIEF = "The $name class " "The $name widget " "The $name file " is provides specifies contains represents a an the
+
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
+# Doxygen will generate a detailed section even if there is only a brief
+# description.
+
+ALWAYS_DETAILED_SEC = YES
+
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
+# inherited members of a class in the documentation of that class as if those
+# members were ordinary class members. Constructors, destructors and assignment
+# operators of the base classes will not be shown.
+
+INLINE_INHERITED_MEMB = NO
+
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
+# path before files name in the file list and in the header files. If set
+# to NO the shortest path that makes the file name unique will be used.
+
+FULL_PATH_NAMES = YES
+
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
+# can be used to strip a user-defined part of the path. Stripping is
+# only done if one of the specified strings matches the left-hand part of
+# the path. The tag can be used to show relative paths in the file list.
+# If left blank the directory from which doxygen is run is used as the
+# path to strip.
+
+STRIP_FROM_PATH =
+
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
+# the path mentioned in the documentation of a class, which tells
+# the reader which header file to include in order to use a class.
+# If left blank only the name of the header file containing the class
+# definition is used. Otherwise one should specify the include paths that
+# are normally passed to the compiler using the -I flag.
+
+STRIP_FROM_INC_PATH =
+
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
+# (but less readable) file names. This can be useful is your file systems
+# doesn't support long names like on DOS, Mac, or CD-ROM.
+
+SHORT_NAMES = NO
+
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
+# will interpret the first line (until the first dot) of a JavaDoc-style
+# comment as the brief description. If set to NO, the JavaDoc
+# comments will behave just like regular Qt-style comments
+# (thus requiring an explicit @brief command for a brief description.)
+
+JAVADOC_AUTOBRIEF = NO
+
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
+# interpret the first line (until the first dot) of a Qt-style
+# comment as the brief description. If set to NO, the comments
+# will behave just like regular Qt-style comments (thus requiring
+# an explicit \brief command for a brief description.)
+
+QT_AUTOBRIEF = NO
+
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///
+# comments) as a brief description. This used to be the default behaviour.
+# The new default is to treat a multi-line C++ comment block as a detailed
+# description. Set this tag to YES if you prefer the old behaviour instead.
+
+MULTILINE_CPP_IS_BRIEF = NO
+
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen
+# will output the detailed description near the top, like JavaDoc.
+# If set to NO, the detailed description appears after the member
+# documentation.
+
+DETAILS_AT_TOP = NO
+
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
+# member inherits the documentation from any documented member that it
+# re-implements.
+
+INHERIT_DOCS = YES
+
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
+# a new page for each member. If set to NO, the documentation of a member will
+# be part of the file/class/namespace that contains it.
+
+SEPARATE_MEMBER_PAGES = NO
+
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.
+# Doxygen uses this value to replace tabs by spaces in code fragments.
+
+TAB_SIZE = 8
+
+# This tag can be used to specify a number of aliases that acts
+# as commands in the documentation. An alias has the form "name=value".
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to
+# put the command \sideeffect (or @sideeffect) in the documentation, which
+# will result in a user-defined paragraph with heading "Side Effects:".
+# You can put \n's in the value part of an alias to insert newlines.
+
+ALIASES =
+
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
+# sources only. Doxygen will then generate output that is more tailored for C.
+# For instance, some of the names that are used will be different. The list
+# of all members will be omitted, etc.
+
+OPTIMIZE_OUTPUT_FOR_C = NO
+
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
+# sources only. Doxygen will then generate output that is more tailored for Java.
+# For instance, namespaces will be presented as packages, qualified scopes
+# will look different, etc.
+
+OPTIMIZE_OUTPUT_JAVA = NO
+
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to
+# include (a tag file for) the STL sources as input, then you should
+# set this tag to YES in order to let doxygen match functions declarations and
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
+# func(std::string) {}). This also make the inheritance and collaboration
+# diagrams that involve STL classes more complete and accurate.
+
+BUILTIN_STL_SUPPORT = NO
+
+# If you use Microsoft's C++/CLI language, you should set this option to YES to
+# enable parsing support.
+
+CPP_CLI_SUPPORT = NO
+
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
+# tag is set to YES, then doxygen will reuse the documentation of the first
+# member in the group (if any) for the other members of the group. By default
+# all members of a group must be documented explicitly.
+
+DISTRIBUTE_GROUP_DOC = NO
+
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
+# the same type (for instance a group of public functions) to be put as a
+# subgroup of that type (e.g. under the Public Functions section). Set it to
+# NO to prevent subgrouping. Alternatively, this can be done per class using
+# the \nosubgrouping command.
+
+SUBGROUPING = YES
+
+#---------------------------------------------------------------------------
+# Build related configuration options
+#---------------------------------------------------------------------------
+
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
+# documentation are documented, even if no documentation was available.
+# Private class members and static file members will be hidden unless
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
+
+EXTRACT_ALL = YES
+
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
+# will be included in the documentation.
+
+EXTRACT_PRIVATE = YES
+
+# If the EXTRACT_STATIC tag is set to YES all static members of a file
+# will be included in the documentation.
+
+EXTRACT_STATIC = NO
+
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
+# defined locally in source files will be included in the documentation.
+# If set to NO only classes defined in header files are included.
+
+EXTRACT_LOCAL_CLASSES = YES
+
+# This flag is only useful for Objective-C code. When set to YES local
+# methods, which are defined in the implementation section but not in
+# the interface are included in the documentation.
+# If set to NO (the default) only methods in the interface are included.
+
+EXTRACT_LOCAL_METHODS = YES
+
+# If this flag is set to YES, the members of anonymous namespaces will be extracted
+# and appear in the documentation as a namespace called 'anonymous_namespace{file}',
+# where file will be replaced with the base name of the file that contains the anonymous
+# namespace. By default anonymous namespace are hidden.
+
+EXTRACT_ANON_NSPACES = NO
+
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
+# undocumented members of documented classes, files or namespaces.
+# If set to NO (the default) these members will be included in the
+# various overviews, but no documentation section is generated.
+# This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_MEMBERS = NO
+
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
+# undocumented classes that are normally visible in the class hierarchy.
+# If set to NO (the default) these classes will be included in the various
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
+
+HIDE_UNDOC_CLASSES = NO
+
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
+# friend (class|struct|union) declarations.
+# If set to NO (the default) these declarations will be included in the
+# documentation.
+
+HIDE_FRIEND_COMPOUNDS = NO
+
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
+# documentation blocks found inside the body of a function.
+# If set to NO (the default) these blocks will be appended to the
+# function's detailed documentation block.
+
+HIDE_IN_BODY_DOCS = NO
+
+# The INTERNAL_DOCS tag determines if documentation
+# that is typed after a \internal command is included. If the tag is set
+# to NO (the default) then the documentation will be excluded.
+# Set it to YES to include the internal documentation.
+
+INTERNAL_DOCS = YES
+
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
+# file names in lower-case letters. If set to YES upper-case letters are also
+# allowed. This is useful if you have classes or files whose names only differ
+# in case and if your file system supports case sensitive file names. Windows
+# and Mac users are advised to set this option to NO.
+
+CASE_SENSE_NAMES = YES
+
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
+# will show members with their full class and namespace scopes in the
+# documentation. If set to YES the scope will be hidden.
+
+HIDE_SCOPE_NAMES = NO
+
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
+# will put a list of the files that are included by a file in the documentation
+# of that file.
+
+SHOW_INCLUDE_FILES = YES
+
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
+# is inserted in the documentation for inline members.
+
+INLINE_INFO = YES
+
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
+# will sort the (detailed) documentation of file and class members
+# alphabetically by member name. If set to NO the members will appear in
+# declaration order.
+
+SORT_MEMBER_DOCS = YES
+
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
+# brief documentation of file, namespace and class members alphabetically
+# by member name. If set to NO (the default) the members will appear in
+# declaration order.
+
+SORT_BRIEF_DOCS = YES
+
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
+# sorted by fully-qualified names, including namespaces. If set to
+# NO (the default), the class list will be sorted only by class name,
+# not including the namespace part.
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
+# Note: This option applies only to the class list, not to the
+# alphabetical list.
+
+SORT_BY_SCOPE_NAME = YES
+
+# The GENERATE_TODOLIST tag can be used to enable (YES) or
+# disable (NO) the todo list. This list is created by putting \todo
+# commands in the documentation.
+
+GENERATE_TODOLIST = YES
+
+# The GENERATE_TESTLIST tag can be used to enable (YES) or
+# disable (NO) the test list. This list is created by putting \test
+# commands in the documentation.
+
+GENERATE_TESTLIST = YES
+
+# The GENERATE_BUGLIST tag can be used to enable (YES) or
+# disable (NO) the bug list. This list is created by putting \bug
+# commands in the documentation.
+
+GENERATE_BUGLIST = YES
+
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
+# disable (NO) the deprecated list. This list is created by putting
+# \deprecated commands in the documentation.
+
+GENERATE_DEPRECATEDLIST = YES
+
+# The ENABLED_SECTIONS tag can be used to enable conditional
+# documentation sections, marked by \if sectionname ... \endif.
+
+ENABLED_SECTIONS =
+
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
+# the initial value of a variable or define consists of for it to appear in
+# the documentation. If the initializer consists of more lines than specified
+# here it will be hidden. Use a value of 0 to hide initializers completely.
+# The appearance of the initializer of individual variables and defines in the
+# documentation can be controlled using \showinitializer or \hideinitializer
+# command in the documentation regardless of this setting.
+
+MAX_INITIALIZER_LINES = 30
+
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
+# at the bottom of the documentation of classes and structs. If set to YES the
+# list will mention the files that were used to generate the documentation.
+
+SHOW_USED_FILES = YES
+
+# If the sources in your project are distributed over multiple directories
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
+# in the documentation. The default is NO.
+
+SHOW_DIRECTORIES = NO
+
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that
+# doxygen should invoke to get the current version for each file (typically from the
+# version control system). Doxygen will invoke the program by executing (via
+# popen()) the command <command> <input-file>, where <command> is the value of
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
+# provided by doxygen. Whatever the program writes to standard output
+# is used as the file version. See the manual for examples.
+
+FILE_VERSION_FILTER =
+
+#---------------------------------------------------------------------------
+# configuration options related to warning and progress messages
+#---------------------------------------------------------------------------
+
+# The QUIET tag can be used to turn on/off the messages that are generated
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
+
+QUIET = NO
+
+# The WARNINGS tag can be used to turn on/off the warning messages that are
+# generated by doxygen. Possible values are YES and NO. If left blank
+# NO is used.
+
+WARNINGS = YES
+
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
+# automatically be disabled.
+
+WARN_IF_UNDOCUMENTED = YES
+
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
+# potential errors in the documentation, such as not documenting some
+# parameters in a documented function, or documenting parameters that
+# don't exist or using markup commands wrongly.
+
+WARN_IF_DOC_ERROR = YES
+
+# This WARN_NO_PARAMDOC option can be abled to get warnings for
+# functions that are documented, but have no documentation for their parameters
+# or return value. If set to NO (the default) doxygen will only warn about
+# wrong or incomplete parameter documentation, but not about the absence of
+# documentation.
+
+WARN_NO_PARAMDOC = YES
+
+# The WARN_FORMAT tag determines the format of the warning messages that
+# doxygen can produce. The string should contain the $file, $line, and $text
+# tags, which will be replaced by the file and line number from which the
+# warning originated and the warning text. Optionally the format may contain
+# $version, which will be replaced by the version of the file (if it could
+# be obtained via FILE_VERSION_FILTER)
+
+WARN_FORMAT = "$file:$line: $text "
+
+# The WARN_LOGFILE tag can be used to specify a file to which warning
+# and error messages should be written. If left blank the output is written
+# to stderr.
+
+WARN_LOGFILE =
+
+#---------------------------------------------------------------------------
+# configuration options related to the input files
+#---------------------------------------------------------------------------
+
+# The INPUT tag can be used to specify the files and/or directories that contain
+# documented source files. You may enter file names like "myfile.cpp" or
+# directories like "/usr/src/myproject". Separate the files or directories
+# with spaces.
+
+INPUT = ../
+
+# This tag can be used to specify the character encoding of the source files that
+# doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default
+# input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding.
+# See http://www.gnu.org/software/libiconv for the list of possible encodings.
+
+INPUT_ENCODING = UTF-8
+
+# If the value of the INPUT tag contains directories, you can use the
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
+# and *.h) to filter out the source-files in the directories. If left
+# blank the following patterns are tested:
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
+# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py
+
+FILE_PATTERNS = *.cpp *.H *.moc *.h *.CPP
+
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories
+# should be searched for input files as well. Possible values are YES and NO.
+# If left blank NO is used.
+
+RECURSIVE = YES
+
+# The EXCLUDE tag can be used to specify files and/or directories that should
+# excluded from the INPUT source files. This way you can easily exclude a
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
+
+EXCLUDE = *.svn doxygen
+
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
+# directories that are symbolic links (a Unix filesystem feature) are excluded
+# from the input.
+
+EXCLUDE_SYMLINKS = NO
+
+# If the value of the INPUT tag contains directories, you can use the
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
+# certain files from those directories. Note that the wildcards are matched
+# against the file with absolute path, so to exclude all test directories
+# for example use the pattern */test/*
+
+EXCLUDE_PATTERNS = resources.cpp
+
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
+# (namespaces, classes, functions, etc.) that should be excluded from the output.
+# The symbol name can be a fully qualified name, a word, or if the wildcard * is used,
+# a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test
+
+EXCLUDE_SYMBOLS =
+
+# The EXAMPLE_PATH tag can be used to specify one or more files or
+# directories that contain example code fragments that are included (see
+# the \include command).
+
+EXAMPLE_PATH =
+
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
+# and *.h) to filter out the source-files in the directories. If left
+# blank all files are included.
+
+EXAMPLE_PATTERNS = *
+
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
+# searched for input files to be used with the \include or \dontinclude
+# commands irrespective of the value of the RECURSIVE tag.
+# Possible values are YES and NO. If left blank NO is used.
+
+EXAMPLE_RECURSIVE = NO
+
+# The IMAGE_PATH tag can be used to specify one or more files or
+# directories that contain image that are included in the documentation (see
+# the \image command).
+
+IMAGE_PATH =
+
+# The INPUT_FILTER tag can be used to specify a program that doxygen should
+# invoke to filter for each input file. Doxygen will invoke the filter program
+# by executing (via popen()) the command <filter> <input-file>, where <filter>
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
+# input file. Doxygen will then use the output that the filter program writes
+# to standard output. If FILTER_PATTERNS is specified, this tag will be
+# ignored.
+
+INPUT_FILTER =
+
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
+# basis. Doxygen will compare the file name with each pattern and apply the
+# filter if there is a match. The filters are a list of the form:
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
+# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
+# is applied to all files.
+
+FILTER_PATTERNS =
+
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
+# INPUT_FILTER) will be used to filter the input files when producing source
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
+
+FILTER_SOURCE_FILES = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to source browsing
+#---------------------------------------------------------------------------
+
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will
+# be generated. Documented entities will be cross-referenced with these sources.
+# Note: To get rid of all source code in the generated output, make sure also
+# VERBATIM_HEADERS is set to NO. If you have enabled CALL_GRAPH or CALLER_GRAPH
+# then you must also enable this option. If you don't then doxygen will produce
+# a warning and turn it on anyway
+
+SOURCE_BROWSER = NO
+
+# Setting the INLINE_SOURCES tag to YES will include the body
+# of functions and classes directly in the documentation.
+
+INLINE_SOURCES = NO
+
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
+# doxygen to hide any special comment blocks from generated source code
+# fragments. Normal C and C++ comments will always remain visible.
+
+STRIP_CODE_COMMENTS = YES
+
+# If the REFERENCED_BY_RELATION tag is set to YES (the default)
+# then for each documented function all documented
+# functions referencing it will be listed.
+
+REFERENCED_BY_RELATION = YES
+
+# If the REFERENCES_RELATION tag is set to YES (the default)
+# then for each documented function all documented entities
+# called/used by that function will be listed.
+
+REFERENCES_RELATION = YES
+
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
+# link to the source code. Otherwise they will link to the documentstion.
+
+REFERENCES_LINK_SOURCE = NO
+
+# If the USE_HTAGS tag is set to YES then the references to source code
+# will point to the HTML generated by the htags(1) tool instead of doxygen
+# built-in source browser. The htags tool is part of GNU's global source
+# tagging system (see http://www.gnu.org/software/global/global.html). You
+# will need version 4.8.6 or higher.
+
+USE_HTAGS = NO
+
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
+# will generate a verbatim copy of the header file for each class for
+# which an include is specified. Set to NO to disable this.
+
+VERBATIM_HEADERS = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the alphabetical class index
+#---------------------------------------------------------------------------
+
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
+# of all compounds will be generated. Enable this if the project
+# contains a lot of classes, structs, unions or interfaces.
+
+ALPHABETICAL_INDEX = YES
+
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
+# in which this list will be split (can be a number in the range [1..20])
+
+COLS_IN_ALPHA_INDEX = 5
+
+# In case all classes in a project start with a common prefix, all
+# classes will be put under the same header in the alphabetical index.
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
+# should be ignored while generating the index headers.
+
+IGNORE_PREFIX =
+
+#---------------------------------------------------------------------------
+# configuration options related to the HTML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
+# generate HTML output.
+
+GENERATE_HTML = YES
+
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `html' will be used as the default path.
+
+HTML_OUTPUT = html
+
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
+# doxygen will generate files with .html extension.
+
+HTML_FILE_EXTENSION = .html
+
+# The HTML_HEADER tag can be used to specify a personal HTML header for
+# each generated HTML page. If it is left blank doxygen will generate a
+# standard header.
+
+HTML_HEADER =
+
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for
+# each generated HTML page. If it is left blank doxygen will generate a
+# standard footer.
+
+HTML_FOOTER = doc/default/footer.html
+
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
+# style sheet that is used by each HTML page. It can be used to
+# fine-tune the look of the HTML output. If the tag is left blank doxygen
+# will generate a default style sheet. Note that doxygen will try to copy
+# the style sheet file to the HTML output directory, so don't put your own
+# stylesheet in the HTML output directory as well, or it will be erased!
+
+HTML_STYLESHEET =
+
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
+# files or namespaces will be aligned in HTML using tables. If set to
+# NO a bullet list will be used.
+
+HTML_ALIGN_MEMBERS = YES
+
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files
+# will be generated that can be used as input for tools like the
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
+# of the generated HTML documentation.
+
+GENERATE_HTMLHELP = NO
+
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
+# documentation will contain sections that can be hidden and shown after the
+# page has loaded. For this to work a browser that supports
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
+
+HTML_DYNAMIC_SECTIONS = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
+# be used to specify the file name of the resulting .chm file. You
+# can add a path in front of the file if the result should not be
+# written to the html output directory.
+
+CHM_FILE =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
+# be used to specify the location (absolute path including file name) of
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
+# the HTML help compiler on the generated index.hhp.
+
+HHC_LOCATION =
+
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
+# controls if a separate .chi index file is generated (YES) or that
+# it should be included in the master .chm file (NO).
+
+GENERATE_CHI = NO
+
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
+# controls whether a binary table of contents is generated (YES) or a
+# normal table of contents (NO) in the .chm file.
+
+BINARY_TOC = NO
+
+# The TOC_EXPAND flag can be set to YES to add extra items for group members
+# to the contents of the HTML help documentation and to the tree view.
+
+TOC_EXPAND = YES
+
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
+# top of each HTML page. The value NO (the default) enables the index and
+# the value YES disables it.
+
+DISABLE_INDEX = NO
+
+# This tag can be used to set the number of enum values (range [1..20])
+# that doxygen will group on one line in the generated HTML documentation.
+
+ENUM_VALUES_PER_LINE = 4
+
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
+# generated containing a tree-like index structure (just like the one that
+# is generated for HTML Help). For this to work a browser that supports
+# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
+# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
+# probably better off using the HTML help feature.
+
+GENERATE_TREEVIEW = YES
+
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
+# used to set the initial width (in pixels) of the frame in which the tree
+# is shown.
+
+TREEVIEW_WIDTH = 250
+
+#---------------------------------------------------------------------------
+# configuration options related to the LaTeX output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
+# generate Latex output.
+
+GENERATE_LATEX = NO
+
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `latex' will be used as the default path.
+
+LATEX_OUTPUT = latex
+
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
+# invoked. If left blank `latex' will be used as the default command name.
+
+LATEX_CMD_NAME = latex
+
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
+# generate index for LaTeX. If left blank `makeindex' will be used as the
+# default command name.
+
+MAKEINDEX_CMD_NAME = makeindex
+
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
+# LaTeX documents. This may be useful for small projects and may help to
+# save some trees in general.
+
+COMPACT_LATEX = NO
+
+# The PAPER_TYPE tag can be used to set the paper type that is used
+# by the printer. Possible values are: a4, a4wide, letter, legal and
+# executive. If left blank a4wide will be used.
+
+PAPER_TYPE = a4
+
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
+# packages that should be included in the LaTeX output.
+
+EXTRA_PACKAGES =
+
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
+# the generated latex document. The header should contain everything until
+# the first chapter. If it is left blank doxygen will generate a
+# standard header. Notice: only use this tag if you know what you are doing!
+
+LATEX_HEADER =
+
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will
+# contain links (just like the HTML output) instead of page references
+# This makes the output suitable for online browsing using a pdf viewer.
+
+PDF_HYPERLINKS = YES
+
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
+# plain latex in the generated Makefile. Set this option to YES to get a
+# higher quality PDF documentation.
+
+USE_PDFLATEX = YES
+
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
+# command to the generated LaTeX files. This will instruct LaTeX to keep
+# running if errors occur, instead of asking the user for help.
+# This option is also used when generating formulas in HTML.
+
+LATEX_BATCHMODE = NO
+
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not
+# include the index chapters (such as File Index, Compound Index, etc.)
+# in the output.
+
+LATEX_HIDE_INDICES = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the RTF output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
+# The RTF output is optimized for Word 97 and may not look very pretty with
+# other RTF readers or editors.
+
+GENERATE_RTF = NO
+
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `rtf' will be used as the default path.
+
+RTF_OUTPUT = rtf
+
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
+# RTF documents. This may be useful for small projects and may help to
+# save some trees in general.
+
+COMPACT_RTF = NO
+
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
+# will contain hyperlink fields. The RTF file will
+# contain links (just like the HTML output) instead of page references.
+# This makes the output suitable for online browsing using WORD or other
+# programs which support those fields.
+# Note: wordpad (write) and others do not support links.
+
+RTF_HYPERLINKS = NO
+
+# Load stylesheet definitions from file. Syntax is similar to doxygen's
+# config file, i.e. a series of assignments. You only have to provide
+# replacements, missing definitions are set to their default value.
+
+RTF_STYLESHEET_FILE =
+
+# Set optional variables used in the generation of an rtf document.
+# Syntax is similar to doxygen's config file.
+
+RTF_EXTENSIONS_FILE =
+
+#---------------------------------------------------------------------------
+# configuration options related to the man page output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
+# generate man pages
+
+GENERATE_MAN = NO
+
+# The MAN_OUTPUT tag is used to specify where the man pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `man' will be used as the default path.
+
+MAN_OUTPUT = man
+
+# The MAN_EXTENSION tag determines the extension that is added to
+# the generated man pages (default is the subroutine's section .3)
+
+MAN_EXTENSION = .3
+
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
+# then it will generate one additional man file for each entity
+# documented in the real man page(s). These additional files
+# only source the real man page, but without them the man command
+# would be unable to find the correct page. The default is NO.
+
+MAN_LINKS = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the XML output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_XML tag is set to YES Doxygen will
+# generate an XML file that captures the structure of
+# the code including all documentation.
+
+GENERATE_XML = NO
+
+# The XML_OUTPUT tag is used to specify where the XML pages will be put.
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
+# put in front of it. If left blank `xml' will be used as the default path.
+
+XML_OUTPUT = xml
+
+# The XML_SCHEMA tag can be used to specify an XML schema,
+# which can be used by a validating XML parser to check the
+# syntax of the XML files.
+
+XML_SCHEMA =
+
+# The XML_DTD tag can be used to specify an XML DTD,
+# which can be used by a validating XML parser to check the
+# syntax of the XML files.
+
+XML_DTD =
+
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
+# dump the program listings (including syntax highlighting
+# and cross-referencing information) to the XML output. Note that
+# enabling this will significantly increase the size of the XML output.
+
+XML_PROGRAMLISTING = YES
+
+#---------------------------------------------------------------------------
+# configuration options for the AutoGen Definitions output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
+# generate an AutoGen Definitions (see autogen.sf.net) file
+# that captures the structure of the code including all
+# documentation. Note that this feature is still experimental
+# and incomplete at the moment.
+
+GENERATE_AUTOGEN_DEF = NO
+
+#---------------------------------------------------------------------------
+# configuration options related to the Perl module output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will
+# generate a Perl module file that captures the structure of
+# the code including all documentation. Note that this
+# feature is still experimental and incomplete at the
+# moment.
+
+GENERATE_PERLMOD = NO
+
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able
+# to generate PDF and DVI output from the Perl module output.
+
+PERLMOD_LATEX = NO
+
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
+# nicely formatted so it can be parsed by a human reader. This is useful
+# if you want to understand what is going on. On the other hand, if this
+# tag is set to NO the size of the Perl module output will be much smaller
+# and Perl will parse it just the same.
+
+PERLMOD_PRETTY = YES
+
+# The names of the make variables in the generated doxyrules.make file
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
+# This is useful so different doxyrules.make files included by the same
+# Makefile don't overwrite each other's variables.
+
+PERLMOD_MAKEVAR_PREFIX =
+
+#---------------------------------------------------------------------------
+# Configuration options related to the preprocessor
+#---------------------------------------------------------------------------
+
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
+# evaluate all C-preprocessor directives found in the sources and include
+# files.
+
+ENABLE_PREPROCESSING = YES
+
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
+# names in the source code. If set to NO (the default) only conditional
+# compilation will be performed. Macro expansion can be done in a controlled
+# way by setting EXPAND_ONLY_PREDEF to YES.
+
+MACRO_EXPANSION = YES
+
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
+# then the macro expansion is limited to the macros specified with the
+# PREDEFINED and EXPAND_AS_DEFINED tags.
+
+EXPAND_ONLY_PREDEF = NO
+
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
+# in the INCLUDE_PATH (see below) will be search if a #include is found.
+
+SEARCH_INCLUDES = YES
+
+# The INCLUDE_PATH tag can be used to specify one or more directories that
+# contain include files that are not input files but should be processed by
+# the preprocessor.
+
+INCLUDE_PATH =
+
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
+# patterns (like *.h and *.hpp) to filter out the header-files in the
+# directories. If left blank, the patterns specified with FILE_PATTERNS will
+# be used.
+
+INCLUDE_FILE_PATTERNS =
+
+# The PREDEFINED tag can be used to specify one or more macro names that
+# are defined before the preprocessor is started (similar to the -D option of
+# gcc). The argument of the tag is a list of macros of the form: name
+# or name=definition (no spaces). If the definition and the = are
+# omitted =1 is assumed. To prevent a macro definition from being
+# undefined via #undef or recursively expanded use the := operator
+# instead of the = operator.
+
+PREDEFINED =
+
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
+# this tag can be used to specify a list of macro names that should be expanded.
+# The macro definition that is found in the sources will be used.
+# Use the PREDEFINED tag if you want to use a different macro definition.
+
+EXPAND_AS_DEFINED =
+
+# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
+# doxygen's preprocessor will remove all function-like macros that are alone
+# on a line, have an all uppercase name, and do not end with a semicolon. Such
+# function macros are typically used for boiler-plate code, and will confuse
+# the parser if not removed.
+
+SKIP_FUNCTION_MACROS = NO
+
+#---------------------------------------------------------------------------
+# Configuration::additions related to external references
+#---------------------------------------------------------------------------
+
+# The TAGFILES option can be used to specify one or more tagfiles.
+# Optionally an initial location of the external documentation
+# can be added for each tagfile. The format of a tag file without
+# this location is as follows:
+# TAGFILES = file1 file2 ...
+# Adding location for the tag files is done as follows:
+# TAGFILES = file1=loc1 "file2 = loc2" ...
+# where "loc1" and "loc2" can be relative or absolute paths or
+# URLs. If a location is present for each tag, the installdox tool
+# does not have to be run to correct the links.
+# Note that each tag file must have a unique name
+# (where the name does NOT include the path)
+# If a tag file is not located in the directory in which doxygen
+# is run, you must also specify the path to the tagfile here.
+
+TAGFILES =
+
+# When a file name is specified after GENERATE_TAGFILE, doxygen will create
+# a tag file that is based on the input files it reads.
+
+GENERATE_TAGFILE = starsphere.tag
+
+# If the ALLEXTERNALS tag is set to YES all external classes will be listed
+# in the class index. If set to NO only the inherited external classes
+# will be listed.
+
+ALLEXTERNALS = NO
+
+# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
+# in the modules index. If set to NO, only the current project's groups will
+# be listed.
+
+EXTERNAL_GROUPS = YES
+
+# The PERL_PATH should be the absolute path and name of the perl script
+# interpreter (i.e. the result of `which perl').
+
+PERL_PATH = /usr/bin/perl
+
+#---------------------------------------------------------------------------
+# Configuration options related to the dot tool
+#---------------------------------------------------------------------------
+
+# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
+# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
+# or super classes. Setting the tag to NO turns the diagrams off. Note that
+# this option is superseded by the HAVE_DOT option below. This is only a
+# fallback. It is recommended to install and use dot, since it yields more
+# powerful graphs.
+
+CLASS_DIAGRAMS = NO
+
+# You can define message sequence charts within doxygen comments using the \msc
+# command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to
+# produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to
+# specify the directory where the mscgen tool resides. If left empty the tool is assumed to
+# be found in the default search path.
+
+MSCGEN_PATH =
+
+# If set to YES, the inheritance and collaboration graphs will hide
+# inheritance and usage relations if the target is undocumented
+# or is not a class.
+
+HIDE_UNDOC_RELATIONS = NO
+
+# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
+# available from the path. This tool is part of Graphviz, a graph visualization
+# toolkit from AT&T and Lucent Bell Labs. The other options in this section
+# have no effect if this option is set to NO (the default)
+
+HAVE_DOT = YES
+
+# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for each documented class showing the direct and
+# indirect inheritance relations. Setting this tag to YES will force the
+# the CLASS_DIAGRAMS tag to NO.
+
+CLASS_GRAPH = YES
+
+# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for each documented class showing the direct and
+# indirect implementation dependencies (inheritance, containment, and
+# class references variables) of the class with other documented classes.
+
+COLLABORATION_GRAPH = YES
+
+# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
+# will generate a graph for groups, showing the direct groups dependencies
+
+GROUP_GRAPHS = NO
+
+# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
+# collaboration diagrams in a style similar to the OMG's Unified Modeling
+# Language.
+
+UML_LOOK = NO
+
+# If set to YES, the inheritance and collaboration graphs will show the
+# relations between templates and their instances.
+
+TEMPLATE_RELATIONS = YES
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
+# tags are set to YES then doxygen will generate a graph for each documented
+# file showing the direct and indirect include dependencies of the file with
+# other documented files.
+
+INCLUDE_GRAPH = YES
+
+# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
+# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
+# documented header file showing the documented files that directly or
+# indirectly include this file.
+
+INCLUDED_BY_GRAPH = YES
+
+# If the CALL_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will
+# generate a call dependency graph for every global function or class method.
+# Note that enabling this option will significantly increase the time of a run.
+# So in most cases it will be better to enable call graphs for selected
+# functions only using the \callgraph command.
+
+CALL_GRAPH = NO
+
+# If the CALLER_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will
+# generate a caller dependency graph for every global function or class method.
+# Note that enabling this option will significantly increase the time of a run.
+# So in most cases it will be better to enable caller graphs for selected
+# functions only using the \callergraph command.
+
+CALLER_GRAPH = NO
+
+# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
+# will graphical hierarchy of all classes instead of a textual one.
+
+GRAPHICAL_HIERARCHY = YES
+
+# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
+# then doxygen will show the dependencies a directory has on other directories
+# in a graphical way. The dependency relations are determined by the #include
+# relations between the files in the directories.
+
+DIRECTORY_GRAPH = YES
+
+# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
+# generated by dot. Possible values are png, jpg, or gif
+# If left blank png will be used.
+
+DOT_IMAGE_FORMAT = png
+
+# The tag DOT_PATH can be used to specify the path where the dot tool can be
+# found. If left blank, it is assumed the dot tool can be found in the path.
+
+DOT_PATH =
+
+# The DOTFILE_DIRS tag can be used to specify one or more directories that
+# contain dot files that are included in the documentation (see the
+# \dotfile command).
+
+DOTFILE_DIRS =
+
+# The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
+# nodes that will be shown in the graph. If the number of nodes in a graph
+# becomes larger than this value, doxygen will truncate the graph, which is
+# visualized by representing a node as a red box. Note that doxygen if the number
+# of direct children of the root node in a graph is already larger than
+# MAX_DOT_GRAPH_NOTES then the graph will not be shown at all. Also note
+# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
+
+DOT_GRAPH_MAX_NODES = 50
+
+# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
+# graphs generated by dot. A depth value of 3 means that only nodes reachable
+# from the root by following a path via at most 3 edges will be shown. Nodes
+# that lay further from the root node will be omitted. Note that setting this
+# option to 1 or 2 may greatly reduce the computation time needed for large
+# code bases. Also note that the size of a graph can be further restricted by
+# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
+
+MAX_DOT_GRAPH_DEPTH = 1000
+
+# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
+# background. This is disabled by default, which results in a white background.
+# Warning: Depending on the platform used, enabling this option may lead to
+# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
+# read).
+
+DOT_TRANSPARENT = NO
+
+# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
+# files in one run (i.e. multiple -o and -T options on the command line). This
+# makes dot run faster, but since only newer versions of dot (>1.8.10)
+# support this, this feature is disabled by default.
+
+DOT_MULTI_TARGETS = YES
+
+# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
+# generate a legend page explaining the meaning of the various boxes and
+# arrows in the dot generated graphs.
+
+GENERATE_LEGEND = YES
+
+# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
+# remove the intermediate dot files that are used to generate
+# the various graphs.
+
+DOT_CLEANUP = YES
+
+#---------------------------------------------------------------------------
+# Configuration::additions related to the search engine
+#---------------------------------------------------------------------------
+
+# The SEARCHENGINE tag specifies whether or not a search engine should be
+# used. If set to NO the values of all tags below this one will be ignored.
+
+SEARCHENGINE = NO
diff --git a/doc/default/aei_full.png b/doc/default/aei_full.png
new file mode 100644
index 0000000000000000000000000000000000000000..f85c720ad26249315d6cfe0997c64ebd44d9ba32
GIT binary patch
literal 7675
zcmeAS@N?(olHy`uVBq!ia0y~yVB}<AU~uDLV_;yoFPNCgz`($g?&#~tz_78O`%fY(
z0|NtRfk$L90|U1(2s1Lwnj^u$z`$PO>FdgVgN2jb*i?2|mK_6wY?r5tV@O5Z+qviS
zlilkc*neH|(MS5jW93|hfR&{NwP#XOGaF)xvbHwP5#wm9jb{&gpSbblG3$v<Z%SmU
z>pdJN%{-j2F=&(Qn?e=k8@HMAzQ$jew3Tzi@oD_Iwu;?`o)<f9&3>#ZTA{TmqGpLl
z*OV*szB9JuU8}D7`s(A=?fdTMht}?2G&d+9Ai!Ws>xKl8tchJrp^UvhcZ-@hxCl%=
zm)Uxpi;HXBu?nZ8iQ$&dR~ywZmo)H{h|Mbt4iQvc@Flfk!GZ-3PW7m&7*#A~iT|sA
z(EhuZ>-+uNTkiX&R|kJIdj0SDH*UVa=MR6_FP^$3O4I${$I3|_*Fri~bl4+KSmZ4+
zIsEB|Ug^RW+$*+S`ezoe9_qPNdBx(J4h0wNlGSa}W!h|;6W`8f?_9F%0f$BI@-?l;
z<JA^zNN8}4^L1!Fx}R@Ld_hOj)E@N|8_rfYxsO89-~Rm7c>KkRmBm5(sm3V_)#Uj-
z>PpGXM^~L#QNCcJ2cPiG>de)XxSE!=?W&(U+rg3b^L8n@*)4O@H{7c`_^_0d!&~(7
zw5W;)sgH{k8Ou5T@XJOQME`r%X+O(VGWy@f7?aryf;G3iEP46k+1F0F%wflRLG|0M
z^fxg}Y<eEFbG_62p)&E=)7&K{$FEL!=Bxd5O2^|3HBwFK2G_qG^?qjlJ#(py>xaV~
zj=D;5X|;10(?u#v&vh5JusF>Bzp%y7EbsLFJ)I9UFN752U+I_D->5j_J$I#Ol%_iq
zUqjckUvZn>8+9&u#@03=>{Q@8hlv|y#eAJ=rdKW5DL?Iew|8sHImtEYR}Gze75?lN
z>fR$K7R#Av(lzl`OPcd^3y$tuA<tYf<&#@765X;G^IMO%P4u|-DD_&cvFZ`~wDYnn
z)9ybpX83F!qAL3Rf8h5=x8kRU+$ldWBa7>sVVbMnLt}04vYkzqQ$4N)ylH#-`ALwX
zp}$kFf{0zXkjV2IL9y6Y*0XY9vroKc_&BL>TkF%lRZAv$@HN`Letx4@_55$E>#?sk
zE)n$Jvfl5Qcg`-O|EhD@7M|UkT_GpO?WvNz@yX7%?=Hu7nFjOSwGB}ft<L97xINeZ
zm@w=4$Ge;B`YJkmU8Lgur)(7UmP&NzDl9$XofB8~E;WL&Y{i4h<wvq2H?1}JE_2%P
ze_-UM)emh&R?Auhxd|&zykd0Y=r0+e$FD704n7x(InA-SC-?VU)8BXck~+%{X-&Lx
zYEta~*bT?GHFh;^7e1L78Rx4l*)A<ARQZInSDTZ2MrYVXk4&pvr{^nQ&EnPeC_0%C
zeQ<BssjA;Sb2;8IoATB_IhR>~j!{*PVL>yWTEz{!<mX!Fw!3Uvwzm0`Q7^m0L4Bnk
zZ<L-sbUh{3q|5r<s)^U&{E=-t7d`M*-Lah^Tky|?xCQSmkCvZ3)B2s~)wkXAe?0#g
zqAI#@rRxX3-#v3zTQ%L*x44pajd9|}h2ApTf?G@vht(bw)8Du-@vD;Q`8vjHCME}d
z*yshxxm<gH(JM0l=1j%^J9lI=#w@XMxlz94$h5!b0=1uN$RtE*E`OMRrS9Ou)yhV8
z>%VrFw4_-piydlu?a**ZAazZRh}>t*!cW2yR}5-IYNQWp*WLU-ZU5hR(fHN(ef$3j
zJN%h(?da~1qdR{#E>Csbe7!N3SGqIh_|4gV-5GN(_DnyVUz+K3Uh}$_Wv?p7W7hYV
z>JBDGZd#nUS?6Y%-}Y}e3m8qhG?KOBl0q}Iq|6%B1o@Abgqg**GbudUa^E`D%0-7U
zqss5zVwX=L2lw8a*^qRbGs@t;u6LQlqIK$%X0@Fa%87NgXv=UE=Cyisz?MBWslUf6
z?DD3N12a^6r=%$_mDKP5Ze4Ny>C)#>tuE}riS1MW3(1{6%qgg@^XbBxH#@$6bNICI
z=Y9LqGtZ~;Gv0c6a`APA-$fIzuTN^bF}=$FaNAWiIVQJmgINay<{T-{W>m^GZIjUp
z+Lm;3SDWv|z?~kswsMvC-tH-7U3H{v%EchnNg9tId%7i=@1O6Hb!tt#gn_(_;NtMz
zQN|11uDm}XZ6?HZc2$!vi*@g2M@B*Y&3#-szdIfqw$69tiQC@ak!++TTOp^var1(k
z*~^7v{#zf~I!jtoTfVlq^V<aXW2f9Jquk>n<=Bg!9zLG*w3fBYHIBF6ziB~sQBK6|
z%Nc^nJtZH7X3JU|S#K@WP`zAfa;5mMz^u28`xUnY^{rWDwXK0c`NEpB`}~h=+`T;W
zg<jqz%iNR4IfQMG@Gp#z&8XKfS?BSawcW*rVOGYrwHt15od3P9ICqxIu~Y7oL(F`t
zIar-LC(mz5{k&vq(W@<;eF@CIe~omR4p_}F6ML|B&qPC)l$?x%VzY8zE4;pL<2C(y
zWvJB$m8NU0S2f(uGQ_w|xfs+CuqJtKecus_rq%ldE;p$O@~;v8QXiuFz1C4ClP_dt
zy|3$(r#|L!6Tdx|VPO9#G&{rW;+tcq=lCtzxaWz_rTpb-m;C0aE0{dWKDz%`cjEE(
zK!1O^Qu{g8?CTmDWO=1Cwh89+UVdqs<MyFMrgyQ<O|cKp#nWY`s;-uL^-)NAUwqO%
z{gt8|tG#^I+y2-R)R*LW`B(A3UH%FO(&l+ytvi^w=Zff*+ZLbsc7HgPDP61-XQpj>
za7NL!^PkRS=@i%gJD?JEJ!a<WorY(8BwRHZw){0;{N=nsMU6<VU!BynvrW??&wdx#
z75ApF;PUe9ye=LG$4AQ!9;mv)>U+J@Ygw|%#hlxM-=jK=UMF8Tw#G}vbfRQvbVhcX
zZ&zuQ){iARH@97GagXA8|E5gr$;!4~8~Zacfop!f?YXn1@Z4XuNn0yU+N}N%q1ScQ
zW!6`5hwroANghAF#{CqB>qKQ8kv%W>yMIo}b4rqWXyC<A)9)Ah;ro91Y0W?Lj{N`I
z|Mkn0iT}Uno4jycrSr+{$K1k>>5<#be(t?-=6!i?a;VX~s^yX)s#7awmTte1^}xE!
zCG5i*W`Cu#jA<${S3ksQKRvN(%WkLdVsAAbC*~(D<NB^2{PXVVRd3EXP1z`VyVc?0
z&I_|Ivj=?GHk&DD=GB?i4r`ftd1o{IlR0z3{?+b}v9Gx9u{~}tEZu(o#zs5Y&5wdN
z>pr+(8M9Ww=v<)hU0dt7X%Qy3AFtt-_{t-6QtBF`w$ZE3C1z{lephbSx!K=q|FW||
zHoJ*ofzsv;o(GK$HY*&S$1P#Zsr{w#?Yd=2>nhhQl=I$lA|hP%a#*9f&za}4XWoCZ
z@lQA_RTz0ea<7MJTYPQhx$t`R-ORr|j)@9z&-v3Sr?|pIAaR-Z;p9r5H%wcj@BBWM
zH^C(+ST*b2(G9a4=j+zpE|5KTck$ml8(#ej+3{RpCT~G-eEPkRr7yp%Yv$X1|AS<#
z+Yh-PHyWR9nOYPzHAE!j)2lD%x%<z~$`%(|yrnfUWlfFAx$kT(E{=`|r%GnG%oBZF
z@<ky2L67P}E-tRLQ(HMZg>D`()_kn9OiM#!hQ4t5otHn`?fJZGOeS31z0gK@@di~c
zu66TgW(ytuBPc6YCpqmWN1OMWLuWKJc38H3Jw5XhW1YkDS5~`^aj<@0pFE>M)1;%R
zX?F6nSuUNE=a)2XVs%j5S2#a*xxBlBh=|A?9b<7Ju6?>21x|6Y{PK%<c0yQSq5Yx-
z3m&A+*tt{iptj)oe>!h|{7YA7I8-bW`Nj6%L;pXUnwpwsr#^E!WSCX{Y(tT{LWrNj
z%-PGdR;Hv`7Wp2oN>LKZjXB<B{^D3k#B%WkOC>Y;qBWOyE-8!sKCzwmcUX5q?!E7V
z_m}o1#UD7gAwpz(ugj)o4{dqBmfez1$(W~7WbnPcw%;dj@}-J{?P+;=KYX%`QfBZb
z&YIfzK-1ipZFkg#EsCe_1s3@4-qCmOU&{}@uaSAXR-Vf9X;)sjQn0Xx(>gwI#*Q8@
z9)7lB-zx@(vj5305Vt(__jk|&-<;ET{u&pnn164-u%<0_@r>0I7$ml7zD_;V$5MLR
z@~qU~4)(Icm(6D7ihmb8YB%fcX|tqW=g^>+2ZVWFbAPzzdMfNUYx`UAwBRdDYd9@R
z59a1~ojA6Y=eu4^>GY&~<+sz{1U#xcdE2b+Hn=Gl8DW>7v$uAqeU#>My`*0|&YZnd
z;Icx(fANR#Kt5yZJZY~2{g^cm%b1RNzj2qkVAFb!Z*P#<P5z1QX-#L>xP3Uh$3mp+
z_(SLFd%cOiJ&eYOXQeZLx8*DQd|S;-XvTR9t)fOnkvo?S%6%X0-Y2lC_E_9$H(NI0
z%^#JXI>s$8+s(Q=dYZd{{^oTH^&TW#;lJyV`6|QU)7G_%*_PcaSX~i1Ywg>`+a~%u
z-I#a7WtQ9p7MaDbw(pj2f42F<ZLvr3<~GkB-_PG;W8>ekd*1)st;hF1w=t@3_gAVm
zbXnK5+IZq#8zsf?wdwDil5RMy2#h+iWM5BZV*Lr{EvBkD>sX}KlN9uug4ZW^`sMJk
z8OW+llhLf0<{`}PaBy>l%L6g-niQF<7y9!jcw9Sm=}2-&)2^@SHm@rJ*T4O!ob#@`
zPki^qd}p1Dbvi8XBh2GFa&H%>KGIA$ZMOTo&ukm%x@h;S^G`hdsk3LB>8C#iABAR1
zzS;Hqm|D2|_PF=|j-L{q<Z;dF150XB-4UU?nlmkCJuL3?{lhhVe{zPNpmqqKs7>&P
zGyVM!pT}x?e-rjEDDAIwI<f8SlfuTmeZ1fKn{!K_R)(lf-IQWK?OFMU*R9zCLUxN;
znjdfD;4oMfrJXugA-w6T9NQ-)lS}(He2V?Ep;*eSBWKG>!HcujF6MsD&RMv4>Hq07
zBKwqcWoJ)(wolBYl~e9AOMZ*~%orhE;R)AS9Y5YK;1O6E_c!*f$Cpp>H@1D<diWRb
znKR7>v!+$EO}~2ItNr=r54X%5_8duDva^2Trv=rq2l-~jUjHfmGNsZ<<WEz_+;1~a
zF6|OOrC)Q-DR}Xb+QiEmT0dOhd)XRYPBa%=z%?gp&jOqI#SZ#U9pcw?czm4MV4I$$
zI!S8QU5;1l_D<}a#>R90@5FYan|Ee$Z+Lbu_y3QrT%Cb2Vl!W*svl};7XDE9yO{5m
zW@tR~iNq)Ux9binc1f8%wk)Y-ws^RB;lsEBbJnze)4vNgPApvY^?Ew%<A#$9R{nP4
zugaC~E_^NT)|ar>ODn@{YQlZ}?T6NNzUo~vPx402{Fx_`bRR#cK9%rmuhhKY3dhaj
zJ2%uluz#-nJY*ZwJIw%YQ{e`ooUK8A(we^Cd*+rg-L1B}Y9_T?`}&7@qTd)+Oxmgc
zf4APGsmkY{@ODm*y#8Tv_muX-=k|*_J=(1!<8+6^#?0~~uWViV+2UtUXKML5Yz^{z
zy!*=ONwulYXTQ!(H)VO-`lbJUP`ZoO;X;Y+|2$tvTwd%n;WG1qzBgL~{>r;=aQz@6
z9R0;0F6}Poln*wt9D1rf7rwFfBuBWvIn2@DHQR9W`ThD%SDOlZ%uiMXO?#teWPj<Z
zhKt+W9(5)=zW$#vt0(*@6=DlNy6;Yh<nu`k*{eL}EnYeGL1IeiZ^oWiw`(I?7v&|J
z#C2|bEkA!@(-qd6Z=e00(Qv||@4Lty<;R|no;u2&6quY56LT+eP5g4@71<Z{8KgAN
za@_08nUKJG{&?sAmzQhJ)KU*#D2rV^L85hAJuBPypq8xXp`Gt%T|E4g#jQ6dwlQH&
zzv%~`S(-DK{Ogod45<B_79*v3wtGsu;2zP$OJb`O(od-RTs6z?dc&}_qO;fIvx3RT
z1D|Kkl+jr(W%hW^R#oRti*0q&LSJj2d>W*vn2^wvbnBdqm0sxv!JGw)rca10eeq4Q
zdg8|1-O4|83KDM}5A==JTz-vjo#u`6v$N(-@q8sOu6{<zcE*MiYSML9y#>X_oNK3C
z4m-80fm!sK`Psu<t3CYhyZO()aYb*+e)mVd+1uj_b|i@T%zb9t9JuBDuOP7}`_iX#
zaX!#q@I>6__DtvJOBQT?V8^{o-0t(T+20jD@JH+x*mFn3Pf1%XJl|Pqa_Mi0+@g?{
z<I4p-Zuw2#`TD4Lj#h>6n>p1Faz3XOXic|>Di)j-YAu_-tVDf{{lw|dH*YwU<9^eG
zZQUNNl^HAA`Sxx+d4unj?NRSvZzNvKn6+!c^nfZUDNWz!{(>K_KP(JY`siN2dg530
z3OV85^Gq+kY1=1V{YU8B&s~OlV@@39?7rY`c-bq>AvCD-eb99^X>$#;$4~D)lK<_z
zONN6tVZBTFtTnd{AMM_2Ba&+Q;SulBiI;MguTiY%FncX{%50@?<fhw=&zblH_Nt!h
zd~;fHqoCe9!8FZE;j?8rnF576Ic8d{zqwb{f7z`3Z)52)-Ur)t<326>{N}sK73+d0
zZdVImpFf>0xMi)r{V~^5(+>DlPE*|-_Cw}DYQXkGSqk#UHkdK2mbK9Gp8Vd~*|w=Z
zyT3GW!j#;+K9?em2RH85Oe_EEVl?6Z;koZOyuVgBZ?i~`rj+;O^-Fbb_AdzCq#e?}
zwKQVy#IM|%KaPlRIq+2R>+{ajzj!~a`}algz;CBJKNX(7z8AS&{`;m~^2QU_@cvF*
z?-UyJa<<;=pw#l~k)R<RwV6K4kG$IOT6Izs%URFA?1{FAPqkl_x4T|gaJ|bYYI2Q!
z|0<J8{W~Se74;vDUZ>bNZrHlu=H{>Gbi~_Uuc`dkvFZ)iIn&vO|4zM?J+@X*=z_2a
zL;Sq^W_uScSRfzoapNnmvFbz_w}AN}7UySmnpM1XUBxx!T%ml2;ab-6ILR-&e?8G>
z{2H<5kHmwG6~CPg4n5lHx}QtXeDCY$S4ACF9)xe#Ob&NEsB)xy<>DL1bEgTv*?P>w
z%{E_6Na)cVx6Fy=7SE@L`!4*hdO&HtcEI}=ljq-M{Ts375Bm#FZUd&rOkUgqh3CZA
z?OE{P*v8EgW_E{lR&w6hIitDEh<CcRUhSL)hEq-Pt?la1=IAT^P&1o9MLVzf)An4y
zf7fdD7SDc?!OzNS?y6+S*x+^Ny6U%2X{>5X|5~z7?EL@XT5i`a(|P`fg!%gZD_1@(
z58C(j^s=;x;ii8cY;-s-k^4yA^5@U|4WHg0$PmtT37zx3Y^SJ*NDTkunbKhnKl+Xp
z``P`Odrva_@tpNXl*<1(Ot#(jt4Ua(PvY*6qQIDwM>I7wX3Tl`?3mK}U-EMsRxDTV
zuUq0@_wD`H7^bUy7A_0VyI(B#XJuvmtRC;d;^!Ifz`*g?WzNfvb&l>$^<1a9xw!JC
z#V9U($o}sC!iE!{{bOdj-s^Du%d0Kl(q7fkqB!eVso^`XlQwU(cF&48<4(U`T6p<;
z)#b1Lhi%^d)O!D53(qeVu}WuWH3Ozcq9L#2m)HLf|90cGvA95knXz<aMBVI;={I`L
zw5`4qnwxs^pX;gS4Ki>3nCIMHde%DBQ?)sF_nqHvX}OP5uely;YsfPH*XWuNw)Me<
z_?OEcOm_KnZco_P*kd}c{8h50>QoYZ4^M39UthF0P-T)S>-+;bmw7ZQwBsJV-4i<F
zb5cQB^2F=>M^3$Ge!|glbA52cldIPsOg*0Tl>e}^-TPOQ_x}>|D&E=d4RVl)fBW75
z&<LcZAb(qKlb1@n*M}o(&lIozdh6wzR+pOTzc&2-&^i5v%Vybo&Y`pBF8>_i%2D=9
zVAbJy&uw0=o1{}{ACqRQ`*>UWo%=`C-{1OZ^jahA`PbhqPi9Ilnm5m8)pGTI8^({v
zWUQad=H2L#aNToe*M&8GRg7CWKbC2Q{O3D1dx6%<n6GwHnr9<frc1U7U0Ke_R2(h2
z-8OIbAC)JuyZ<&F_9(W$v&USY?JVz)RjW;PK3RSEYU9JxZnVs;T=A-bo`Z||f?4j8
z(TQ(d<g=B-1m0u{zsh+urMgVnU-gnq%l*>DY%?U7^JMqSzJ1L-tGO?sx#O|M<B*vF
zUyht!<G=gn3a#JHOP^+nZRBiAD$AMmq3~<~YuQ_;0x3<q?4@bPm1gCNM1L&GzdU6%
zb3;dR{gm@-@0U$z?MeP_`~RoUsWrDJdrY3TvG&-!^tgMQ_j_wMJ<r=b@4M{w$k$t@
z7FoTy#o)C;J~bz?{KC1(Hoi;_HzfP?(`>sh9#>jF-SMx_6Ry>Er`#OQypJo|kaonj
zC`sMQs);u?>3r{=Z>-YNyXS5f%6zA7@o8@CN1@poS=_U17e>B4FnQIIM{!mryCrkD
zea~`DT6Lnc+(6STO(nr<#oE>4zwYkYv)gM%?iZ)vgGctf$TRd)X`lG)@;6EAj4ZE$
z^;#<@2;b73sMhnZDGfAEGjB)s(`)&QqThD)d_BYZ>T1r9kD_Xcd~YL}zbWO`gm7u;
zh0Iwz@sdk$p<~a%cV%a9gdI92dUj{o^p0TG?`tfL!hf|MQCk1c|KNAa=hKTt`53zQ
z{F6$t7c04=<$c_~=u`3k&!BSa)`2_kH63QM>}8H_sa49&xjl`url{exxuF{Oti9hN
z%~gIam-@%CMmI}2*gR;~t|M|AZV9G^FW_biZd%*DMS9*p4{kr@jGfi5R_AbhoWxlz
zcDsV3!ch6|E}4HFd6NZmIoAg>Xy`Xhw%vczBeQJ&(&f4tH?9b>zpF@Lx{!Bh!mqQR
zo}O>G<(gHV;Fc5V{^7`(UAAkdC_lAqj@Deh?(psVM`x_FoVZ_EdO`V(t+MYnSGzy=
zv}n4&a?`J5i+S&N6)G!S`Q4OXH+iZ(TSoDxV0E2CSEo6sI5n2p_RPuanttPev1`c@
z#;#u~d|L6gVS>A7#5TAoUv$*-Js7s)YRs}Y^+~h3+ZiULH?i<-kgaEt?KHoX=@?uw
zPc@P0M4b?Hob2%4k5aFk9QUNWH=dCz=@xHNu>NppYW<zwjmf%aR@h!YbE3RN>`P0_
zP5Xt`D{j6ye&X=EiyaF;?|TrfuE5}wd+6hTi=X+qJCvWj5T7~C<Ff<jyf39G8C*xL
zCbRmO^7QHKJXxpa$oVS8)--13f#u5UcN#D+f9iVba7Aab$!yshK5qW;VI@Z%?r8dI
zWThHbYbs}4TDw%R{Lr_W<s7D+KR2F`=GtVGvamtIZT95(|5iThOJKA1OZVAx#_Hab
zWs7xIW=x)%`Fc}e9fPp*<?YVl&h9T%qPR-7woG(VTrzQ1K;cD^iz{S8J(tei6h2iZ
zWy5N>^^y_-YbI~Ie0<d-<I*Dk8}r_a*oyv}v)<)LLi1ng;Eg9%S517Cec|W(ruVjD
z+VA_773$U(e_H-NtEFM4KBN5f6KP!E=XUZ<eENKWfZ6FwCW7l)ljfc%$*6w2Y|(UK
zqqrpFpqgvnm&%Bwom!){JlxeZ$46UX!S%ZH^Dp)DYQ;<qVR@4&ytYz!*S{G%t)HkR
zPWsl;UNh&hWRE1v-K_#?Wrx{V-zh)8^=@v-`xiExZ)+|-d$OG2z4t!$J2SlkbUtZy
z?@4Su{5|=FjhJ@*jK|q0md=}Jll8xT3xnbLm)B2kc=cqZ&|k@Ak5tV}b2JQR2u8bJ
z6T6mUb^G4mA5PL|8G7;+nwF=YtlM*@YR{2nVlulgZk}4yWyqVwHSf3(uUd0RXi(wh
zMU5*Tzj<}lrRYXy+v*!1jb7hqSfRHg@4Nq}JE==wtv<~y!`)ysaf7g@Z$_Bto|~d8
z%nogz`|0+kTt<ba<r>>gPx|ZTwYi1!bsuNnYSA~hCw$uZwf(&D`#Cm3Cueal$!<Qd
z?%<o-lfTzaFI>&+Kj*;4_t!TXZH{X9`cTF)-*wjSSVe)D+gDdA-8=Gxd+zR&m-j!q
z^oz$%OuPQUx2zYgtF~>9+c)Es&dV^VFXvg~w>|hR{^4!@#!r(!TuChX-f>6hk*Zls
z+E=ByHHv2}RLb&fc*I_>IF*-how5C~!5i*t65sz+222eR*)#RJ+4W@?lHbpBji{5J
zvCLMnQ&NE~EbUizl+aCim&zMkPfv=~wcxv6bf)=E>diTyk2c2qyij_h+jW&;!r6(8
z(f-Xs&rMEEdf^oO)8WHa3pH0;+sZHHMQ`oXQ%=?Lo!`kjMfLX~wJP3zQIQyPP=$Lp
zvAQ+Qci!Wm6|Re&tQ`Zl2`-F_UQ#1CLqn?M<((U0^@mTfvoqCQwtpyOWK<g6+Ps*B
z-@2)H)toxlc*lb}8<>(dAE`09ZNp~Dxu&zw?{L3MX{0;f;m6NGgSbDXyyW+)J}`f@
zM5aAJR7Yb+Ufv_wGonKGs@O_zzB_Yz17mLV{^z|1{FFO;!ipB3JK5CKbnyu{XFG3Y
zJlo%W4`%ZR?UP$-c;)hB_w~A;X8nEfN1W+_clM-+-h~1@tgQN+i(6TCY!xb>vthya
z_V4S9)4I4jSU6rkDLLN5S=jB{+0@ijqbDxJ%F4R`+8^$F$?jK|F1^acz`(%Z>FVdQ
I&MBb@0A8rAKmY&$
literal 0
HcmV?d00001
diff --git a/doc/default/footer.html b/doc/default/footer.html
new file mode 100644
index 0000000..570bf95
--- /dev/null
+++ b/doc/default/footer.html
@@ -0,0 +1,10 @@
+<hr size="1">
+<table col="3" width="100%">
+ <tr>
+ <td width="300"><a href="http://www.aei.mpg.de"><img src="aei_full.png" alt="Albert-Einstein-Institute" align="left" border="0"></a></td>
+ <td width="*"><p align="center">Generated on $datetime</p></td>
+ <td width="300"><a href="http://www.doxygen.org/index.html"><img src="doxygen.png" alt="doxygen" align="right" border="0"></a></td>
+ <tr>
+</table>
+</body>
+</html>
diff --git a/doc/default/header.html b/doc/default/header.html
new file mode 100644
index 0000000..7c427c0
--- /dev/null
+++ b/doc/default/header.html
@@ -0,0 +1,6 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
+<title>$title</title>
+<link href="$relpath$doxygen.css" rel="stylesheet" type="text/css">
+<link href="$relpath$tabs.css" rel="stylesheet" type="text/css">
+</head><body>
diff --git a/doc/default/stylesheet.css b/doc/default/stylesheet.css
new file mode 100644
index 0000000..c7db1a8
--- /dev/null
+++ b/doc/default/stylesheet.css
@@ -0,0 +1,358 @@
+BODY,H1,H2,H3,H4,H5,H6,P,CENTER,TD,TH,UL,DL,DIV {
+ font-family: Geneva, Arial, Helvetica, sans-serif;
+}
+BODY,TD {
+ font-size: 90%;
+}
+H1 {
+ text-align: center;
+ font-size: 160%;
+}
+H2 {
+ font-size: 120%;
+}
+H3 {
+ font-size: 100%;
+}
+CAPTION { font-weight: bold }
+DIV.qindex {
+ width: 100%;
+ background-color: #e8eef2;
+ border: 1px solid #84b0c7;
+ text-align: center;
+ margin: 2px;
+ padding: 2px;
+ line-height: 140%;
+}
+DIV.nav {
+ width: 100%;
+ background-color: #e8eef2;
+ border: 1px solid #84b0c7;
+ text-align: center;
+ margin: 2px;
+ padding: 2px;
+ line-height: 140%;
+}
+DIV.navtab {
+ background-color: #e8eef2;
+ border: 1px solid #84b0c7;
+ text-align: center;
+ margin: 2px;
+ margin-right: 15px;
+ padding: 2px;
+}
+TD.navtab {
+ font-size: 70%;
+}
+A.qindex {
+ text-decoration: none;
+ font-weight: bold;
+ color: #1A419D;
+}
+A.qindex:visited {
+ text-decoration: none;
+ font-weight: bold;
+ color: #1A419D
+}
+A.qindex:hover {
+ text-decoration: none;
+ background-color: #ddddff;
+}
+A.qindexHL {
+ text-decoration: none;
+ font-weight: bold;
+ background-color: #6666cc;
+ color: #ffffff;
+ border: 1px double #9295C2;
+}
+A.qindexHL:hover {
+ text-decoration: none;
+ background-color: #6666cc;
+ color: #ffffff;
+}
+A.qindexHL:visited { text-decoration: none; background-color: #6666cc; color: #ffffff }
+A.el { text-decoration: none; font-weight: bold }
+A.elRef { font-weight: bold }
+A.code:link { text-decoration: none; font-weight: normal; color: #0000FF}
+A.code:visited { text-decoration: none; font-weight: normal; color: #0000FF}
+A.codeRef:link { font-weight: normal; color: #0000FF}
+A.codeRef:visited { font-weight: normal; color: #0000FF}
+A:hover { text-decoration: none; background-color: #f2f2ff }
+DL.el { margin-left: -1cm }
+.fragment {
+ font-family: monospace, fixed;
+ font-size: 95%;
+}
+PRE.fragment {
+ border: 1px solid #CCCCCC;
+ background-color: #f5f5f5;
+ margin-top: 4px;
+ margin-bottom: 4px;
+ margin-left: 2px;
+ margin-right: 8px;
+ padding-left: 6px;
+ padding-right: 6px;
+ padding-top: 4px;
+ padding-bottom: 4px;
+}
+DIV.ah { background-color: black; font-weight: bold; color: #ffffff; margin-bottom: 3px; margin-top: 3px }
+
+DIV.groupHeader {
+ margin-left: 16px;
+ margin-top: 12px;
+ margin-bottom: 6px;
+ font-weight: bold;
+}
+DIV.groupText { margin-left: 16px; font-style: italic; font-size: 90% }
+BODY {
+ background: white;
+ color: black;
+ margin-right: 20px;
+ margin-left: 20px;
+}
+TD.indexkey {
+ background-color: #e8eef2;
+ font-weight: bold;
+ padding-right : 10px;
+ padding-top : 2px;
+ padding-left : 10px;
+ padding-bottom : 2px;
+ margin-left : 0px;
+ margin-right : 0px;
+ margin-top : 2px;
+ margin-bottom : 2px;
+ border: 1px solid #CCCCCC;
+}
+TD.indexvalue {
+ background-color: #e8eef2;
+ font-style: italic;
+ padding-right : 10px;
+ padding-top : 2px;
+ padding-left : 10px;
+ padding-bottom : 2px;
+ margin-left : 0px;
+ margin-right : 0px;
+ margin-top : 2px;
+ margin-bottom : 2px;
+ border: 1px solid #CCCCCC;
+}
+TR.memlist {
+ background-color: #f0f0f0;
+}
+P.formulaDsp { text-align: center; }
+IMG.formulaDsp { }
+IMG.formulaInl { vertical-align: middle; }
+SPAN.keyword { color: #008000 }
+SPAN.keywordtype { color: #604020 }
+SPAN.keywordflow { color: #e08000 }
+SPAN.comment { color: #800000 }
+SPAN.preprocessor { color: #806020 }
+SPAN.stringliteral { color: #002080 }
+SPAN.charliteral { color: #008080 }
+.mdescLeft {
+ padding: 0px 8px 4px 8px;
+ font-size: 80%;
+ font-style: italic;
+ background-color: #FAFAFA;
+ border-top: 1px none #E0E0E0;
+ border-right: 1px none #E0E0E0;
+ border-bottom: 1px none #E0E0E0;
+ border-left: 1px none #E0E0E0;
+ margin: 0px;
+}
+.mdescRight {
+ padding: 0px 8px 4px 8px;
+ font-size: 80%;
+ font-style: italic;
+ background-color: #FAFAFA;
+ border-top: 1px none #E0E0E0;
+ border-right: 1px none #E0E0E0;
+ border-bottom: 1px none #E0E0E0;
+ border-left: 1px none #E0E0E0;
+ margin: 0px;
+}
+.memItemLeft {
+ padding: 1px 0px 0px 8px;
+ margin: 4px;
+ border-top-width: 1px;
+ border-right-width: 1px;
+ border-bottom-width: 1px;
+ border-left-width: 1px;
+ border-top-color: #E0E0E0;
+ border-right-color: #E0E0E0;
+ border-bottom-color: #E0E0E0;
+ border-left-color: #E0E0E0;
+ border-top-style: solid;
+ border-right-style: none;
+ border-bottom-style: none;
+ border-left-style: none;
+ background-color: #FAFAFA;
+ font-size: 80%;
+}
+.memItemRight {
+ padding: 1px 8px 0px 8px;
+ margin: 4px;
+ border-top-width: 1px;
+ border-right-width: 1px;
+ border-bottom-width: 1px;
+ border-left-width: 1px;
+ border-top-color: #E0E0E0;
+ border-right-color: #E0E0E0;
+ border-bottom-color: #E0E0E0;
+ border-left-color: #E0E0E0;
+ border-top-style: solid;
+ border-right-style: none;
+ border-bottom-style: none;
+ border-left-style: none;
+ background-color: #FAFAFA;
+ font-size: 80%;
+}
+.memTemplItemLeft {
+ padding: 1px 0px 0px 8px;
+ margin: 4px;
+ border-top-width: 1px;
+ border-right-width: 1px;
+ border-bottom-width: 1px;
+ border-left-width: 1px;
+ border-top-color: #E0E0E0;
+ border-right-color: #E0E0E0;
+ border-bottom-color: #E0E0E0;
+ border-left-color: #E0E0E0;
+ border-top-style: none;
+ border-right-style: none;
+ border-bottom-style: none;
+ border-left-style: none;
+ background-color: #FAFAFA;
+ font-size: 80%;
+}
+.memTemplItemRight {
+ padding: 1px 8px 0px 8px;
+ margin: 4px;
+ border-top-width: 1px;
+ border-right-width: 1px;
+ border-bottom-width: 1px;
+ border-left-width: 1px;
+ border-top-color: #E0E0E0;
+ border-right-color: #E0E0E0;
+ border-bottom-color: #E0E0E0;
+ border-left-color: #E0E0E0;
+ border-top-style: none;
+ border-right-style: none;
+ border-bottom-style: none;
+ border-left-style: none;
+ background-color: #FAFAFA;
+ font-size: 80%;
+}
+.memTemplParams {
+ padding: 1px 0px 0px 8px;
+ margin: 4px;
+ border-top-width: 1px;
+ border-right-width: 1px;
+ border-bottom-width: 1px;
+ border-left-width: 1px;
+ border-top-color: #E0E0E0;
+ border-right-color: #E0E0E0;
+ border-bottom-color: #E0E0E0;
+ border-left-color: #E0E0E0;
+ border-top-style: solid;
+ border-right-style: none;
+ border-bottom-style: none;
+ border-left-style: none;
+ color: #606060;
+ background-color: #FAFAFA;
+ font-size: 80%;
+}
+.search { color: #003399;
+ font-weight: bold;
+}
+FORM.search {
+ margin-bottom: 0px;
+ margin-top: 0px;
+}
+INPUT.search { font-size: 75%;
+ color: #000080;
+ font-weight: normal;
+ background-color: #e8eef2;
+}
+TD.tiny { font-size: 75%;
+}
+a {
+ color: #1A41A8;
+}
+a:visited {
+ color: #2A3798;
+}
+.dirtab { padding: 4px;
+ border-collapse: collapse;
+ border: 1px solid #84b0c7;
+}
+TH.dirtab { background: #e8eef2;
+ font-weight: bold;
+}
+HR { height: 1px;
+ border: none;
+ border-top: 1px solid black;
+}
+
+/* Style for detailed member documentation */
+.memtemplate {
+ font-size: 80%;
+ color: #606060;
+ font-weight: normal;
+}
+.memnav {
+ background-color: #e8eef2;
+ border: 1px solid #84b0c7;
+ text-align: center;
+ margin: 2px;
+ margin-right: 15px;
+ padding: 2px;
+}
+.memitem {
+ padding: 4px;
+ background-color: #eef3f5;
+ border-width: 1px;
+ border-style: solid;
+ border-color: #dedeee;
+ -moz-border-radius: 8px 8px 8px 8px;
+}
+.memname {
+ white-space: nowrap;
+ font-weight: bold;
+}
+.memdoc{
+ padding-left: 10px;
+}
+.memproto {
+ background-color: #d5e1e8;
+ width: 100%;
+ border-width: 1px;
+ border-style: solid;
+ border-color: #84b0c7;
+ font-weight: bold;
+ -moz-border-radius: 8px 8px 8px 8px;
+}
+.paramkey {
+ text-align: right;
+}
+.paramtype {
+ white-space: nowrap;
+}
+.paramname {
+ color: #602020;
+ font-style: italic;
+ white-space: nowrap;
+}
+/* End Styling for detailed member documentation */
+
+/* for the tree view */
+.ftvtree {
+ font-family: sans-serif;
+ margin:0.5em;
+}
+.directory { font-size: 9pt; font-weight: bold; }
+.directory h3 { margin: 0px; margin-top: 1em; font-size: 11pt; }
+.directory > h3 { margin-top: 0; }
+.directory p { margin: 0px; white-space: nowrap; }
+.directory div { display: none; margin: 0px; }
+.directory img { vertical-align: -30%; }
--
GitLab