Colony

# Doxyfile 1.5.9

# 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

# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 

# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 

# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 

# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 

# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 

# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.

# comments will behave just like regular Qt-style comments 

# (thus requiring an explicit @brief command for a brief description.)

# 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

# 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.

# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 

# sources only. Doxygen will then generate output that is more tailored for 

# Fortran.

OPTIMIZE_FOR_FORTRAN   = NO

# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 

# sources. Doxygen will then generate output that is tailored for 

# VHDL.

OPTIMIZE_OUTPUT_VHDL   = NO

# Doxygen selects the parser to use depending on the extension of the files it parses. 

# With this tag you can assign which parser to use for a given extension. 

# Doxygen has a built-in mapping, but you can override or extend it using this tag. 

# The format is ext=language, where ext is a file extension, and language is one of 

# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, 

# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat 

# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), 

# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.

EXTENSION_MAPPING      = 

# 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 

# If you use Microsoft's C++/CLI language, you should set this option to YES to 

# enable parsing support.

CPP_CLI_SUPPORT        = NO

# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 

# Doxygen will parse them like normal C++ but will assume all classes use public 

# instead of private inheritance when no explicit protection keyword is present.

SIP_SUPPORT            = NO

# For Microsoft's IDL there are propget and propput attributes to indicate getter 

# and setter methods for a property. Setting this option to YES (the default) 

# will make doxygen to replace the get and set methods by a property in the 

# documentation. This will only work if the methods are indeed getting or 

# setting a simple type. If this is not the case, or you want to show the 

# methods anyway, you should set this option to NO.

IDL_PROPERTY_SUPPORT   = YES

# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 

# is documented as struct, union, or enum with the name of the typedef. So 

# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 

# with name TypeT. When disabled the typedef will appear as a member of a file, 

# namespace, or class. And the struct will be named TypeS. This can typically 

# be useful for C code in case the coding convention dictates that all compound 

# types are typedef'ed and only the typedef is referenced, never the tag name.

TYPEDEF_HIDES_STRUCT   = NO

# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 

# determine which symbols to keep in memory and which to flush to disk. 

# When the cache is full, less often used symbols will be written to disk. 

# For small to medium size projects (<1000 input files) the default value is 

# probably good enough. For larger projects a too small cache size can cause 

# doxygen to be busy swapping symbols to and from disk most of the time 

# causing a significant performance penality. 

# If the system has enough physical memory increasing the cache will improve the 

# performance by keeping more symbols in memory. Note that the value works on 

# a logarithmic scale so increasing the size by one will rougly double the 

# memory usage. The cache size is given by this formula: 

# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 

# corresponding to a cache size of 2^16 = 65536 symbols

SYMBOL_CACHE_SIZE      = 0

# 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 SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 

# hierarchy of group names into alphabetical order. If set to NO (the default) 

# the group names will appear in their defined order.

SORT_GROUP_NAMES       = NO

# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 

# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 

# This will remove the Files entry from the Quick Index and from the 

# Folder Tree View (if specified). The default is YES.

SHOW_FILES             = YES

# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 

# Namespaces page. 

# This will remove the Namespaces entry from the Quick Index 

# and from the Folder Tree View (if specified). The default is YES.

SHOW_NAMESPACES        = YES

# 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 

# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by 

# doxygen. The layout file controls the global structure of the generated output files 

# in an output format independent way. The create the layout file that represents 

# doxygen's defaults, run doxygen with the -l option. You can optionally specify a 

# file name after the option, if omitted DoxygenLayout.xml will be used as the name 

# of the layout file.

LAYOUT_FILE            = 

# 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

# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90

# 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        = 

# to standard output. 

# If FILTER_PATTERNS is specified, this tag will be 

# 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: 

# If the REFERENCED_BY_RELATION tag is set to YES 

# If the REFERENCES_RELATION tag is set to 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 documentation.

# 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_DOCSET tag is set to YES, additional index files 

# will be generated that can be used as input for Apple's Xcode 3 

# integrated development environment, introduced with OSX 10.5 (Leopard). 

# To create a documentation set, doxygen will generate a Makefile in the 

# HTML output directory. Running make will produce the docset in that 

# directory and running "make install" will install the docset in 

# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 

# it at startup. 

# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.

GENERATE_DOCSET        = NO

# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 

# feed. A documentation feed provides an umbrella under which multiple 

# documentation sets from a single provider (such as a company or product suite) 

# can be grouped.

DOCSET_FEEDNAME        = "Doxygen generated docs"

# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 

# should uniquely identify the documentation set bundle. This should be a 

# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 

# will append .docset to the name.

DOCSET_BUNDLE_ID       = org.doxygen.Project

# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 

# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 

# is used to encode HtmlHelp index (hhk), content (hhc) and project file 

# content.

CHM_INDEX_ENCODING     = 

# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER 

# are set, an additional index file will be generated that can be used as input for 

# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated 

# HTML documentation.

GENERATE_QHP           = NO

# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 

# be used to specify the file name of the resulting .qch file. 

# The path specified is relative to the HTML output folder.

QCH_FILE               = 

# The QHP_NAMESPACE tag specifies the namespace to use when generating 

# Qt Help Project output. For more information please see 

# http://doc.trolltech.com/qthelpproject.html#namespace

QHP_NAMESPACE          = 

# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 

# Qt Help Project output. For more information please see 

# http://doc.trolltech.com/qthelpproject.html#virtual-folders

QHP_VIRTUAL_FOLDER     = doc

# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. 

# For more information please see 

# http://doc.trolltech.com/qthelpproject.html#custom-filters

QHP_CUST_FILTER_NAME   = 

# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see 

# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.

QHP_CUST_FILTER_ATTRS  = 

# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's 

# filter section matches. 

# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.

QHP_SECT_FILTER_ATTRS  = 

# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 

# be used to specify the location of Qt's qhelpgenerator. 

# If non-empty doxygen will try to run qhelpgenerator on the generated 

# .qhp file.

QHG_LOCATION           = 

# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 

# structure should be generated to display hierarchical information. 

# If the tag value is set to FRAME, a side panel will be generated 

# containing a tree-like index structure (just like the one that 

# probably better off using the HTML help feature. Other possible values 

# for this tag are: HIERARCHIES, which will generate the Groups, Directories, 

# and Class Hierarchy pages using a tree view instead of an ordered list; 

# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which 

# disables this behavior completely. For backwards compatibility with previous 

# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE 

# respectively.

# Use this tag to change the font size of Latex formulas included 

# as images in the HTML documentation. The default is 10. Note that 

# when you change the font size after a successful doxygen run you need 

# to manually remove any form_*.png images from the HTML output directory 

# to force them to be regenerated.

FORMULA_FONTSIZE       = 10

# If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.

LATEX_SOURCE_CODE      = NO

# 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 

#  

# TAGFILES = file1 file2 ... 

#  

# TAGFILES = file1=loc1 "file2 = loc2" ... 

# 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) 

# 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            = 

# By default doxygen will write a font called FreeSans.ttf to the output 

# directory and reference it in all dot files that doxygen generates. This 

# font does not include all possible unicode characters however, so when you need 

# these (or just want a differently looking font) you can specify the font name 

# using DOT_FONTNAME. You need need to make sure dot is able to find the font, 

# which can be done by putting it in a standard location or by setting the 

# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory 

# containing the font.

DOT_FONTNAME           = FreeSans

# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 

# The default size is 10pt.

DOT_FONTSIZE           = 10

# By default doxygen will tell dot to use the output directory to look for the 

# FreeSans.ttf font (which doxygen will put there itself). If you specify a 

# different font using DOT_FONTNAME you can set the path where dot 

# can find it using this tag.

DOT_FONTPATH           = 

# If the CALL_GRAPH and HAVE_DOT options 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.

# If the CALLER_GRAPH 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.

# in a graphical way. The dependency relations are determined by the #include 

# generated by dot. Possible values are png, jpg, or gif 

# The 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 

# DOT_GRAPH_MAX_NODES 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

# 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.

# background. This is disabled by default, because dot on Windows does not 

# seem to support this out of the box. 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).

# Options related to the search engine