Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

The GtkRadiant sources as originally released under the GPL license.

  • Loading branch information...
commit 0991a5ce8b8ccb86a5b0d54c089369d84f53dc10 0 parents
Travis Bradshaw authored January 31, 2012

Showing 190 changed files with 39,538 additions and 0 deletions. Show diff stats Hide diff stats

  1. 7,837  CHANGES
  2. 78  COMPILING
  3. 82  CONTRIBUTORS
  4. 47  DoxyConfig
  5. 1,117  Doxyfile
  6. 159  Doxygen_files/Doxyfile
  7. 45  Doxygen_files/doxy_mainpage.h
  8. 34  Doxygen_files/doxygen_gtkradiant.css
  9. 49  Doxygen_files/doxygen_gtkradiant_foot.html
  10. 38  Doxygen_files/doxygen_gtkradiant_head.html
  11. 7  Doxygen_files/doxygen_index.html
  12. 46  Doxygen_files/doxygen_reference_foot.html
  13. 38  Doxygen_files/doxygen_reference_head.html
  14. 103  Doxygen_files/example/annotated.html
  15. 110  Doxygen_files/example/classIEpair-members.html
  16. 414  Doxygen_files/example/classIEpair.html
  17. 103  Doxygen_files/example/classes.html
  18. BIN  Doxygen_files/example/doxygen.gif
  19. 35  Doxygen_files/example/doxygen_gtkradiant.css
  20. 102  Doxygen_files/example/files.html
  21. 110  Doxygen_files/example/functions.html
  22. 16  Doxygen_files/example/graph_legend.dot
  23. BIN  Doxygen_files/example/graph_legend.gif
  24. 141  Doxygen_files/example/graph_legend.html
  25. 102  Doxygen_files/example/index.html
  26. 104  Doxygen_files/example/pages.html
  27. 140  Doxygen_files/example/test_8c-source.html
  28. 107  Doxygen_files/example/test_8c.html
  29. 105  Doxygen_files/example/todo.html
  30. 159  Doxygen_files/genDoxyfile
  31. 421  Doxygen_files/gendoxfunctions
  32. BIN  Doxygen_files/images/body-left-tile.gif
  33. BIN  Doxygen_files/images/body-lower-left.gif
  34. BIN  Doxygen_files/images/body-lower-right.gif
  35. BIN  Doxygen_files/images/body-lower-tile.gif
  36. BIN  Doxygen_files/images/body-right-tile.gif
  37. BIN  Doxygen_files/images/body-upper-left.gif
  38. BIN  Doxygen_files/images/body-upper-right.gif
  39. BIN  Doxygen_files/images/body-upper-tile.gif
  40. BIN  Doxygen_files/images/gtkr_splash.jpg
  41. BIN  Doxygen_files/images/gtkr_splash_sm.jpg
  42. BIN  Doxygen_files/images/history_id_logo.gif
  43. BIN  Doxygen_files/images/top-right.gif
  44. BIN  Doxygen_files/images/top-tile.gif
  45. BIN  Doxygen_files/images/top-title.gif
  46. 333  Doxygen_files/reference1.html
  47. 340  GPL
  48. 690  GtkRadiant.prj
  49. 271  GtkRadiant.sln
  50. 458  LGPL
  51. 36  LICENSE
  52. 51  README.doxygen
  53. 31  README.txt
  54. 922  SConscript
  55. 332  SConstruct
  56. 165  TODO
  57. 0  bobtoolz/bt/bt-el2.txt b/contrib/bobtoolz/bt/bt-el2.txt
  58. BIN  contrib/bkgrnd2d/bitmaps/bkgrnd2d_conf.bmp
  59. BIN  contrib/bkgrnd2d/bitmaps/bkgrnd2d_xy_toggle.bmp
  60. BIN  contrib/bkgrnd2d/bitmaps/bkgrnd2d_xz_toggle.bmp
  61. BIN  contrib/bkgrnd2d/bitmaps/bkgrnd2d_yz_toggle.bmp
  62. 318  contrib/bkgrnd2d/bkgrnd2d.cpp
  63. 8  contrib/bkgrnd2d/bkgrnd2d.def
  64. 133  contrib/bkgrnd2d/bkgrnd2d.dsp
  65. 82  contrib/bkgrnd2d/bkgrnd2d.h
  66. 171  contrib/bkgrnd2d/bkgrnd2d.vcproj
  67. 364  contrib/bkgrnd2d/dialog.cpp
  68. 35  contrib/bkgrnd2d/dialog.h
  69. 319  contrib/bkgrnd2d/plugin.cpp
  70. 79  contrib/bkgrnd2d/plugin.h
  71. 131  contrib/bkgrnd2d/readme_bkgrnd2d-b0.25.txt
  72. 63  contrib/bobtoolz/CPortals.h
  73. 366  contrib/bobtoolz/DBobView.cpp
  74. 72  contrib/bobtoolz/DBobView.h
  75. 867  contrib/bobtoolz/DBrush.cpp
  76. 99  contrib/bobtoolz/DBrush.h
  77. 50  contrib/bobtoolz/DEPair.cpp
  78. 45  contrib/bobtoolz/DEPair.h
  79. 667  contrib/bobtoolz/DEntity.cpp
  80. 109  contrib/bobtoolz/DEntity.h
  81. 93  contrib/bobtoolz/DListener.cpp
  82. 62  contrib/bobtoolz/DListener.h
  83. 182  contrib/bobtoolz/DMap.cpp
  84. 54  contrib/bobtoolz/DMap.h
  85. 458  contrib/bobtoolz/DPatch.cpp
  86. 75  contrib/bobtoolz/DPatch.h
  87. 264  contrib/bobtoolz/DPlane.cpp
  88. 67  contrib/bobtoolz/DPlane.h
  89. 52  contrib/bobtoolz/DPoint.cpp
  90. 45  contrib/bobtoolz/DPoint.h
  91. 469  contrib/bobtoolz/DShape.cpp
  92. 60  contrib/bobtoolz/DShape.h
  93. 366  contrib/bobtoolz/DTrainDrawer.cpp
  94. 80  contrib/bobtoolz/DTrainDrawer.h
  95. 307  contrib/bobtoolz/DTreePlanter.cpp
  96. 219  contrib/bobtoolz/DTreePlanter.h
  97. 185  contrib/bobtoolz/DVisDrawer.cpp
  98. 56  contrib/bobtoolz/DVisDrawer.h
  99. 486  contrib/bobtoolz/DWinding.cpp
  100. 68  contrib/bobtoolz/DWinding.h
  101. 286  contrib/bobtoolz/ScriptParser.cpp
  102. 61  contrib/bobtoolz/ScriptParser.h
  103. 25  contrib/bobtoolz/StdAfx.cpp
  104. 141  contrib/bobtoolz/StdAfx.h
  105. 298  contrib/bobtoolz/bobToolz-GTK.cpp
  106. 8  contrib/bobtoolz/bobToolz.def
  107. 41  contrib/bobtoolz/bobToolz.dsw
  108. 64  contrib/bobtoolz/bobToolz.h
  109. 533  contrib/bobtoolz/bobToolz.rc
  110. 344  contrib/bobtoolz/bobToolz_gtk.dsp
  111. 328  contrib/bobtoolz/bobToolz_gtk.vcproj
  112. 109  contrib/bobtoolz/bobtoolz-gtk.rc
  113. 258  contrib/bobtoolz/bsploader.cpp
  114. 134  contrib/bobtoolz/bsploader.h
  115. 17  contrib/bobtoolz/bt/bt-el1.txt
  116. 61  contrib/bobtoolz/bt/ctf-blue.txt
  117. 61  contrib/bobtoolz/bt/ctf-red.txt
  118. 5  contrib/bobtoolz/bt/door-tex-trim.txt
  119. 10  contrib/bobtoolz/bt/door-tex.txt
  120. 14  contrib/bobtoolz/bt/tp_ent.txt
  121. 340  contrib/bobtoolz/cportals.cpp
  122. 97  contrib/bobtoolz/ctfToolz-GTK.cpp
  123. 34  contrib/bobtoolz/ctfresource_gtk.h
  124. 109  contrib/bobtoolz/ctfresource_gtk.rc
  125. 12  contrib/bobtoolz/ctftoolz.def
  126. 62  contrib/bobtoolz/dialogs/AboutDialog.cpp
  127. 64  contrib/bobtoolz/dialogs/AboutDialog.h
  128. 63  contrib/bobtoolz/dialogs/AutoCaulkDialog.cpp
  129. 66  contrib/bobtoolz/dialogs/AutoCaulkDialog.h
  130. 66  contrib/bobtoolz/dialogs/AutoCaulkStartDialog.cpp
  131. 71  contrib/bobtoolz/dialogs/AutoCaulkStartDialog.h
  132. 65  contrib/bobtoolz/dialogs/BrushCheckDialog.h
  133. 92  contrib/bobtoolz/dialogs/DoorDialog.cpp
  134. 74  contrib/bobtoolz/dialogs/DoorDialog.h
  135. 65  contrib/bobtoolz/dialogs/IntersectDialog.cpp
  136. 70  contrib/bobtoolz/dialogs/IntersectDialog.h
  137. 61  contrib/bobtoolz/dialogs/IntersectInfoDialog.cpp
  138. 65  contrib/bobtoolz/dialogs/IntersectInfoDialog.h
  139. 116  contrib/bobtoolz/dialogs/PolygonDialog.cpp
  140. 74  contrib/bobtoolz/dialogs/PolygonDialog.h
  141. 105  contrib/bobtoolz/dialogs/StairDialog.cpp
  142. 74  contrib/bobtoolz/dialogs/StairDialog.h
  143. 81  contrib/bobtoolz/dialogs/TextureResetDialog.cpp
  144. 73  contrib/bobtoolz/dialogs/TextureResetDialog.h
  145. 61  contrib/bobtoolz/dialogs/brushcheckdialog.cpp
  146. 1,909  contrib/bobtoolz/dialogs/dialogs-gtk.cpp
  147. 98  contrib/bobtoolz/dialogs/dialogs-gtk.h
  148. 85  contrib/bobtoolz/dialogs/pathplotterdialog.cpp
  149. 70  contrib/bobtoolz/dialogs/pathplotterdialog.h
  150. 790  contrib/bobtoolz/funchandlers-GTK.cpp
  151. 214  contrib/bobtoolz/funchandlers-ctf-GTK.cpp
  152. 503  contrib/bobtoolz/funchandlers.cpp
  153. 72  contrib/bobtoolz/funchandlers.h
  154. 88  contrib/bobtoolz/lists.cpp
  155. 21  contrib/bobtoolz/lists.h
  156. 430  contrib/bobtoolz/misc.cpp
  157. 46  contrib/bobtoolz/misc.h
  158. 13  contrib/bobtoolz/res/plugin.rc2
  159. 15  contrib/bobtoolz/resource-gtk.h
  160. 115  contrib/bobtoolz/resource.h
  161. 653  contrib/bobtoolz/shapes.cpp
  162. 49  contrib/bobtoolz/shapes.h
  163. 96  contrib/bobtoolz/txt/changelog.txt
  164. 77  contrib/bobtoolz/txt/readme.txt
  165. 247  contrib/bobtoolz/visfind.cpp
  166. 1  contrib/bobtoolz/visfind.h
  167. BIN  contrib/camera/bitmaps/camera_insp.bmp
  168. 290  contrib/camera/camera.cpp
  169. 8  contrib/camera/camera.def
  170. 174  contrib/camera/camera.dsp
  171. 165  contrib/camera/camera.h
  172. 190  contrib/camera/camera.vcproj
  173. 1,356  contrib/camera/dialogs.cpp
  174. 37  contrib/camera/dialogs.h
  175. 51  contrib/camera/dialogs_common.cpp
  176. 269  contrib/camera/funchandlers.cpp
  177. 37  contrib/camera/funchandlers.h
  178. 234  contrib/camera/listener.cpp
  179. 64  contrib/camera/listener.h
  180. 243  contrib/camera/misc.cpp
  181. 76  contrib/camera/misc.h
  182. 183  contrib/camera/renderer.cpp
  183. 46  contrib/camera/renderer.h
  184. 4  contrib/gtkgensurf/.cvsignore
  185. 73  contrib/gtkgensurf/CHANGES
  186. 434  contrib/gtkgensurf/bitmap.cpp
  187. 1,328  contrib/gtkgensurf/dec.cpp
  188. 452  contrib/gtkgensurf/face.cpp
  189. 270  contrib/gtkgensurf/font.cpp
7,837  CHANGES
7837 additions, 0 deletions not shown
78  COMPILING
... ...
@@ -0,0 +1,78 @@
  1
+developer documentation for GtkRadiant 1.5.0
  2
+============================================
  3
+
  4
+getting the source
  5
+==================
  6
+
  7
+The latest source is available from the Subversion repository.
  8
+  https://zerowing.idsoftware.com/svn/radiant/GtkRadiant/trunk/
  9
+
  10
+The subversion client can be obtained from the Subversion site.
  11
+  http://subversion.tigris.org
  12
+
  13
+To get a copy of the source using the commandline Subversion client:
  14
+  Change the current directory to the desired location for the source.
  15
+  svn checkout https://zerowing.idsoftware.com/svn/radiant/GtkRadiant/trunk/ ./GtkRadiant
  16
+  svn checkout https://zerowing.idsoftware.com/svn/radiant.gamepacks/Q3Pack/trunk/ ./GtkRadiant/games/Q3Pack
  17
+
  18
+
  19
+
  20
+Linux/OSX(using X-windows)
  21
+==========================
  22
+
  23
+environment:
  24
+- gcc3 (preferably)
  25
+- scons = 0.96 (radiant is built with scons rather than make)
  26
+- python >= 2.3.0 (scons requires python, some build steps use python)
  27
+- svn >= 1.1 (some build steps use svn)
  28
+
  29
+dependencies:
  30
+- gtk+ >= 2.4.0 (requires glib, atk, pango, iconv, etc)
  31
+- gtkglext >= 1.0.0 (requires opengl)
  32
+- libxml2 >= 2.0.0
  33
+- zlib >= 1.2.0 (for archivezip module)
  34
+- libpng >= 1.2.0 (for imagepng module)
  35
+- libmhash = 0.9.0 (for q3map2)
  36
+
  37
+build:
  38
+Execute 'scons SETUP=0' in the directory containing SConscript
  39
+
  40
+install:
  41
+run './GtkRadiant/install.py'
  42
+note - this script should be run after each time you update from svn
  43
+
  44
+run:
  45
+Execute './GtkRadiant/install/radiant.x86' (or './GtkRadiant/install/radiant.ppc' on osx)
  46
+
  47
+
  48
+
  49
+Win32 (2000 or XP)
  50
+==================
  51
+
  52
+environment:
  53
+- visual studio .net 2003
  54
+- microsoft c++ compiler 7.1 (comes with vs.net 2003)
  55
+- python 2.3.0 or later (some build steps use python)
  56
+- subversion 1.1 or later (some build steps use svn)
  57
+
  58
+dependencies are prepackaged archives, extract them to the directory above GtkRadiant.sln:
  59
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/gtk2-2.4.14.zip (gtk-wimp, gtkglext, gtk, glib, atk, pango, iconv etc)
  60
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/libxml2-2.6.2.zip
  61
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/STLport-4.6.2.zip
  62
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/zlib1-1.2.1.zip (for archivezip module)
  63
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/libpng-1.2.5.zip (for imagepng module)
  64
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/mhash-0.9.1.zip (for q3map2)
  65
+- http://zerowing.idsoftware.com/files/radiant/developer/1.5/msvc_redist.zip (msvc runtime libraries)
  66
+
  67
+build:
  68
+Open GtkRadiant.sln.
  69
+In tools > options > projects > VC++ Directories > executables, add the paths to python.exe (e.g. c:\python23\) and svn.exe (e.g. c:\svn\) 
  70
+Hit 'Build > Build Solution' (F7)
  71
+
  72
+install:
  73
+run './GtkRadiant/install.py'
  74
+note - this script should be run after each time you update from svn
  75
+
  76
+run:
  77
+set Project > Properties > Debugging > Command to "$(SolutionDir)install/$(TargetFileName)"
  78
+hit 'Debug > Start' (F5)
82  CONTRIBUTORS
... ...
@@ -0,0 +1,82 @@
  1
+GtkRadiant CONTRIBUTORS and CREDITS
  2
+last update: 09/12/2004
  3
+=======================
  4
+
  5
+Loki
  6
+----
  7
+Leonardo Zide leo@lokigames.com
  8
+Mike Phillips (Loki QA)
  9
+Bernd Kreimeier (overall coordination)
  10
+
  11
+QER.com
  12
+-------
  13
+TTimo timo@idsoftware.com
  14
+^Fishman (Pablo Zurita) fish@gamedesign.net
  15
+RR2DO2 rr2do2@q3f.com
  16
+SmallPileofGibs spog@planetquake.com
  17
+
  18
+Curry plugin
  19
+------------
  20
+Mike "mickey" Jackman
  21
+Tim "Maj" Rennie
  22
+
  23
+PrtView plugin, various bug fixes and q3map guru
  24
+------------------------------------------------
  25
+Geoffrey DeWan
  26
+
  27
+Gensurf plugin
  28
+--------------
  29
+David Hyde
  30
+
  31
+PicoModel
  32
+---------
  33
+seaw0lf with assist by ydnar
  34
+
  35
+Q3Map2
  36
+------
  37
+Randy 'ydnar' Reddig
  38
+
  39
+Updated shader files, textures, entities.def, keyboard shortcut list
  40
+overall testing and feedback
  41
+----------------------------
  42
+Jean-Francois "Eutectic" Groleau
  43
+
  44
+Improvements and bug fixing
  45
+---------------------------
  46
+Jan Paul "MrElusive" van Waveren
  47
+Robert Duffy
  48
+Forest "LordHavoc" Wroncy-Hale
  49
+Nurail
  50
+AcidDeath
  51
+Chronos
  52
+Michael Schlueter
  53
+Jamie Wilkinson
  54
+Robert "Tr3B" Beckebans
  55
+
  56
+Web
  57
+---
  58
+Dave "Bargle" Koenig
  59
+Jason "Wolfen" Spencer
  60
+Shawn "EvilTypeGuy" Walker
  61
+
  62
+Thanks to John Hutton, AstroCreep and W2k for web help
  63
+
  64
+FAQ
  65
+---
  66
+Equim and Wex
  67
+
  68
+
  69
+Testing/Feedback
  70
+---
  71
+Black_Dog, d0nkey, Fjoggis, Jago, jetscreamer, gibbie, Godmil, Gom Jabbar,
  72
+Mindlink, mslaf, necros, Promit, Ravo, RPG, scampie, sock, sponge, thiste,
  73
+voodoochopsticks, Zwiffle
  74
+
  75
+
  76
+Misc
  77
+----
  78
+Thanks to everyone on the beta mailing list and
  79
+irc.telefragged.com #qeradiant for testing and feedback.
  80
+Updated icons by AstroCreep!
  81
+Bitch-slapping by RaYGunn!
  82
+Last minute bugs by SPoG! (SPoG--)
47  DoxyConfig
... ...
@@ -0,0 +1,47 @@
  1
+# Included Doxygen Config file
  2
+#---------------------------------------------------------------------------
  3
+# Project name & version number
  4
+#---------------------------------------------------------------------------
  5
+PROJECT_NAME           = 
  6
+PROJECT_NUMBER         = 
  7
+
  8
+#---------------------------------------------------------------------------
  9
+# Where to put the output
  10
+# Note: The images dir should be next to the created html dir within the
  11
+#	output dir.
  12
+#       eg;
  13
+#       [Current Dir]
  14
+#               L__[OUTPUT_DIRECTORY]
  15
+#                      L__[html]
  16
+#                      L__[images]
  17
+#---------------------------------------------------------------------------
  18
+OUTPUT_DIRECTORY       = ../GtkRadiant-doxygen
  19
+
  20
+#---------------------------------------------------------------------------
  21
+# Where to read the sources
  22
+# you can add more than one source...
  23
+# INPUT                   = radiant/ \
  24
+#                           tools/quake3/q3map \
  25
+#                           tools/quake3/q3data
  26
+#
  27
+# Recursive is set on, so setting it to ./ (current dir) would read source
  28
+# files recursively from the current dir down. (which would take a while)
  29
+#
  30
+# eg: To document just include, if the current directory is ../GtkRadiant/ 
  31
+# then...
  32
+#---------------------------------------------------------------------------
  33
+INPUT                  = radiant/
  34
+
  35
+#---------------------------------------------------------------------------
  36
+# Misc settings
  37
+# TAB_SIZE     - sets the indenting for the inline source and the source 
  38
+#                browser
  39
+# INCLUDE_PATH - will include documentation for included files from other
  40
+#                packages. You can specify more than one path the same as
  41
+#                shown in the INPUT example Leave it blank if you don't want 
  42
+#                this.
  43
+# PERL_PATH    - path to the perl executable
  44
+#
  45
+#---------------------------------------------------------------------------
  46
+PERL_PATH              = /usr/bin/perl
  47
+
1,117  Doxyfile
... ...
@@ -0,0 +1,1117 @@
  1
+# Doxyfile 1.3.6
  2
+
  3
+# This file describes the settings to be used by the documentation system
  4
+# doxygen (www.doxygen.org) for a project
  5
+#
  6
+# All text after a hash (#) is considered a comment and will be ignored
  7
+# The format is:
  8
+#       TAG = value [value, ...]
  9
+# For lists items can also be appended using:
  10
+#       TAG += value [value, ...]
  11
+# Values that contain spaces should be placed between quotes (" ")
  12
+
  13
+#---------------------------------------------------------------------------
  14
+# Project related configuration options
  15
+#---------------------------------------------------------------------------
  16
+
  17
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
  18
+# by quotes) that should identify the project.
  19
+
  20
+PROJECT_NAME           = GtkRadiant
  21
+
  22
+# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
  23
+# This could be handy for archiving the generated documentation or 
  24
+# if some version control system is used.
  25
+
  26
+PROJECT_NUMBER         = 1.5.0
  27
+
  28
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
  29
+# base path where the generated documentation will be put. 
  30
+# If a relative path is entered, it will be relative to the location 
  31
+# where doxygen was started. If left blank the current directory will be used.
  32
+
  33
+OUTPUT_DIRECTORY       = doxygen-out
  34
+
  35
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
  36
+# documentation generated by doxygen is written. Doxygen will use this 
  37
+# information to generate all constant output in the proper language. 
  38
+# The default language is English, other supported languages are: 
  39
+# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, 
  40
+# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en 
  41
+# (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese, 
  42
+# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
  43
+
  44
+OUTPUT_LANGUAGE        = English
  45
+
  46
+# This tag can be used to specify the encoding used in the generated output. 
  47
+# The encoding is not always determined by the language that is chosen, 
  48
+# but also whether or not the output is meant for Windows or non-Windows users. 
  49
+# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES 
  50
+# forces the Windows encoding (this is the default for the Windows binary), 
  51
+# whereas setting the tag to NO uses a Unix-style encoding (the default for 
  52
+# all platforms other than Windows).
  53
+
  54
+USE_WINDOWS_ENCODING   = YES
  55
+
  56
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
  57
+# include brief member descriptions after the members that are listed in 
  58
+# the file and class documentation (similar to JavaDoc). 
  59
+# Set to NO to disable this.
  60
+
  61
+BRIEF_MEMBER_DESC      = YES
  62
+
  63
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
  64
+# the brief description of a member or function before the detailed description. 
  65
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
  66
+# brief descriptions will be completely suppressed.
  67
+
  68
+REPEAT_BRIEF           = YES
  69
+
  70
+# This tag implements a quasi-intelligent brief description abbreviator 
  71
+# that is used to form the text in various listings. Each string 
  72
+# in this list, if found as the leading text of the brief description, will be 
  73
+# stripped from the text and the result after processing the whole list, is used 
  74
+# as the annotated text. Otherwise, the brief description is used as-is. If left 
  75
+# blank, the following values are used ("$name" is automatically replaced with the 
  76
+# name of the entity): "The $name class" "The $name widget" "The $name file" 
  77
+# "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
  78
+
  79
+ABBREVIATE_BRIEF       = 
  80
+
  81
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
  82
+# Doxygen will generate a detailed section even if there is only a brief 
  83
+# description.
  84
+
  85
+ALWAYS_DETAILED_SEC    = NO
  86
+
  87
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited 
  88
+# members of a class in the documentation of that class as if those members were 
  89
+# ordinary class members. Constructors, destructors and assignment operators of 
  90
+# the base classes will not be shown.
  91
+
  92
+INLINE_INHERITED_MEMB  = NO
  93
+
  94
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
  95
+# path before files name in the file list and in the header files. If set 
  96
+# to NO the shortest path that makes the file name unique will be used.
  97
+
  98
+FULL_PATH_NAMES        = NO
  99
+
  100
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
  101
+# can be used to strip a user-defined part of the path. Stripping is 
  102
+# only done if one of the specified strings matches the left-hand part of 
  103
+# the path. It is allowed to use relative paths in the argument list. 
  104
+# If left blank the directory from which doxygen is run is used as the 
  105
+# path to strip.
  106
+
  107
+STRIP_FROM_PATH        = 
  108
+
  109
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
  110
+# (but less readable) file names. This can be useful is your file systems 
  111
+# doesn't support long names like on DOS, Mac, or CD-ROM.
  112
+
  113
+SHORT_NAMES            = NO
  114
+
  115
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
  116
+# will interpret the first line (until the first dot) of a JavaDoc-style 
  117
+# comment as the brief description. If set to NO, the JavaDoc 
  118
+# comments will behave just like the Qt-style comments (thus requiring an 
  119
+# explicit @brief command for a brief description.
  120
+
  121
+JAVADOC_AUTOBRIEF      = NO
  122
+
  123
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
  124
+# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
  125
+# comments) as a brief description. This used to be the default behaviour. 
  126
+# The new default is to treat a multi-line C++ comment block as a detailed 
  127
+# description. Set this tag to YES if you prefer the old behaviour instead.
  128
+
  129
+MULTILINE_CPP_IS_BRIEF = NO
  130
+
  131
+# If the DETAILS_AT_TOP tag is set to YES then Doxygen 
  132
+# will output the detailed description near the top, like JavaDoc.
  133
+# If set to NO, the detailed description appears after the member 
  134
+# documentation.
  135
+
  136
+DETAILS_AT_TOP         = NO
  137
+
  138
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
  139
+# member inherits the documentation from any documented member that it 
  140
+# re-implements.
  141
+
  142
+INHERIT_DOCS           = YES
  143
+
  144
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
  145
+# tag is set to YES, then doxygen will reuse the documentation of the first 
  146
+# member in the group (if any) for the other members of the group. By default 
  147
+# all members of a group must be documented explicitly.
  148
+
  149
+DISTRIBUTE_GROUP_DOC   = NO
  150
+
  151
+# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
  152
+# Doxygen uses this value to replace tabs by spaces in code fragments.
  153
+
  154
+TAB_SIZE               = 2
  155
+
  156
+# This tag can be used to specify a number of aliases that acts 
  157
+# as commands in the documentation. An alias has the form "name=value". 
  158
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
  159
+# put the command \sideeffect (or @sideeffect) in the documentation, which 
  160
+# will result in a user-defined paragraph with heading "Side Effects:". 
  161
+# You can put \n's in the value part of an alias to insert newlines.
  162
+
  163
+ALIASES                = 
  164
+
  165
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 
  166
+# only. Doxygen will then generate output that is more tailored for C. 
  167
+# For instance, some of the names that are used will be different. The list 
  168
+# of all members will be omitted, etc.
  169
+
  170
+OPTIMIZE_OUTPUT_FOR_C  = NO
  171
+
  172
+# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources 
  173
+# only. Doxygen will then generate output that is more tailored for Java. 
  174
+# For instance, namespaces will be presented as packages, qualified scopes 
  175
+# will look different, etc.
  176
+
  177
+OPTIMIZE_OUTPUT_JAVA   = NO
  178
+
  179
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
  180
+# the same type (for instance a group of public functions) to be put as a 
  181
+# subgroup of that type (e.g. under the Public Functions section). Set it to 
  182
+# NO to prevent subgrouping. Alternatively, this can be done per class using 
  183
+# the \nosubgrouping command.
  184
+
  185
+SUBGROUPING            = YES
  186
+
  187
+#---------------------------------------------------------------------------
  188
+# Build related configuration options
  189
+#---------------------------------------------------------------------------
  190
+
  191
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
  192
+# documentation are documented, even if no documentation was available. 
  193
+# Private class members and static file members will be hidden unless 
  194
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
  195
+
  196
+EXTRACT_ALL            = NO
  197
+
  198
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
  199
+# will be included in the documentation.
  200
+
  201
+EXTRACT_PRIVATE        = NO
  202
+
  203
+# If the EXTRACT_STATIC tag is set to YES all static members of a file 
  204
+# will be included in the documentation.
  205
+
  206
+EXTRACT_STATIC         = YES
  207
+
  208
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
  209
+# defined locally in source files will be included in the documentation. 
  210
+# If set to NO only classes defined in header files are included.
  211
+
  212
+EXTRACT_LOCAL_CLASSES  = YES
  213
+
  214
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
  215
+# undocumented members of documented classes, files or namespaces. 
  216
+# If set to NO (the default) these members will be included in the 
  217
+# various overviews, but no documentation section is generated. 
  218
+# This option has no effect if EXTRACT_ALL is enabled.
  219
+
  220
+HIDE_UNDOC_MEMBERS     = NO
  221
+
  222
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
  223
+# undocumented classes that are normally visible in the class hierarchy. 
  224
+# If set to NO (the default) these classes will be included in the various 
  225
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
  226
+
  227
+HIDE_UNDOC_CLASSES     = NO
  228
+
  229
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
  230
+# friend (class|struct|union) declarations. 
  231
+# If set to NO (the default) these declarations will be included in the 
  232
+# documentation.
  233
+
  234
+HIDE_FRIEND_COMPOUNDS  = NO
  235
+
  236
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
  237
+# documentation blocks found inside the body of a function. 
  238
+# If set to NO (the default) these blocks will be appended to the 
  239
+# function's detailed documentation block.
  240
+
  241
+HIDE_IN_BODY_DOCS      = NO
  242
+
  243
+# The INTERNAL_DOCS tag determines if documentation 
  244
+# that is typed after a \internal command is included. If the tag is set 
  245
+# to NO (the default) then the documentation will be excluded. 
  246
+# Set it to YES to include the internal documentation.
  247
+
  248
+INTERNAL_DOCS          = NO
  249
+
  250
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
  251
+# file names in lower-case letters. If set to YES upper-case letters are also 
  252
+# allowed. This is useful if you have classes or files whose names only differ 
  253
+# in case and if your file system supports case sensitive file names. Windows 
  254
+# users are advised to set this option to NO.
  255
+
  256
+CASE_SENSE_NAMES       = YES
  257
+
  258
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
  259
+# will show members with their full class and namespace scopes in the 
  260
+# documentation. If set to YES the scope will be hidden.
  261
+
  262
+HIDE_SCOPE_NAMES       = NO
  263
+
  264
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
  265
+# will put a list of the files that are included by a file in the documentation 
  266
+# of that file.
  267
+
  268
+SHOW_INCLUDE_FILES     = YES
  269
+
  270
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
  271
+# is inserted in the documentation for inline members.
  272
+
  273
+INLINE_INFO            = YES
  274
+
  275
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
  276
+# will sort the (detailed) documentation of file and class members 
  277
+# alphabetically by member name. If set to NO the members will appear in 
  278
+# declaration order.
  279
+
  280
+SORT_MEMBER_DOCS       = YES
  281
+
  282
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
  283
+# brief documentation of file, namespace and class members alphabetically 
  284
+# by member name. If set to NO (the default) the members will appear in 
  285
+# declaration order.
  286
+
  287
+SORT_BRIEF_DOCS        = NO
  288
+
  289
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
  290
+# sorted by fully-qualified names, including namespaces. If set to 
  291
+# NO (the default), the class list will be sorted only by class name, 
  292
+# not including the namespace part. 
  293
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
  294
+# Note: This option applies only to the class list, not to the 
  295
+# alphabetical list.
  296
+
  297
+SORT_BY_SCOPE_NAME     = NO
  298
+
  299
+# The GENERATE_TODOLIST tag can be used to enable (YES) or 
  300
+# disable (NO) the todo list. This list is created by putting \todo 
  301
+# commands in the documentation.
  302
+
  303
+GENERATE_TODOLIST      = YES
  304
+
  305
+# The GENERATE_TESTLIST tag can be used to enable (YES) or 
  306
+# disable (NO) the test list. This list is created by putting \test 
  307
+# commands in the documentation.
  308
+
  309
+GENERATE_TESTLIST      = YES
  310
+
  311
+# The GENERATE_BUGLIST tag can be used to enable (YES) or 
  312
+# disable (NO) the bug list. This list is created by putting \bug 
  313
+# commands in the documentation.
  314
+
  315
+GENERATE_BUGLIST       = YES
  316
+
  317
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
  318
+# disable (NO) the deprecated list. This list is created by putting 
  319
+# \deprecated commands in the documentation.
  320
+
  321
+GENERATE_DEPRECATEDLIST= YES
  322
+
  323
+# The ENABLED_SECTIONS tag can be used to enable conditional 
  324
+# documentation sections, marked by \if sectionname ... \endif.
  325
+
  326
+ENABLED_SECTIONS       = 
  327
+
  328
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
  329
+# the initial value of a variable or define consists of for it to appear in 
  330
+# the documentation. If the initializer consists of more lines than specified 
  331
+# here it will be hidden. Use a value of 0 to hide initializers completely. 
  332
+# The appearance of the initializer of individual variables and defines in the 
  333
+# documentation can be controlled using \showinitializer or \hideinitializer 
  334
+# command in the documentation regardless of this setting.
  335
+
  336
+MAX_INITIALIZER_LINES  = 30
  337
+
  338
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
  339
+# at the bottom of the documentation of classes and structs. If set to YES the 
  340
+# list will mention the files that were used to generate the documentation.
  341
+
  342
+SHOW_USED_FILES        = YES
  343
+
  344
+#---------------------------------------------------------------------------
  345
+# configuration options related to warning and progress messages
  346
+#---------------------------------------------------------------------------
  347
+
  348
+# The QUIET tag can be used to turn on/off the messages that are generated 
  349
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
  350
+
  351
+QUIET                  = NO
  352
+
  353
+# The WARNINGS tag can be used to turn on/off the warning messages that are 
  354
+# generated by doxygen. Possible values are YES and NO. If left blank 
  355
+# NO is used.
  356
+
  357
+WARNINGS               = YES
  358
+
  359
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
  360
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
  361
+# automatically be disabled.
  362
+
  363
+WARN_IF_UNDOCUMENTED   = NO
  364
+
  365
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
  366
+# potential errors in the documentation, such as not documenting some 
  367
+# parameters in a documented function, or documenting parameters that 
  368
+# don't exist or using markup commands wrongly.
  369
+
  370
+WARN_IF_DOC_ERROR      = YES
  371
+
  372
+# The WARN_FORMAT tag determines the format of the warning messages that 
  373
+# doxygen can produce. The string should contain the $file, $line, and $text 
  374
+# tags, which will be replaced by the file and line number from which the 
  375
+# warning originated and the warning text.
  376
+
  377
+WARN_FORMAT            = "$file:$line: $text"
  378
+
  379
+# The WARN_LOGFILE tag can be used to specify a file to which warning 
  380
+# and error messages should be written. If left blank the output is written 
  381
+# to stderr.
  382
+
  383
+WARN_LOGFILE           = 
  384
+
  385
+#---------------------------------------------------------------------------
  386
+# configuration options related to the input files
  387
+#---------------------------------------------------------------------------
  388
+
  389
+# The INPUT tag can be used to specify the files and/or directories that contain 
  390
+# documented source files. You may enter file names like "myfile.cpp" or 
  391
+# directories like "/usr/src/myproject". Separate the files or directories 
  392
+# with spaces.
  393
+
  394
+INPUT                  = radiant/ plugins/ libs/ include/
  395
+
  396
+# If the value of the INPUT tag contains directories, you can use the 
  397
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
  398
+# and *.h) to filter out the source-files in the directories. If left 
  399
+# blank the following patterns are tested: 
  400
+# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp 
  401
+# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
  402
+
  403
+FILE_PATTERNS          = 
  404
+
  405
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
  406
+# should be searched for input files as well. Possible values are YES and NO. 
  407
+# If left blank NO is used.
  408
+
  409
+RECURSIVE              = YES
  410
+
  411
+# The EXCLUDE tag can be used to specify files and/or directories that should 
  412
+# excluded from the INPUT source files. This way you can easily exclude a 
  413
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
  414
+
  415
+EXCLUDE                = 
  416
+
  417
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories 
  418
+# that are symbolic links (a Unix filesystem feature) are excluded from the input.
  419
+
  420
+EXCLUDE_SYMLINKS       = NO
  421
+
  422
+# If the value of the INPUT tag contains directories, you can use the 
  423
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
  424
+# certain files from those directories.
  425
+
  426
+EXCLUDE_PATTERNS       = */.svn/*
  427
+
  428
+# The EXAMPLE_PATH tag can be used to specify one or more files or 
  429
+# directories that contain example code fragments that are included (see 
  430
+# the \include command).
  431
+
  432
+EXAMPLE_PATH           = radiant/ plugins/ libs/ include/
  433
+
  434
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
  435
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
  436
+# and *.h) to filter out the source-files in the directories. If left 
  437
+# blank all files are included.
  438
+
  439
+EXAMPLE_PATTERNS       = 
  440
+
  441
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
  442
+# searched for input files to be used with the \include or \dontinclude 
  443
+# commands irrespective of the value of the RECURSIVE tag. 
  444
+# Possible values are YES and NO. If left blank NO is used.
  445
+
  446
+EXAMPLE_RECURSIVE      = NO
  447
+
  448
+# The IMAGE_PATH tag can be used to specify one or more files or 
  449
+# directories that contain image that are included in the documentation (see 
  450
+# the \image command).
  451
+
  452
+IMAGE_PATH             = 
  453
+
  454
+# The INPUT_FILTER tag can be used to specify a program that doxygen should 
  455
+# invoke to filter for each input file. Doxygen will invoke the filter program 
  456
+# by executing (via popen()) the command <filter> <input-file>, where <filter> 
  457
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
  458
+# input file. Doxygen will then use the output that the filter program writes 
  459
+# to standard output.
  460
+
  461
+INPUT_FILTER           = 
  462
+
  463
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
  464
+# INPUT_FILTER) will be used to filter the input files when producing source 
  465
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
  466
+
  467
+FILTER_SOURCE_FILES    = NO
  468
+
  469
+#---------------------------------------------------------------------------
  470
+# configuration options related to source browsing
  471
+#---------------------------------------------------------------------------
  472
+
  473
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
  474
+# be generated. Documented entities will be cross-referenced with these sources. 
  475
+# Note: To get rid of all source code in the generated output, make sure also 
  476
+# VERBATIM_HEADERS is set to NO.
  477
+
  478
+SOURCE_BROWSER         = NO
  479
+
  480
+# Setting the INLINE_SOURCES tag to YES will include the body 
  481
+# of functions and classes directly in the documentation.
  482
+
  483
+INLINE_SOURCES         = NO
  484
+
  485
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
  486
+# doxygen to hide any special comment blocks from generated source code 
  487
+# fragments. Normal C and C++ comments will always remain visible.
  488
+
  489
+STRIP_CODE_COMMENTS    = YES
  490
+
  491
+# If the REFERENCED_BY_RELATION tag is set to YES (the default) 
  492
+# then for each documented function all documented 
  493
+# functions referencing it will be listed.
  494
+
  495
+REFERENCED_BY_RELATION = YES
  496
+
  497
+# If the REFERENCES_RELATION tag is set to YES (the default) 
  498
+# then for each documented function all documented entities 
  499
+# called/used by that function will be listed.
  500
+
  501
+REFERENCES_RELATION    = YES
  502
+
  503
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
  504
+# will generate a verbatim copy of the header file for each class for 
  505
+# which an include is specified. Set to NO to disable this.
  506
+
  507
+VERBATIM_HEADERS       = YES
  508
+
  509
+#---------------------------------------------------------------------------
  510
+# configuration options related to the alphabetical class index
  511
+#---------------------------------------------------------------------------
  512
+
  513
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
  514
+# of all compounds will be generated. Enable this if the project 
  515
+# contains a lot of classes, structs, unions or interfaces.
  516
+
  517
+ALPHABETICAL_INDEX     = NO
  518
+
  519
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
  520
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
  521
+# in which this list will be split (can be a number in the range [1..20])
  522
+
  523
+COLS_IN_ALPHA_INDEX    = 5
  524
+
  525
+# In case all classes in a project start with a common prefix, all 
  526
+# classes will be put under the same header in the alphabetical index. 
  527
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
  528
+# should be ignored while generating the index headers.
  529
+
  530
+IGNORE_PREFIX          = 
  531
+
  532
+#---------------------------------------------------------------------------
  533
+# configuration options related to the HTML output
  534
+#---------------------------------------------------------------------------
  535
+
  536
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
  537
+# generate HTML output.
  538
+
  539
+GENERATE_HTML          = YES
  540
+
  541
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
  542
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  543
+# put in front of it. If left blank `html' will be used as the default path.
  544
+
  545
+HTML_OUTPUT            = html
  546
+
  547
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
  548
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
  549
+# doxygen will generate files with .html extension.
  550
+
  551
+HTML_FILE_EXTENSION    = .html
  552
+
  553
+# The HTML_HEADER tag can be used to specify a personal HTML header for 
  554
+# each generated HTML page. If it is left blank doxygen will generate a 
  555
+# standard header.
  556
+
  557
+HTML_HEADER            = 
  558
+
  559
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
  560
+# each generated HTML page. If it is left blank doxygen will generate a 
  561
+# standard footer.
  562
+
  563
+HTML_FOOTER            = 
  564
+
  565
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
  566
+# style sheet that is used by each HTML page. It can be used to 
  567
+# fine-tune the look of the HTML output. If the tag is left blank doxygen 
  568
+# will generate a default style sheet. Note that doxygen will try to copy 
  569
+# the style sheet file to the HTML output directory, so don't put your own 
  570
+# stylesheet in the HTML output directory as well, or it will be erased!
  571
+
  572
+HTML_STYLESHEET        = 
  573
+
  574
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
  575
+# files or namespaces will be aligned in HTML using tables. If set to 
  576
+# NO a bullet list will be used.
  577
+
  578
+HTML_ALIGN_MEMBERS     = YES
  579
+
  580
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
  581
+# will be generated that can be used as input for tools like the 
  582
+# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 
  583
+# of the generated HTML documentation.
  584
+
  585
+GENERATE_HTMLHELP      = NO
  586
+
  587
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
  588
+# be used to specify the file name of the resulting .chm file. You 
  589
+# can add a path in front of the file if the result should not be 
  590
+# written to the html output directory.
  591
+
  592
+CHM_FILE               = 
  593
+
  594
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
  595
+# be used to specify the location (absolute path including file name) of 
  596
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
  597
+# the HTML help compiler on the generated index.hhp.
  598
+
  599
+HHC_LOCATION           = 
  600
+
  601
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
  602
+# controls if a separate .chi index file is generated (YES) or that 
  603
+# it should be included in the master .chm file (NO).
  604
+
  605
+GENERATE_CHI           = NO
  606
+
  607
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
  608
+# controls whether a binary table of contents is generated (YES) or a 
  609
+# normal table of contents (NO) in the .chm file.
  610
+
  611
+BINARY_TOC             = NO
  612
+
  613
+# The TOC_EXPAND flag can be set to YES to add extra items for group members 
  614
+# to the contents of the HTML help documentation and to the tree view.
  615
+
  616
+TOC_EXPAND             = NO
  617
+
  618
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
  619
+# top of each HTML page. The value NO (the default) enables the index and 
  620
+# the value YES disables it.
  621
+
  622
+DISABLE_INDEX          = NO
  623
+
  624
+# This tag can be used to set the number of enum values (range [1..20]) 
  625
+# that doxygen will group on one line in the generated HTML documentation.
  626
+
  627
+ENUM_VALUES_PER_LINE   = 4
  628
+
  629
+# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
  630
+# generated containing a tree-like index structure (just like the one that 
  631
+# is generated for HTML Help). For this to work a browser that supports 
  632
+# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, 
  633
+# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are 
  634
+# probably better off using the HTML help feature.
  635
+
  636
+GENERATE_TREEVIEW      = NO
  637
+
  638
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
  639
+# used to set the initial width (in pixels) of the frame in which the tree 
  640
+# is shown.
  641
+
  642
+TREEVIEW_WIDTH         = 250
  643
+
  644
+#---------------------------------------------------------------------------
  645
+# configuration options related to the LaTeX output
  646
+#---------------------------------------------------------------------------
  647
+
  648
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
  649
+# generate Latex output.
  650
+
  651
+GENERATE_LATEX         = YES
  652
+
  653
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
  654
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  655
+# put in front of it. If left blank `latex' will be used as the default path.
  656
+
  657
+LATEX_OUTPUT           = latex
  658
+
  659
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
  660
+# invoked. If left blank `latex' will be used as the default command name.
  661
+
  662
+LATEX_CMD_NAME         = latex
  663
+
  664
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
  665
+# generate index for LaTeX. If left blank `makeindex' will be used as the 
  666
+# default command name.
  667
+
  668
+MAKEINDEX_CMD_NAME     = makeindex
  669
+
  670
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
  671
+# LaTeX documents. This may be useful for small projects and may help to 
  672
+# save some trees in general.
  673
+
  674
+COMPACT_LATEX          = NO
  675
+
  676
+# The PAPER_TYPE tag can be used to set the paper type that is used 
  677
+# by the printer. Possible values are: a4, a4wide, letter, legal and 
  678
+# executive. If left blank a4wide will be used.
  679
+
  680
+PAPER_TYPE             = a4wide
  681
+
  682
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
  683
+# packages that should be included in the LaTeX output.
  684
+
  685
+EXTRA_PACKAGES         = 
  686
+
  687
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
  688
+# the generated latex document. The header should contain everything until 
  689
+# the first chapter. If it is left blank doxygen will generate a 
  690
+# standard header. Notice: only use this tag if you know what you are doing!
  691
+
  692
+LATEX_HEADER           = 
  693
+
  694
+# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
  695
+# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
  696
+# contain links (just like the HTML output) instead of page references 
  697
+# This makes the output suitable for online browsing using a pdf viewer.
  698
+
  699
+PDF_HYPERLINKS         = NO
  700
+
  701
+# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
  702
+# plain latex in the generated Makefile. Set this option to YES to get a 
  703
+# higher quality PDF documentation.
  704
+
  705
+USE_PDFLATEX           = NO
  706
+
  707
+# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
  708
+# command to the generated LaTeX files. This will instruct LaTeX to keep 
  709
+# running if errors occur, instead of asking the user for help. 
  710
+# This option is also used when generating formulas in HTML.
  711
+
  712
+LATEX_BATCHMODE        = NO
  713
+
  714
+# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
  715
+# include the index chapters (such as File Index, Compound Index, etc.) 
  716
+# in the output.
  717
+
  718
+LATEX_HIDE_INDICES     = NO
  719
+
  720
+#---------------------------------------------------------------------------
  721
+# configuration options related to the RTF output
  722
+#---------------------------------------------------------------------------
  723
+
  724
+# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
  725
+# The RTF output is optimized for Word 97 and may not look very pretty with 
  726
+# other RTF readers or editors.
  727
+
  728
+GENERATE_RTF           = NO
  729
+
  730
+# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
  731
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  732
+# put in front of it. If left blank `rtf' will be used as the default path.
  733
+
  734
+RTF_OUTPUT             = rtf
  735
+
  736
+# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
  737
+# RTF documents. This may be useful for small projects and may help to 
  738
+# save some trees in general.
  739
+
  740
+COMPACT_RTF            = NO
  741
+
  742
+# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
  743
+# will contain hyperlink fields. The RTF file will 
  744
+# contain links (just like the HTML output) instead of page references. 
  745
+# This makes the output suitable for online browsing using WORD or other 
  746
+# programs which support those fields. 
  747
+# Note: wordpad (write) and others do not support links.
  748
+
  749
+RTF_HYPERLINKS         = NO
  750
+
  751
+# Load stylesheet definitions from file. Syntax is similar to doxygen's 
  752
+# config file, i.e. a series of assignments. You only have to provide 
  753
+# replacements, missing definitions are set to their default value.
  754
+
  755
+RTF_STYLESHEET_FILE    = 
  756
+
  757
+# Set optional variables used in the generation of an rtf document. 
  758
+# Syntax is similar to doxygen's config file.
  759
+
  760
+RTF_EXTENSIONS_FILE    = 
  761
+
  762
+#---------------------------------------------------------------------------
  763
+# configuration options related to the man page output
  764
+#---------------------------------------------------------------------------
  765
+
  766
+# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
  767
+# generate man pages
  768
+
  769
+GENERATE_MAN           = NO
  770
+
  771
+# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
  772
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  773
+# put in front of it. If left blank `man' will be used as the default path.
  774
+
  775
+MAN_OUTPUT             = man
  776
+
  777
+# The MAN_EXTENSION tag determines the extension that is added to 
  778
+# the generated man pages (default is the subroutine's section .3)
  779
+
  780
+MAN_EXTENSION          = .3
  781
+
  782
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
  783
+# then it will generate one additional man file for each entity 
  784
+# documented in the real man page(s). These additional files 
  785
+# only source the real man page, but without them the man command 
  786
+# would be unable to find the correct page. The default is NO.
  787
+
  788
+MAN_LINKS              = NO
  789
+
  790
+#---------------------------------------------------------------------------
  791
+# configuration options related to the XML output
  792
+#---------------------------------------------------------------------------
  793
+
  794
+# If the GENERATE_XML tag is set to YES Doxygen will 
  795
+# generate an XML file that captures the structure of 
  796
+# the code including all documentation.
  797
+
  798
+GENERATE_XML           = YES
  799
+
  800
+# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
  801
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  802
+# put in front of it. If left blank `xml' will be used as the default path.
  803
+
  804
+XML_OUTPUT             = doxygen-xml
  805
+
  806
+# The XML_SCHEMA tag can be used to specify an XML schema, 
  807
+# which can be used by a validating XML parser to check the 
  808
+# syntax of the XML files.
  809
+
  810
+XML_SCHEMA             = 
  811
+
  812
+# The XML_DTD tag can be used to specify an XML DTD, 
  813
+# which can be used by a validating XML parser to check the 
  814
+# syntax of the XML files.
  815
+
  816
+XML_DTD                = 
  817
+
  818
+# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
  819
+# dump the program listings (including syntax highlighting 
  820
+# and cross-referencing information) to the XML output. Note that 
  821
+# enabling this will significantly increase the size of the XML output.
  822
+
  823
+XML_PROGRAMLISTING     = NO
  824
+
  825
+#---------------------------------------------------------------------------
  826
+# configuration options for the AutoGen Definitions output
  827
+#---------------------------------------------------------------------------
  828
+
  829
+# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
  830
+# generate an AutoGen Definitions (see autogen.sf.net) file 
  831
+# that captures the structure of the code including all 
  832
+# documentation. Note that this feature is still experimental 
  833
+# and incomplete at the moment.
  834
+
  835
+GENERATE_AUTOGEN_DEF   = NO
  836
+
  837
+#---------------------------------------------------------------------------
  838
+# configuration options related to the Perl module output
  839
+#---------------------------------------------------------------------------
  840
+
  841
+# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
  842
+# generate a Perl module file that captures the structure of 
  843
+# the code including all documentation. Note that this 
  844
+# feature is still experimental and incomplete at the 
  845
+# moment.
  846
+
  847
+GENERATE_PERLMOD       = NO
  848
+
  849
+# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
  850
+# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
  851
+# to generate PDF and DVI output from the Perl module output.
  852
+
  853
+PERLMOD_LATEX          = NO
  854
+
  855
+# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
  856
+# nicely formatted so it can be parsed by a human reader.  This is useful 
  857
+# if you want to understand what is going on.  On the other hand, if this 
  858
+# tag is set to NO the size of the Perl module output will be much smaller 
  859
+# and Perl will parse it just the same.
  860
+
  861
+PERLMOD_PRETTY         = YES
  862
+
  863
+# The names of the make variables in the generated doxyrules.make file 
  864
+# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
  865
+# This is useful so different doxyrules.make files included by the same 
  866
+# Makefile don't overwrite each other's variables.
  867
+
  868
+PERLMOD_MAKEVAR_PREFIX = 
  869
+
  870
+#---------------------------------------------------------------------------
  871
+# Configuration options related to the preprocessor   
  872
+#---------------------------------------------------------------------------
  873
+
  874
+# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
  875
+# evaluate all C-preprocessor directives found in the sources and include 
  876
+# files.
  877
+
  878
+ENABLE_PREPROCESSING   = YES
  879
+
  880
+# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
  881
+# names in the source code. If set to NO (the default) only conditional 
  882
+# compilation will be performed. Macro expansion can be done in a controlled 
  883
+# way by setting EXPAND_ONLY_PREDEF to YES.
  884
+
  885
+MACRO_EXPANSION        = NO
  886
+
  887
+# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
  888
+# then the macro expansion is limited to the macros specified with the 
  889
+# PREDEFINED and EXPAND_AS_PREDEFINED tags.
  890
+
  891
+EXPAND_ONLY_PREDEF     = NO
  892
+
  893
+# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
  894
+# in the INCLUDE_PATH (see below) will be search if a #include is found.
  895
+
  896
+SEARCH_INCLUDES        = YES
  897
+
  898
+# The INCLUDE_PATH tag can be used to specify one or more directories that 
  899
+# contain include files that are not input files but should be processed by 
  900
+# the preprocessor.
  901
+
  902
+INCLUDE_PATH           = 
  903
+
  904
+# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
  905
+# patterns (like *.h and *.hpp) to filter out the header-files in the 
  906
+# directories. If left blank, the patterns specified with FILE_PATTERNS will 
  907
+# be used.
  908
+
  909
+INCLUDE_FILE_PATTERNS  = 
  910
+
  911
+# The PREDEFINED tag can be used to specify one or more macro names that 
  912
+# are defined before the preprocessor is started (similar to the -D option of 
  913
+# gcc). The argument of the tag is a list of macros of the form: name 
  914
+# or name=definition (no spaces). If the definition and the = are 
  915
+# omitted =1 is assumed.
  916
+
  917
+PREDEFINED             = 
  918
+
  919
+# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
  920
+# this tag can be used to specify a list of macro names that should be expanded. 
  921
+# The macro definition that is found in the sources will be used.