Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Organize files

  • Loading branch information...
commit a68686d19edc80c370309ab35affee51fabe7388 1 parent 3053aad
@makotok makotok authored
Showing with 8 additions and 29,380 deletions.
  1. +6 −5 {distribute/moai-sdk-run-scripts → bin}/replace-run-scripts.sh
  2. 0  {samples/tutorials/RocketDirective/tutorial/step 02 - make base → bin/run-scripts}/run.bat
  3. +2 −0  {samples/tutorials/RocketDirective → bin/run-scripts}/run.sh
  4. +0 −79 distribute/.gitignore
  5. +0 −23 distribute/docs/README.txt
  6. +0 −70 distribute/docs/legal.txt
  7. +0 −516 distribute/docs/license.txt
  8. +0 −7 distribute/doxygen/.gitignore
  9. +0 −8 distribute/doxygen/README.txt
  10. +0 −1,541 distribute/doxygen/doxyfile-full
  11. +0 −1,541 distribute/doxygen/doxyfile-lua
  12. +0 −28 distribute/doxygen/intro-page.txt
  13. +0 −85 distribute/doxygen/make-docs-lua.bat
  14. BIN  distribute/doxygen/parser/bin/glut32.dll
  15. BIN  distribute/doxygen/parser/bin/lua-5.1.3.dll
  16. BIN  distribute/doxygen/parser/bin/moai-DLL.dll
  17. BIN  distribute/doxygen/parser/bin/moai.exe
  18. +0 −8 distribute/doxygen/parser/fr.bat
  19. +0 −273 distribute/doxygen/parser/header-files.lua
  20. +0 −376 distribute/doxygen/parser/input.test.cpp
  21. +0 −84 distribute/doxygen/parser/input.test.h
  22. +0 −3  distribute/doxygen/parser/luadox/build.bat
  23. BIN  distribute/doxygen/parser/luadox/luadox.cgt
  24. +0 −37 distribute/doxygen/parser/luadox/luadox.grm
  25. +0 −172 distribute/doxygen/parser/luadox/luadox.log
  26. +0 −9 distribute/doxygen/parser/parse-file.bat
  27. +0 −3  distribute/doxygen/parser/predox/build.bat
  28. BIN  distribute/doxygen/parser/predox/predox.cgt
  29. +0 −43 distribute/doxygen/parser/predox/predox.grm
  30. +0 −244 distribute/doxygen/parser/predox/predox.log
  31. +0 −3  distribute/doxygen/parser/process-files.bat
  32. +0 −346 distribute/doxygen/parser/source-files-cpp.lua
  33. +0 −346 distribute/doxygen/parser/source-files-mm.lua
  34. +0 −3  distribute/doxygen/parser/test-header-file.bat
  35. +0 −4 distribute/doxygen/parser/test-source-file.bat
  36. +0 −17 distribute/hosts/ant/README.txt
  37. +0 −2  distribute/hosts/ant/host-source/external/crittercism/classpath.xml
  38. BIN  distribute/hosts/ant/host-source/external/crittercism/lib/crittercism_v1_3_0.jar
  39. +0 −8 distribute/hosts/ant/host-source/external/crittercism/manifest_declarations.xml
  40. +0 −5 distribute/hosts/ant/host-source/external/crittercism/manifest_permissions.xml
  41. +0 −2  distribute/hosts/ant/host-source/external/facebook/manifest_permissions.xml
  42. +0 −8 distribute/hosts/ant/host-source/external/facebook/project/.classpath
  43. +0 −33 distribute/hosts/ant/host-source/external/facebook/project/.project
  44. +0 −6 distribute/hosts/ant/host-source/external/facebook/project/AndroidManifest.xml
  45. +0 −85 distribute/hosts/ant/host-source/external/facebook/project/build.xml
  46. +0 −10 distribute/hosts/ant/host-source/external/facebook/project/local.properties
  47. +0 −12 distribute/hosts/ant/host-source/external/facebook/project/project.properties
  48. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable-hdpi/close.png
  49. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable-hdpi/facebook_icon.png
  50. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable-ldpi/close.png
  51. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable-ldpi/facebook_icon.png
  52. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable-xhdpi/close.png
  53. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable/close.png
  54. BIN  distribute/hosts/ant/host-source/external/facebook/project/res/drawable/facebook_icon.png
  55. +0 −316 distribute/hosts/ant/host-source/external/facebook/project/src/com/facebook/android/AsyncFacebookRunner.java
  56. +0 −51 distribute/hosts/ant/host-source/external/facebook/project/src/com/facebook/android/DialogError.java
  57. +0 −946 distribute/hosts/ant/host-source/external/facebook/project/src/com/facebook/android/Facebook.java
  58. +0 −50 distribute/hosts/ant/host-source/external/facebook/project/src/com/facebook/android/FacebookError.java
  59. +0 −196 distribute/hosts/ant/host-source/external/facebook/project/src/com/facebook/android/FbDialog.java
  60. +0 −301 distribute/hosts/ant/host-source/external/facebook/project/src/com/facebook/android/Util.java
  61. +0 −9 distribute/hosts/ant/host-source/external/google-billing/manifest_declarations.xml
  62. +0 −2  distribute/hosts/ant/host-source/external/google-billing/manifest_permissions.xml
  63. +0 −24 ...te/hosts/ant/host-source/external/google-billing/src/com/android/vending/billing/IMarketBillingService.aidl
  64. BIN  distribute/hosts/ant/host-source/external/google-push/lib/gcm.jar
  65. +0 −11 distribute/hosts/ant/host-source/external/google-push/manifest_declarations.xml
  66. +0 −4 distribute/hosts/ant/host-source/external/google-push/manifest_permissions.xml
  67. +0 −556 distribute/hosts/ant/host-source/external/miscellaneous/src/com/external/base64/Base64.java
  68. +0 −31 distribute/hosts/ant/host-source/external/miscellaneous/src/com/external/base64/Base64DecoderException.java
  69. +0 −11 distribute/hosts/ant/host-source/external/tapjoy/manifest_declarations.xml
  70. +0 −5 distribute/hosts/ant/host-source/external/tapjoy/manifest_permissions.xml
  71. +0 −8 distribute/hosts/ant/host-source/external/tapjoy/project/.classpath
  72. +0 −33 distribute/hosts/ant/host-source/external/tapjoy/project/.project
  73. +0 −6 distribute/hosts/ant/host-source/external/tapjoy/project/AndroidManifest.xml
  74. +0 −85 distribute/hosts/ant/host-source/external/tapjoy/project/build.xml
  75. +0 −10 distribute/hosts/ant/host-source/external/tapjoy/project/local.properties
  76. +0 −12 distribute/hosts/ant/host-source/external/tapjoy/project/project.properties
  77. +0 −13 distribute/hosts/ant/host-source/external/tapjoy/project/res/drawable/tapjoy_buttonnormal.xml
  78. +0 −9 distribute/hosts/ant/host-source/external/tapjoy/project/res/drawable/tapjoy_buttonselected.xml
  79. +0 −5 distribute/hosts/ant/host-source/external/tapjoy/project/res/drawable/tapjoy_gradientline.xml
  80. +0 −7 distribute/hosts/ant/host-source/external/tapjoy/project/res/drawable/tapjoy_tablerowstates.xml
  81. BIN  distribute/hosts/ant/host-source/external/tapjoy/project/res/drawable/tapjoy_virtualgoods_error.png
  82. +0 −17 distribute/hosts/ant/host-source/external/tapjoy/project/res/drawable/tapjoy_virtualgoods_row_bg.xml
  83. +0 −369 distribute/hosts/ant/host-source/external/tapjoy/project/res/layout/tapjoy_virtualgoods.xml
  84. +0 −92 distribute/hosts/ant/host-source/external/tapjoy/project/res/layout/tapjoy_virtualgoods_purchaseitems_row.xml
  85. +0 −28 ...bute/hosts/ant/host-source/external/tapjoy/project/res/layout/tapjoy_virtualgoods_reconnectvirtualgoods.xml
  86. +0 −61 distribute/hosts/ant/host-source/external/tapjoy/project/res/layout/tapjoy_virtualgoods_row.xml
  87. +0 −14 distribute/hosts/ant/host-source/external/tapjoy/project/res/values/tapjoy.xml
  88. +0 −90 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/DownloadVirtualGood.java
  89. +0 −432 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TJCOffers.java
  90. +0 −385 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TJCOffersWebView.java
  91. +0 −1,085 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TJCVirtualGoodUtil.java
  92. +0 −2,345 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TJCVirtualGoods.java
  93. +0 −63 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TJCVirtualGoodsConnection.java
  94. +0 −1,154 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TJCVirtualGoodsData.java
  95. +0 −33 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyAwardPointsNotifier.java
  96. +0 −457 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyConnect.java
  97. +0 −957 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyConnectCore.java
  98. +0 −143 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyConstants.java
  99. +0 −468 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyDisplayAd.java
  100. +0 −35 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyDisplayAdNotifier.java
  101. +0 −26 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyDisplayAdSize.java
  102. +0 −68 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyDisplayMetricsUtil.java
  103. +0 −23 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyEarnedPointsNotifier.java
  104. +0 −275 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyFeaturedApp.java
  105. +0 −33 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyFeaturedAppNotifier.java
  106. +0 −52 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyFeaturedAppObject.java
  107. +0 −244 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyFeaturedAppWebView.java
  108. +0 −44 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyHardwareUtil.java
  109. +0 −88 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyLog.java
  110. +0 −32 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyNotifier.java
  111. +0 −65 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyReferralTracker.java
  112. +0 −33 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoySpendPointsNotifier.java
  113. +0 −258 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyURLConnection.java
  114. +0 −172 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyUtil.java
  115. +0 −847 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyVideo.java
  116. +0 −21 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyVideoNotifier.java
  117. +0 −43 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyVideoObject.java
  118. +0 −32 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyVideoStatus.java
  119. +0 −957 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/TapjoyVideoView.java
  120. +0 −190 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/VGStoreItem.java
  121. +0 −44 distribute/hosts/ant/host-source/external/tapjoy/project/src/com/tapjoy/VGStoreItemAttributeValue.java
  122. +0 −1  distribute/hosts/ant/host-source/init.lua
  123. +0 −49 distribute/hosts/ant/host-source/moai/crittercism/MoaiCrittercism.java
  124. +0 −288 distribute/hosts/ant/host-source/moai/facebook/MoaiFacebook.java
  125. +0 −149 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBilling.java
  126. +0 −80 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBillingConstants.java
  127. +0 −91 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBillingPurchaseObserver.java
  128. +0 −81 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBillingReceiver.java
  129. +0 −76 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBillingResponseHandler.java
  130. +0 −238 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBillingSecurity.java
  131. +0 −538 distribute/hosts/ant/host-source/moai/google-billing/MoaiGoogleBillingService.java
  132. +0 −93 distribute/hosts/ant/host-source/moai/google-push/MoaiGooglePush.java
  133. +0 −48 distribute/hosts/ant/host-source/moai/google-push/MoaiGooglePushConstants.java
  134. +0 −153 distribute/hosts/ant/host-source/moai/google-push/MoaiGooglePushReceiver.java
  135. +0 −94 distribute/hosts/ant/host-source/moai/tapjoy/MoaiTapjoy.java
  136. +0 −11 distribute/hosts/ant/host-source/project/.classpath
  137. +0 −33 distribute/hosts/ant/host-source/project/.project
  138. +0 −65 distribute/hosts/ant/host-source/project/AndroidManifest.xml
  139. +0 −21 distribute/hosts/ant/host-source/project/ant.properties
  140. +0 −85 distribute/hosts/ant/host-source/project/build.xml
  141. +0 −10 distribute/hosts/ant/host-source/project/local.properties
  142. +0 −44 distribute/hosts/ant/host-source/project/proguard.cfg
  143. +0 −11 distribute/hosts/ant/host-source/project/project.properties
  144. +0 −4 distribute/hosts/ant/host-source/project/res/values/strings.xml
  145. +0 −501 distribute/hosts/ant/host-source/project/src/com/getmoai/samples/MoaiActivity.java
  146. +0 −266 distribute/hosts/ant/host-source/project/src/com/getmoai/samples/MoaiView.java
  147. +0 −691 distribute/hosts/ant/host-source/project/src/com/ziplinegames/moai/Moai.java
  148. +0 −107 distribute/hosts/ant/host-source/project/src/com/ziplinegames/moai/MoaiLocalNotificationReceiver.java
  149. +0 −45 distribute/hosts/ant/host-source/project/src/com/ziplinegames/moai/MoaiLog.java
  150. +0 −180 distribute/hosts/ant/host-source/project/src/com/ziplinegames/moai/MoaiMoviePlayer.java
  151. BIN  distribute/hosts/ant/res/icon-hdpi.png
  152. BIN  distribute/hosts/ant/res/icon-ldpi.png
  153. BIN  distribute/hosts/ant/res/icon-mdpi.png
  154. BIN  distribute/hosts/ant/res/icon-xhdpi.png
  155. +0 −31 distribute/hosts/ant/run-host.bat
  156. +0 −227 distribute/hosts/ant/run-host.sh
  157. +0 −8 distribute/hosts/ant/sdk-setup.bat
  158. +0 −10 distribute/hosts/ant/sdk-setup.sh
  159. +0 −49 distribute/hosts/ant/settings-global.sh
  160. +0 −34 distribute/hosts/ant/settings-local.sh
  161. BIN  distribute/hosts/chrome/Icon_128.png
  162. BIN  distribute/hosts/chrome/Icon_16.png
  163. +0 −57 distribute/hosts/chrome/Moai.html
  164. BIN  distribute/hosts/chrome/bannerMoai.png
  165. +0 −7 distribute/hosts/chrome/bind.js
  166. BIN  distribute/hosts/chrome/logo.png
  167. +0 −19 distribute/hosts/chrome/manifest.json
  168. +0 −121 distribute/hosts/chrome/moai_base.js
  169. +0 −8 distribute/hosts/chrome/sdk-setup.bat
  170. +0 −11 distribute/hosts/chrome/sdk-setup.sh
  171. +0 −43 distribute/hosts/chrome/style1.css
  172. +0 −80 distribute/hosts/src/FolderWatcher-mac.h
  173. +0 −339 distribute/hosts/src/FolderWatcher-mac.mm
  174. +0 −268 distribute/hosts/src/FolderWatcher-win.cpp
  175. +0 −8 distribute/hosts/src/FolderWatcher-win.h
  176. +0 −435 distribute/hosts/src/GlutHost.cpp
  177. +0 −11 distribute/hosts/src/GlutHost.h
  178. +0 −18 distribute/hosts/src/GlutHostMain.cpp
  179. +0 −172 distribute/hosts/src/GlutHostTest.cpp
  180. +0 −10 distribute/hosts/src/GlutHostTest.h
  181. +0 −14 distribute/hosts/src/GlutHostTestMain.cpp
  182. +0 −51 distribute/hosts/src/ParticlePresets.cpp
  183. +0 −10 distribute/hosts/src/ParticlePresets.h
  184. +0 −41 distribute/hosts/vs2008/moai-host.sln
  185. +0 −384 distribute/hosts/vs2008/moai-untz/moai-untz.vcproj
  186. +0 −384 distribute/hosts/vs2008/moai/moai.vcproj
  187. +0 −5 distribute/hosts/vs2008/msbuild.xml
  188. +0 −36 distribute/hosts/vs2010/moai-host.sln
  189. +0 −236 distribute/hosts/vs2010/moai-untz/moai-untz.vcxproj
  190. +0 −237 distribute/hosts/vs2010/moai/moai.vcxproj
  191. +0 −5 distribute/hosts/vs2010/msbuild.xml
  192. +0 −74 distribute/hosts/xcode/ios/Classes/LocationObserver.h
  193. +0 −211 distribute/hosts/xcode/ios/Classes/LocationObserver.mm
  194. +0 −29 distribute/hosts/xcode/ios/Classes/MoaiAppDelegate.h
  195. +0 −149 distribute/hosts/xcode/ios/Classes/MoaiAppDelegate.mm
  196. +0 −15 distribute/hosts/xcode/ios/Classes/MoaiVC.h
  197. +0 −84 distribute/hosts/xcode/ios/Classes/MoaiVC.mm
  198. +0 −40 distribute/hosts/xcode/ios/Classes/MoaiView.h
  199. +0 −331 distribute/hosts/xcode/ios/Classes/MoaiView.mm
  200. +0 −41 distribute/hosts/xcode/ios/Classes/OpenGLView.h
  201. +0 −216 distribute/hosts/xcode/ios/Classes/OpenGLView.mm
  202. +0 −200 distribute/hosts/xcode/ios/Classes/RefPtr.h
  203. +0 −8 distribute/hosts/xcode/ios/Entitlements.plist
  204. BIN  distribute/hosts/xcode/ios/Icon-72.png
  205. BIN  distribute/hosts/xcode/ios/Icon-Small-50.png
  206. BIN  distribute/hosts/xcode/ios/Icon-Small.png
  207. BIN  distribute/hosts/xcode/ios/Icon-Small@2x.png
  208. BIN  distribute/hosts/xcode/ios/Icon.png
  209. BIN  distribute/hosts/xcode/ios/Icon@2x.png
  210. +0 −39 distribute/hosts/xcode/ios/Info.plist
  211. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginNormal.png
  212. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginNormal@2x.png
  213. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginPressed.png
  214. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginPressed@2x.png
  215. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginWithFacebookNormal.png
  216. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginWithFacebookNormal@2x.png
  217. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginWithFacebookPressed.png
  218. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LoginWithFacebookPressed@2x.png
  219. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LogoutNormal.png
  220. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LogoutNormal@2x.png
  221. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LogoutPressed.png
  222. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/LogoutPressed@2x.png
  223. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBConnect.bundle/images/runaround_image.jpg
  224. BIN  ...e/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/Contents/Resources/en.lproj/Localizable.strings
  225. BIN  ...e/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/Contents/Resources/he.lproj/Localizable.strings
  226. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/facebook-logo.png
  227. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/facebook-logo@2x.png
  228. BIN  ...sts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/loginBackgroundIPadLandscape.jpg
  229. BIN  .../xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/loginBackgroundIPadLandscape@2x.jpg
  230. BIN  ...osts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/loginBackgroundIPadPortrait.jpg
  231. BIN  ...s/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/loginBackgroundIPadPortrait@2x.jpg
  232. BIN  ...ts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/loginBackgroundIPhonePortrait.jpg
  233. BIN  ...xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/loginBackgroundIPhonePortrait@2x.jpg
  234. BIN  ...ibute/hosts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/silver-button-normal.png
  235. BIN  ...te/hosts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/silver-button-normal@2x.png
  236. BIN  ...bute/hosts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/silver-button-pressed.png
  237. BIN  ...e/hosts/xcode/ios/Libraries/Facebook/FBUserSettingsViewResources.bundle/images/silver-button-pressed@2x.png
  238. BIN  ...ts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/Contents/Resources/en.lproj/Localizable.strings
  239. BIN  ...ts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/Contents/Resources/he.lproj/Localizable.strings
  240. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBDialog/images/close.png
  241. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBDialog/images/close@2x.png
  242. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBDialog/images/fbicon.png
  243. BIN  ...ribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBFriendPickerView/images/default.png
  244. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/bluetint.png
  245. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/f_logo.png
  246. BIN  distribute/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/facebook.png
  247. BIN  .../xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/login-button-small-pressed.png
  248. BIN  ...ode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/login-button-small-pressed@2x.png
  249. BIN  ...te/hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/login-button-small.png
  250. BIN  ...hosts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBLoginView/images/login-button-small@2x.png
  251. BIN  ...osts/xcode/ios/Libraries/Facebook/FacebookSDKResources.bundle/FBPlacePickerView/images/fb_generic_place.png
  252. BIN  ...os/Libraries/Facebook/FacebookSDKResources.bundle/FBProfilePictureView/images/fb_blank_profile_portrait.png
  253. BIN  .../ios/Libraries/Facebook/FacebookSDKResources.bundle/FBProfilePictureView/images/fb_blank_profile_square.png
Sorry, we could not display the entire diff because too many files (635) changed.
View
11 ...ibute/moai-sdk-run-scripts/replace-run-scripts.sh → bin/replace-run-scripts.sh
@@ -7,11 +7,12 @@
#================================================================#
set -e
+cd `dirname $0`
-for f in $(find ../moai-sdk/samples -type f -name run.bat); do
+for f in $(find ../samples -type f -name run.bat); do
echo "Replacing $f";
- rm -f ${f%/*}/run.bat;
- cp -f run.bat ${f%/*}/run.bat;
- rm -f ${f%/*}/run.sh;
- cp -f run.sh ${f%/*}/run.sh;
+ rm -f "${f%/*}/run.bat";
+ cp -f "run-scripts/run.bat" "${f%/*}/run.bat";
+ rm -f "${f%/*}/run.sh";
+ cp -f "run-scripts/run.sh" "${f%/*}/run.sh";
done
View
0  ...ketDirective/tutorial/step 02 - make base/run.bat → bin/run-scripts/run.bat
File renamed without changes
View
2  samples/tutorials/RocketDirective/run.sh → bin/run-scripts/run.sh
@@ -5,6 +5,8 @@
# http://getmoai.com
#--------------------------------------------------------------------------------------
+cd `dirname $0`
+
# Verify paths
if [ ! -f "$MOAI_BIN/moai" ]; then
echo "---------------------------------------------------------------------------"
View
79 distribute/.gitignore
@@ -1,79 +0,0 @@
-!moai-sdk/
-
-moai-sdk/*
-!moai-sdk/hosts
-!moai-sdk/README.txt
-!moai-sdk/legal.txt
-!moai-sdk/license.txt
-
-moai-sdk/hosts/*
-!moai-sdk/hosts/ant
-!moai-sdk/hosts/chrome
-!moai-sdk/hosts/vs2008
-!moai-sdk/hosts/vs2010
-!moai-sdk/hosts/xcode
-
-moai-sdk/hosts/ant/*
-!moai-sdk/hosts/ant/sdk-setup.bat
-!moai-sdk/hosts/ant/sdk-setup.sh
-!moai-sdk/hosts/ant/settings-local.sh
-
-moai-sdk/hosts/chrome/*
-!moai-sdk/hosts/chrome/bannerMoai.png
-!moai-sdk/hosts/chrome/bind.js
-!moai-sdk/hosts/chrome/Icon_128.png
-!moai-sdk/hosts/chrome/Icon_16.png
-!moai-sdk/hosts/chrome/logo.png
-!moai-sdk/hosts/chrome/manifest.json
-!moai-sdk/hosts/chrome/Moai.html
-!moai-sdk/hosts/chrome/moai_base.js
-!moai-sdk/hosts/chrome/sdk-setup.bat
-!moai-sdk/hosts/chrome/sdk-setup.sh
-!moai-sdk/hosts/chrome/style1.css
-
-moai-sdk/hosts/vs2008/*
-!moai-sdk/hosts/vs2008/moai
-!moai-sdk/hosts/vs2008/moai-untz
-!moai-sdk/hosts/vs2008/moai-host.sln
-
-moai-sdk/hosts/vs2008/moai/*
-!moai-sdk/hosts/vs2008/moai/moai.vcproj
-
-moai-sdk/hosts/vs2008/moai-untz/*
-!moai-sdk/hosts/vs2008/moai-untz/moai-untz.vcproj
-
-moai-sdk/hosts/vs2010/*
-!moai-sdk/hosts/vs2010/moai
-!moai-sdk/hosts/vs2010/moai-untz
-!moai-sdk/hosts/vs2010/moai-host.sln
-
-moai-sdk/hosts/vs2010/moai/*
-!moai-sdk/hosts/vs2010/moai/moai.vcxproj
-
-moai-sdk/hosts/vs2010/moai-untz/*
-!moai-sdk/hosts/vs2010/moai-untz/moai-untz.vcxproj
-
-moai-sdk/hosts/xcode/*
-!moai-sdk/hosts/xcode/ios
-!moai-sdk/hosts/xcode/osx
-
-moai-sdk/hosts/xcode/ios/*
-!moai-sdk/hosts/xcode/ios/moai.xcodeproj
-!moai-sdk/hosts/xcode/ios/moai_Prefix.pch
-
-moai-sdk/hosts/xcode/ios/moai.xcodeproj/*
-!moai-sdk/hosts/xcode/ios/moai.xcodeproj/project.xcworkspace
-!moai-sdk/hosts/xcode/ios/moai.xcodeproj/project.pbxproj
-
-moai-sdk/hosts/xcode/ios/moai.xcodeproj/project.xcworkspace/*
-!moai-sdk/hosts/xcode/ios/moai.xcodeproj/project.xcworkspace/contents.xcworkspacedata
-
-moai-sdk/hosts/xcode/osx/*
-!moai-sdk/hosts/xcode/osx/moai.xcodeproj
-
-moai-sdk/hosts/xcode/osx/moai.xcodeproj/*
-!moai-sdk/hosts/xcode/osx/moai.xcodeproj/project.xcworkspace
-!moai-sdk/hosts/xcode/osx/moai.xcodeproj/project.pbxproj
-
-moai-sdk/hosts/xcode/osx/moai.xcodeproj/project.xcworkspace/*
-!moai-sdk/hosts/xcode/osx/moai.xcodeproj/project.xcworkspace/contents.xcworkspacedata
View
0  distribute/CHANGELOG.txt
Sorry, we could not display the changes to this file because there were too many other changes to display.
View
23 distribute/docs/README.txt
@@ -1,23 +0,0 @@
-Welcome to Moai!
-
-Thanks for installing the Moai SDK. Here's the scoop.
-
-Sample code:
-Go to the samples folder, choose a sample, then execute run.bat (or run.sh) to see it perform. One of our priorities is to build richer samples for Moai developers, so if you'd like to see a particular code sample, let us know by posting in the Moai forums at http://getmoai.com/forums/.
-
-Object model documentation:
-You can view the object model documentation in the docs folder (index.html) or at http://getmoai.com/docs/.
-
-FAQ:
-Answers to frequently asked questions are available in the Moai FAQ at http://getmoai.com/marketing/moai-faqs.html.
-
-Wiki:
-You can find detailed documentation, instructions and other helpful information in the Moai Wiki at http://getmoai.com/wiki/.
-
-Moai Cloud:
-You already have a Moai Cloud account which allows you to upload Lua scripts to be hosted and run as web services via the Moai Cloud Dashboard at http://dashboard.moaicloud.com/. If you have support questions, post them to the Moai Cloud Developer Support Forum at http://getmoai.com/forums/moai-cloud-developer-support.html or check out the Moai Wiki at http://getmoai.com/wiki/.
-
-License:
-This SDK uses the CPAL license (http://www.opensource.org/licenses/cpal_1.0). Refer to the Made With Moai page at http://getmoai.com/marketing/made-with-moai.html for attribution screens to include with games made with Moai.
-
-Happy game-making with Moai. Check out the Moai Wiki at http://getmoai.com/wiki/, ping us through the forums at http://getmoai.com/forums/ or email us at support@getmoai.com if you need help. The Moai team is here to help.
View
70 distribute/docs/legal.txt
@@ -1,70 +0,0 @@
-LEGAL INFORMATION
-
-This LEGAL.txt file accompanies the Moai SDK. It includes notices required by the licenses as well as general legal notices.
-
-Software in the '3rdparty' folder is covered under separate licenses as provided in that folder.
-
-=========================================
- COPYRIGHT AND ATTRIBUTION NOTICES
-=========================================
-
-Copyright (c) 2010-2011 Zipline Games, Inc. All Rights Reserved.
-
-Made with Moai
-
-www.getmoai.com
-
-=========================================
- SOURCE CODE AVAILABILITY NOTICE
-=========================================
-
-The source code for this product is available from http://getmoai.com.
-
-=========================================
- GENERAL LEGAL NOTICES
-=========================================
-
-Moai is a trademark of Zipline Games, Inc.
-
-=========================================
- SOURCE CODE LICENSE
-=========================================
-
-Except as explicitly indicated in the file itself, the contents of all files
-that make up this product are subject to the Common Public Attribution License
-Version 1.0 (the "License"; alternatively, the "CPAL"); you may not use the
-files except in compliance with the License. You may obtain a copy of the
-License at http://getmoai.com/license. The License is based on the Mozilla
-Public License Version 1.1 but Sections 14 and 15 have been added to cover
-use of software over a computer network and provide for limited attribution
-for the Original Developer. In addition, Exhibit A has been modified to be
-consistent with Exhibit B.
-
-Software distributed under the License is distributed on an "AS IS" basis,
-WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for
-the specific language governing rights and limitations under the License.
-
-=========================================
- LEGAL NOTICES REQUIRED BY THE LICENSE
-=========================================
-
-CHANGES MADE TO THE COVERED CODE (see CPAL Section 3.3):
-
-2011-03-01, Patrick Meehan:
- Original Code based on Moai SDK 1.0.
- Licensing notices added to all applicable files.
-
-----
-
-(Documentation of future changes as the result of Modifications, including the
-date of change, will go here in this LEGAL.txt file. This documentation may be
-summaries of changes with the more detailed descriptions included in the actual
-modified files as appropriate.)
-
-=========================================
- THIRD PARTY CLAIMS
-=========================================
-
-(See CPAL Section 3.4(a)):
-
-None known at present.
View
516 distribute/docs/license.txt
@@ -1,516 +0,0 @@
-Zipline Games, Inc. - Moai SDK
-
-Common Public Attribution License Version 1.0 (CPAL)
-
-1. "Definitions"
-
-1.0.1 "Commercial Use" means distribution or otherwise making the Covered Code
- available to a third party.
-
-1.1 "Contributor" means each entity that creates or contributes to the creation
- of Modifications.
-
-1.2 "Contributor Version" means the combination of the Original Code, prior
- Modifications used by a Contributor, and the Modifications made by that
- particular Contributor.
-
-1.3 "Covered Code" means the Original Code or Modifications or the combination
- of the Original Code and Modifications, in each case including portions
- thereof.
-
-1.4 "Electronic Distribution Mechanism" means a mechanism generally accepted in
- the software development community for the electronic transfer of data.
-
-1.5 "Executable" means Covered Code in any form other than Source Code.
-
-1.6 "Initial Developer" means the individual or entity identified as the Initial
- Developer in the Source Code notice required by Exhibit A.
-
-1.7 "Larger Work" means a work which combines Covered Code or portions thereof
- with code not governed by the terms of this License.
-
-1.8 "License" means this document.
-
-1.8.1 "Licensable" means having the right to grant, to the maximum extent
- possible, whether at the time of the initial grant or subsequently acquired,
- any and all of the rights conveyed herein.
-
-1.9 "Modifications" means any addition to or deletion from the substance or
- structure of either the Original Code or any previous Modifications. When
- Covered Code is released as a series of files, a Modification is:
-
-A. Any addition to or deletion from the contents of a file containing Original
-Code or previous Modifications.
-
-B. Any new file that contains any part of the Original Code or previous
-Modifications.
-
-1.10 "Original Code" means Source Code of computer software code which is
- described in the Source Code notice required by Exhibit A as Original Code,
- and which, at the time of its release under this License is not already
- Covered Code governed by this License.
-
-1.10.1 "Patent Claims" means any patent claim(s), now owned or hereafter
- acquired, including without limitation, method, process, and apparatus
- claims, in any patent Licensable by grantor.
-
-1.11 "Source Code" means the preferred form of the Covered Code for making
- modifications to it, including all modules it contains, plus any associated
- interface definition files, scripts used to control compilation and
- installation of an Executable, or source code differential comparisons against
- either the Original Code or another well known, available Covered Code of the
- Contributor's choice. The Source Code can be in a compressed or archival form,
- provided the appropriate decompression or de-archiving software is widely
- available for no charge.
-
-1.12 "You" (or "Your") means an individual or a legal entity exercising rights
- under, and complying with all of the terms of, this License or a future
- version of this License issued under Section 6.1. For legal entities, "You"
- includes any entity which controls, is controlled by, or is under common
- control with You. For purposes of this definition, "control" means (a) the
- power, direct or indirect, to cause the direction or management of such
- entity, whether by contract or otherwise, or (b) ownership of more than fifty
- percent (50%) of the outstanding shares or beneficial ownership of such
- entity.
-
-2. Source Code License.
-
-2.1 The Initial Developer Grant.
-
-The Initial Developer hereby grants You a world-wide, royalty-free,
-non-exclusive license, subject to third party intellectual property claims:
-
-(a) under intellectual property rights (other than patent or trademark)
-Licensable by Initial Developer to use, reproduce, modify, display, perform,
-sublicense and distribute the Original Code (or portions thereof) with or
-without Modifications, and/or as part of a Larger Work; and
-
-(b) under Patents Claims infringed by the making, using or selling of Original
-Code, to make, have made, use, practice, sell, and offer for sale, and/or
-otherwise dispose of the Original Code (or portions thereof).
-
-(c) the licenses granted in this Section 2.1(a) and (b) are effective on the
-date Initial Developer first distributes Original Code under the terms of this
-License.
-
-(d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for
-code that You delete from the Original Code; 2) separate from the Original Code;
-or 3) for infringements caused by: i) the modification of the Original Code or
-ii) the combination of the Original Code with other software or devices.
-
-2.2 Contributor Grant.
-
-Subject to third party intellectual property claims, each Contributor hereby
-grants You a world-wide, royalty-free, non-exclusive license
-
-(a) under intellectual property rights (other than patent or trademark)
-Licensable by Contributor, to use, reproduce, modify, display, perform,
-sublicense and distribute the Modifications created by such Contributor (or
-portions thereof) either on an unmodified basis, with other Modifications, as
-Covered Code and/or as part of a Larger Work; and
-
-(b) under Patent Claims infringed by the making, using, or selling of
-Modifications made by that Contributor either alone and/or in combination with
-its Contributor Version (or portions of such combination), to make, use, sell,
-offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by
-that Contributor (or portions thereof); and 2) the combination of Modifications
-made by that Contributor with its Contributor Version (or portions of such
-combination).
-
-(c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date
-Contributor first makes Commercial Use of the Covered Code.
-
-(d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for
-any code that Contributor has deleted from the Contributor Version; 2) separate
-from the Contributor Version; 3) for infringements caused by: i) third party
-modifications of Contributor Version or ii) the combination of Modifications
-made by that Contributor with other software (except as part of the Contributor
-Version) or other devices; or 4) under Patent Claims infringed by Covered Code
-in the absence of Modifications made by that Contributor.
-
-3. Distribution Obligations.
-
-3.1 Application of License.
-
-The Modifications which You create or to which You contribute are governed by
-the terms of this License, including without limitation Section 2.2. The Source
-Code version of Covered Code may be distributed only under the terms of this
-License or a future version of this License released under Section 6.1, and You
-must include a copy of this License with every copy of the Source Code You
-distribute. You may not offer or impose any terms on any Source Code version
-that alters or restricts the applicable version of this License or the
-recipients' rights hereunder. However, You may include an additional document
-offering the additional rights described in Section 3.5.
-
-3.2 Availability of Source Code.
-
-Any Modification which You create or to which You contribute must be made
-available in Source Code form under the terms of this License either on the same
-media as an Executable version or via an accepted Electronic Distribution
-Mechanism to anyone to whom you made an Executable version available; and if
-made available via Electronic Distribution Mechanism, must remain available for
-at least twelve (12) months after the date it initially became available, or at
-least six (6) months after a subsequent version of that particular Modification
-has been made available to such recipients. You are responsible for ensuring
-that the Source Code version remains available even if the Electronic
-Distribution Mechanism is maintained by a third party.
-
-3.3 Description of Modifications.
-
-You must cause all Covered Code to which You contribute to contain a file
-documenting the changes You made to create that Covered Code and the date of any
-change. You must include a prominent statement that the Modification is derived,
-directly or indirectly, from Original Code provided by the Initial Developer and
-including the name of the Initial Developer in (a) the Source Code, and (b) in
-any notice in an Executable version or related documentation in which You
-describe the origin or ownership of the Covered Code.
-
-3.4 Intellectual Property Matters
-
-(a) Third Party Claims.
-
-If Contributor has knowledge that a license under a third party's intellectual
-property rights is required to exercise the rights granted by such Contributor
-under Sections 2.1 or 2.2, Contributor must include a text file with the Source
-Code distribution titled "LEGAL" which describes the claim and the party making
-the claim in sufficient detail that a recipient will know whom to contact. If
-Contributor obtains such knowledge after the Modification is made available as
-described in Section 3.2, Contributor shall promptly modify the LEGAL file in
-all copies Contributor makes available thereafter and shall take other steps
-(such as notifying appropriate mailing lists or newsgroups) reasonably
-calculated to inform those who received the Covered Code that new knowledge has
-been obtained.
-
-(b) Contributor APIs.
-
-If Contributor's Modifications include an application programming interface and
-Contributor has knowledge of patent licenses which are reasonably necessary to
-implement that API, Contributor must also include this information in the LEGAL
-file.
-
-(c) Representations.
-
-Contributor represents that, except as disclosed pursuant to Section 3.4(a)
-above, Contributor believes that Contributor's Modifications are Contributor's
-original creation(s) and/or Contributor has sufficient rights to grant the
-rights conveyed by this License.
-
-3.5 Required Notices.
-
-You must duplicate the notice in Exhibit A in each file of the Source Code. If
-it is not possible to put such notice in a particular Source Code file due to
-its structure, then You must include such notice in a location (such as a
-relevant directory) where a user would be likely to look for such a notice. If
-You created one or more Modification(s) You may add your name as a Contributor
-to the notice described in Exhibit A. You must also duplicate this License in
-any documentation for the Source Code where You describe recipients' rights or
-ownership rights relating to Covered Code. You may choose to offer, and to
-charge a fee for, warranty, support, indemnity or liability obligations to one
-or more recipients of Covered Code. However, You may do so only on Your own
-behalf, and not on behalf of the Initial Developer or any Contributor. You must
-make it absolutely clear than any such warranty, support, indemnity or liability
-obligation is offered by You alone, and You hereby agree to indemnify the
-Initial Developer and every Contributor for any liability incurred by the
-Initial Developer or such Contributor as a result of warranty, support,
-indemnity or liability terms You offer.
-
-3.6 Distribution of Executable Versions.
-
-You may distribute Covered Code in Executable form only if the requirements of
-Section 3.1-3.5 have been met for that Covered Code, and if You include a notice
-stating that the Source Code version of the Covered Code is available under the
-terms of this License, including a description of how and where You have
-fulfilled the obligations of Section 3.2. The notice must be conspicuously
-included in any notice in an Executable version, related documentation or
-collateral in which You describe recipients' rights relating to the Covered
-Code. You may distribute the Executable version of Covered Code or ownership
-rights under a license of Your choice, which may contain terms different from
-this License, provided that You are in compliance with the terms of this License
-and that the license for the Executable version does not attempt to limit or
-alter the recipient's rights in the Source Code version from the rights set
-forth in this License. If You distribute the Executable version under a
-different license You must make it absolutely clear that any terms which differ
-from this License are offered by You alone, not by the Initial Developer,
-Original Developer or any Contributor. You hereby agree to indemnify the Initial
-Developer, Original Developer and every Contributor for any liability incurred
-by the Initial Developer, Original Developer or such Contributor as a result of
-any such terms You offer.
-
-3.7 Larger Works.
-
-You may create a Larger Work by combining Covered Code with other code not
-governed by the terms of this License and distribute the Larger Work as a single
-product. In such a case, You must make sure the requirements of this License are
-fulfilled for the Covered Code.
-
-4. Inability to Comply Due to Statute or Regulation.
-
-If it is impossible for You to comply with any of the terms of this License with
-respect to some or all of the Covered Code due to statute, judicial order, or
-regulation then You must: (a) comply with the terms of this License to the
-maximum extent possible; and (b) describe the limitations and the code they
-affect. Such description must be included in the LEGAL file described in Section
-3.4 and must be included with all distributions of the Source Code. Except to
-the extent prohibited by statute or regulation, such description must be
-sufficiently detailed for a recipient of ordinary skill to be able to understand
-it.
-
-5. Application of this License.
-
-This License applies to code to which the Initial Developer has attached the
-notice in Exhibit A and to related Covered Code.
-
-6. Versions of the License.
-
-6.1 New Versions.
-
-CondeNet, Inc. ("CondeNet") may publish revised and/or new versions of the
-License from time to time. Each version will be given a distinguishing version
-number.
-
-6.2 Effect of New Versions.
-
-Once Covered Code has been published under a particular version of the License,
-You may always continue to use it under the terms of that version. You may also
-choose to use such Covered Code under the terms of any subsequent version of the
-License published by CondeNet. No one other than CondeNet has the right to
-modify the terms applicable to Covered Code created under this License.
-
-6.3 Derivative Works.
-
-If You create or use a modified version of this License (which you may only do
-in order to apply it to code which is not already Covered Code governed by this
-License), You must (a) rename Your license so that the phrases "CondeNet",
-"CPAL" or any confusingly similar phrase do not appear in your license (except
-to note that your license differs from this License) and (b) otherwise make it
-clear that Your version of the license contains terms which differ from the
-CPAL. (Filling in the name of the Initial Developer, Original Developer,
-Original Code or Contributor in the notice described in Exhibit A shall not of
-themselves be deemed to be modifications of this License.)
-
-7. DISCLAIMER OF WARRANTY.
-
-COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
-LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE,
-FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE
-QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE
-PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER, ORIGINAL
-DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING,
-REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART
-OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER
-THIS DISCLAIMER.
-
-8. TERMINATION.
-
-8.1 This License and the rights granted hereunder will terminate automatically
- if You fail to comply with terms herein and fail to cure such breach within 30
- days of becoming aware of the breach. All sublicenses to the Covered Code
- which are properly granted shall survive any termination of this
- License. Provisions which, by their nature, must remain in effect beyond the
- termination of this License shall survive.
-
-8.2 If You initiate litigation by asserting a patent infringement claim
- (excluding declatory judgment actions) against Initial Developer, Original
- Developer or a Contributor (the Initial Developer, Original Developer or
- Contributor against whom You file such action is referred to as "Participant")
- alleging that:
-
-(a) such Participant's Contributor Version directly or indirectly infringes any
-patent, then any and all rights granted by such Participant to You under
-Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from
-Participant terminate prospectively, unless if within 60 days after receipt of
-notice You either: (i) agree in writing to pay Participant a mutually agreeable
-reasonable royalty for Your past and future use of Modifications made by such
-Participant, or (ii) withdraw Your litigation claim with respect to the
-Contributor Version against such Participant. If within 60 days of notice, a
-reasonable royalty and payment arrangement are not mutually agreed upon in
-writing by the parties or the litigation claim is not withdrawn, the rights
-granted by Participant to You under Sections 2.1 and/or 2.2 automatically
-terminate at the expiration of the 60 day notice period specified above.
-
-(b) any software, hardware, or device, other than such Participant's Contributor
-Version, directly or indirectly infringes any patent, then any rights granted to
-You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective
-as of the date You first made, used, sold, distributed, or had made,
-Modifications made by that Participant.
-
-8.3 If You assert a patent infringement claim against Participant alleging that
- such Participant's Contributor Version directly or indirectly infringes any
- patent where such claim is resolved (such as by license or settlement) prior
- to the initiation of patent infringement litigation, then the reasonable value
- of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be
- taken into account in determining the amount or value of any payment or
- license.
-
-8.4 In the event of termination under Sections 8.1 or 8.2 above, all end user
- license agreements (excluding distributors and resellers) which have been
- validly granted by You or any distributor hereunder prior to termination shall
- survive termination.
-
-9. LIMITATION OF LIABILITY.
-
-UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING
-NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ORIGINAL
-DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY
-SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT,
-SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
-WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER
-FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN
-IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS
-LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL
-INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW
-PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR
-LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND
-LIMITATION MAY NOT APPLY TO YOU.
-
-10. U.S. GOVERNMENT END USERS.
-
-The Covered Code is a "commercial item," as that term is defined in 48
-C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and
-"commercial computer software documentation," as such terms are used in 48
-C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48
-C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users
-acquire Covered Code with only those rights set forth herein.
-
-11. MISCELLANEOUS.
-
-This License represents the complete agreement concerning subject matter
-hereof. If any provision of this License is held to be unenforceable, such
-provision shall be reformed only to the extent necessary to make it
-enforceable. This License shall be governed by California law provisions (except
-to the extent applicable law, if any, provides otherwise), excluding its
-conflict-of-law provisions. With respect to disputes in which at least one party
-is a citizen of, or an entity chartered or registered to do business in the
-United States of America, any litigation relating to this License shall be
-subject to the jurisdiction of the Federal Courts of the Northern District of
-California, with venue lying in Santa Clara County, California, with the losing
-party responsible for costs, including without limitation, court costs and
-reasonable attorneys' fees and expenses. The application of the United Nations
-Convention on Contracts for the International Sale of Goods is expressly
-excluded. Any law or regulation which provides that the language of a contract
-shall be construed against the drafter shall not apply to this License.
-
-12. RESPONSIBILITY FOR CLAIMS.
-
-As between Initial Developer, Original Developer and the Contributors, each
-party is responsible for claims and damages arising, directly or indirectly, out
-of its utilization of rights under this License and You agree to work with
-Initial Developer, Original Developer and Contributors to distribute such
-responsibility on an equitable basis. Nothing herein is intended or shall be
-deemed to constitute any admission of liability.
-
-13. MULTIPLE-LICENSED CODE.
-
-Initial Developer may designate portions of the Covered Code as
-Multiple-Licensed. Multiple-Licensed means that the Initial Developer permits
-you to utilize portions of the Covered Code under Your choice of the CPAL or the
-alternative licenses, if any, specified by the Initial Developer in the file
-described in Exhibit A.
-
-14. ADDITIONAL TERM: ATTRIBUTION
-
-(a) As a modest attribution to the organizer of the development of the Original
-Code ("Original Developer"), in the hope that its promotional value may help
-justify the time, money and effort invested in writing the Original Code, the
-Original Developer may include in Exhibit B ("Attribution Information") a
-requirement that each time an Executable and Source Code or a Larger Work is
-launched or initially run (which includes initiating a session), a prominent
-display of the Original Developer's Attribution Information (as defined below)
-must occur on the graphic user interface employed by the end user to access such
-Covered Code (which may include display on a splash screen), if any. The size of
-the graphic image should be consistent with the size of the other elements of
-the Attribution Information. If the access by the end user to the Executable and
-Source Code does not create a graphic user interface for access to the Covered
-Code, this obligation shall not apply. If the Original Code displays such
-Attribution Information in a particular form (such as in the form of a splash
-screen, notice at login, an "about" display, or dedicated attribution area on
-user interface screens), continued use of such form for that Attribution
-Information is one way of meeting this requirement for notice.
-
-(b) Attribution information may only include a copyright notice, a brief phrase,
-graphic image and a URL ("Attribution Information") and is subject to the
-Attribution Limits as defined below. For these purposes, prominent shall mean
-display for sufficient duration to give reasonable notice to the user of the
-identity of the Original Developer and that if You include Attribution
-Information or similar information for other parties, You must ensure that the
-Attribution Information for the Original Developer shall be no less prominent
-than such Attribution Information or similar information for the other
-party. For greater certainty, the Original Developer may choose to specify in
-Exhibit B below that the above attribution requirement only applies to an
-Executable and Source Code resulting from the Original Code or any Modification,
-but not a Larger Work. The intent is to provide for reasonably modest
-attribution, therefore the Original Developer cannot require that You display,
-at any time, more than the following information as Attribution Information: (a)
-a copyright notice including the name of the Original Developer; (b) a word or
-one phrase (not exceeding 10 words); (c) one graphic image provided by the
-Original Developer; and (d) a URL (collectively, the "Attribution Limits").
-
-(c) If Exhibit B does not include any Attribution Information, then there are no
-requirements for You to display any Attribution Information of the Original
-Developer.
-
-(d) You acknowledge that all trademarks, service marks and/or trade names
-contained within the Attribution Information distributed with the Covered Code
-are the exclusive property of their owners and may only be used with the
-permission of their owners, or under circumstances otherwise permitted by law or
-as expressly set out in this License.
-
-15. ADDITIONAL TERM: NETWORK USE.
-
-The term "External Deployment" means the use, distribution, or communication of
-the Original Code or Modifications in any way such that the Original Code or
-Modifications may be used by anyone other than You, whether those works are
-distributed or communicated to those persons or made available as an application
-intended for use over a network. As an express condition for the grants of
-license hereunder, You must treat any External Deployment by You of the Original
-Code or Modifications as a distribution under section 3.1 and make Source Code
-available under Section 3.2.
-
-EXHIBIT A. Common Public Attribution License Version 1.0.
-
-"The contents of this file are subject to the Common Public Attribution License
-Version 1.0. (the "License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-http://getmoai.com/license. The License is based on the Mozilla Public
-License Version 1.1, but Sections 14 and 15 have been added to cover use of
-software over a computer network and provide for limited attribution for the
-Original Developer. In addition, Exhibit A has been modified to be consistent
-with Exhibit B.
-
-Software distributed under the License is distributed on an "AS IS" basis,
-WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the
-specific language governing rights and limitations under the License.
-
-The Original Code is Moai SDK
-
-The Original Developer is the Initial Developer. The Initial Developer of the
-Original Code is Zipline Games, Inc.
-
-All portions of the code written by Zipline Games are Copyright (c) 2010-2011
-Zipline Games, Inc. All Rights Reserved.
-
-EXHIBIT B. Attribution Information
-
-Subject to the limitations and other requirements in Section 14 of the
-License, the Original Developer requires You to display the following
-Attribution Information:
-
-Attribution Phrase: Made with Moai
-
-Attribution URL: http://getmoai.com
-
-Graphic Image as provided in the Covered Code:
-http://getmoai.com/moailogo.png
-
-Attribution Copyright Notice: Copyright (c) 2010-2011 Zipline Games, Inc. All Rights Reserved.
-
-An Alternative Image incorporating all four attributions is available at http://getmoai.com/madewithmoai
-
-This display should include, at a minimum, listing the Attribution Phrase, Attribution URL,
-Graphic Image and Attribution Copyright Notice in a credits screen, or alternatively
-the Alternative Image displayed in a splash screen for a minimum of two seconds.
-
-Display of Attribution Information is required in Larger Works which are
-defined in the CPAL as a work which combines Covered Code or portions
-thereof with code not governed by the terms of the CPAL.
View
7 distribute/doxygen/.gitignore
@@ -1,7 +0,0 @@
-html-lua/
-src-copy/
-*.lnk
-input.cpp
-output.cpp
-input.h
-output.h
View
8 distribute/doxygen/README.txt
@@ -1,8 +0,0 @@
-This file explains how to generate the HTML documentation for the Moai SDK from source. This is useful if you've made changes to Moai's C++ source code and would like an updated Lua class reference.
-
-Windows
-- Install Perl (ActivePerl is available for Windows).
-- Install Graphviz. Doxygen uses Graphviz to create the class diagrams.
-- Install Doxygen.
-- Make sure your PATH environment variable contains the bin directories of Perl, Graphviz, and Doxygen.
-- Run make-docs-lua.bat
View
1,541 distribute/doxygen/doxyfile-full
@@ -1,1541 +0,0 @@
-# Doxyfile 1.5.8
-
-# 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 = Moai
-
-# 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.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 = html-full
-
-# 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 = YES
-
-# 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, 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, 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 = NO
-
-# 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 = NO
-
-# 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 = NO
-
-# 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 = NO
-
-# 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 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 = 4
-
-# 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
-
-# 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
-
-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
-# 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 = YES
-
-# 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
-
-# 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
-
-# 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
-
-#---------------------------------------------------------------------------
-# 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 = YES
-
-# 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 = NO
-
-# 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 = NO
-
-# 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 = NO
-
-# 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 = 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
-
-# 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 = NO
-
-# 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
-
-# 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
-
-# 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 =
-
-# 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 =
-
-#---------------------------------------------------------------------------
-# 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 = NO
-
-# 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 = "../src/"
-
-# 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 *.f90
-
-FILE_PATTERNS = *.c \
- *.cc \
- *.cxx \
- *.cpp \
- *.c++ \
- *.d \
- *.java \
- *.ii \
- *.ixx \
- *.ipp \
- *.i++ \
- *.inl \
- *.h \
- *.hh \
- *.hxx \
- *.hpp \
- *.h++ \
- *.idl \
- *.odl \
- *.cs \
- *.php \
- *.php3 \
- *.inc \
- *.m \
- *.mm \
- *.dox \
- *.py \
- *.f90 \
- *.f \
- *.vhd \
- *.vhdl
-
-# 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 =
-
-# 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 =
-
-# 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.
-
-SOURCE_BROWSER = YES
-
-# 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
-# then for each documented function all documented
-# functions referencing it will be listed.
-
-REFERENCED_BY_RELATION = NO
-
-# If the REFERENCES_RELATION tag is set to YES
-# then for each documented function all documented entities
-# called/used by that function will be listed.
-
-REFERENCES_RELATION = NO
-
-# 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.
-
-REFERENCES_LINK_SOURCE = YES
-
-# 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 =
-
-# 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 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 = YES
-
-# 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
-
-# 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 compiled HTML help file (.chm)
-# of the generated HTML documentation.
-
-GENERATE_HTMLHELP = 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 CHM_INDEX_ENCODING
-# is used to encode HtmlHelp index (hhk), content (hhc) and project file
-# content.
-
-CHM_INDEX_ENCODING =
-
-# 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 = NO
-
-# 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 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
-
-# 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
-# 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. 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.
-
-GENERATE_TREEVIEW = ALL
-
-# 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
-
-# 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
-
-#---------------------------------------------------------------------------
-# 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 = a4wide
-
-# 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 = NO
-
-# 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 = USE_BOX2D USE_CHIPMUNK USE_FMOD USE_FREETYPE
-
-# 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 = YES
-
-#---------------------------------------------------------------------------
-# 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 =
-
-# 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 = YES
-
-# 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 = YES
-
-# 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
-
-# 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 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 = YES
-
-# 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 = YES
-
-# 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 = NO
-
-# 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 = NO
-
-# 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.
-
-CALL_GRAPH = YES
-
-# 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.
-
-CALLER_GRAPH = YES
-
-# 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 = NO
-
-# 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 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
-
-# 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 = 0
-
-# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
-# 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).
-
-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
-
-#---------------------------------------------------------------------------
-# Options 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
View
1,541 distribute/doxygen/doxyfile-lua
@@ -1,1541 +0,0 @@
-# Doxyfile 1.5.8
-
-# 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 = "Moai SDK"
-
-# 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 = @@VERSION@@
-
-# 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 = html-lua
-
-# 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, 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, 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 = NO
-
-# 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 = NO
-