<doxygenlayout version="1.0">
  <!-- Generated by doxygen 1.8.3.1 -->
  <!-- Navigation index tabs for HTML output -->
  <navindex>
    <tab type="mainpage" visible="yes" title=""/>
    <tab type="pages" visible="yes" title="" intro=""/>
    <tab type="modules" visible="yes" title="" intro=""/>
	<!-- T2D: we are hiding the "real" Namespaces tab.  See notes in our "fake" Namespaces tab below.
	     If we could, we'd rename the concept of "Namespace" to "Functions" to get what we want.
		 Instead we have simply made invisible all namespace-related tabs so they won't show
		 in any cross-references.
	-->
    <tab type="namespaces" visible="no" title="Namespaces">
      <tab type="namespacelist" visible="no" title="Functions by Category" intro="A list of all functions organized by category"/>
      <tab type="namespacemembers" visible="no" title="All Function" intro="A list of all functions from all categories"/>
    </tab>
	<!-- We are making a global functions page.  Global functions are actually functions
		 in the pseudo-namespace "Functions".
	-->
	<tab type="user" title="Functions" url="namespaceFunctions.html"/>
	<!-- T2D: we are hiding the "real" Classes tab.  See notes in our "fake" Classes tab below -->
    <tab type="classes" visible="no" title="">
      <tab type="classindex" visible="$ALPHABETICAL_INDEX" title="Classes A-Z"/>
      <tab type="hierarchy" visible="yes" title="Classes Hierarchy"/>
      <tab type="classlist" visible="no" title="" intro=""/>
      <tab type="classmembers" visible="no" title="" intro=""/>
    </tab>
	<!-- T2D: note that we made invisible the *real* "Classes" tab and then made our own.
	     The reason is that the real Classes tab defaults to the "Class List" sub tab, which
		 we don't want (more below).
		 So why not just turn off the "classlist" tab so it doesn't show by default?  Tried it, but
		 doxygen shows that tab by default anyway.  Even though it is "invisible" in the index.
		 
		 Why do we want to hide the class list tab anyway?  It shows classes within namespaces.
		 Since we are using namespaces to hide our TorqueScript classes/functions from the related
		 Torque2D classes/functions (using namespaces "Functions" and "Class"), this list of classes
		 in namespaces looked confusing.
	-->
	<tab type="usergroup" title="Classes">
		<tab type="user" url="classes.html" title="Classes A-Z"/>
		<tab type="user" url="hierarchy.html" title="Classes Hierarchy"/>		
    </tab>		
    <tab type="files" visible="yes" title="">
      <tab type="filelist" visible="yes" title="" intro=""/>
      <tab type="globals" visible="yes" title="" intro=""/>
    </tab>
    <tab type="examples" visible="yes" title="" intro=""/>  
  </navindex>

  <!-- Layout definition for a class page -->
  <class>
    <briefdescription visible="yes"/>
    <includes visible="$SHOW_INCLUDE_FILES"/>
    <inheritancegraph visible="$CLASS_GRAPH"/>
    <collaborationgraph visible="$COLLABORATION_GRAPH"/>
    <memberdecl>
      <nestedclasses visible="yes" title=""/>
      <publictypes title=""/>
      <publicslots title=""/>
      <signals title=""/>
	  <!-- T2D: rename "Public Methods Function" to be just "Methods" for TorqueScript -->
      <publicmethods title="Methods"/>
      <publicstaticmethods title=""/>
	  <!-- T2D: rename "Public Attributes" to be just "Fields" for TorqueScript -->
      <publicattributes title="Fields"/>
      <publicstaticattributes title=""/>
      <protectedtypes title=""/>
      <protectedslots title=""/>
      <protectedmethods title=""/>
      <protectedstaticmethods title=""/>
      <protectedattributes title=""/>
      <protectedstaticattributes title=""/>
      <packagetypes title=""/>
      <packagemethods title=""/>
      <packagestaticmethods title=""/>
      <packageattributes title=""/>
      <packagestaticattributes title=""/>
      <properties title=""/>
      <events title=""/>
      <privatetypes title=""/>
      <privateslots title=""/>
      <privatemethods title=""/>
      <privatestaticmethods title=""/>
      <privateattributes title=""/>
      <privatestaticattributes title=""/>
      <friends title=""/>
      <related title="" subtitle=""/>
      <membergroups visible="yes"/>
    </memberdecl>
    <detaileddescription title=""/>
    <memberdef>
      <inlineclasses title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <constructors title=""/>
	  <!-- T2D: rename "Public Method Functions" to be just "Methods" for TorqueScript -->
      <functions title="Methods"/>
      <related title=""/>
      <variables title=""/>
      <properties title=""/>
      <events title=""/>
    </memberdef>
    <allmemberslink visible="yes"/>
    <usedfiles visible="$SHOW_USED_FILES"/>
    <authorsection visible="yes"/>
  </class>

  <!-- Layout definition for a namespace page -->
  <!-- T2D: we will make namespaces look like "function categories" which
       hold sets of global TorqueScript functions.  This is simply a hack.
  -->
  <namespace>
    <briefdescription visible="yes"/>
    <memberdecl>
      <nestednamespaces visible="yes" title="Function Categories"/>
      <classes visible="yes" title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <functions title=""/>
      <variables title=""/>
      <membergroups visible="yes"/>
    </memberdecl>
    <detaileddescription title=""/>
    <memberdef>
      <inlineclasses title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <functions title=""/>
      <variables title=""/>
    </memberdef>
    <authorsection visible="yes"/>
  </namespace>

  <!-- Layout definition for a file page -->
  <file>
    <briefdescription visible="yes"/>
    <includes visible="$SHOW_INCLUDE_FILES"/>
    <includegraph visible="$INCLUDE_GRAPH"/>
    <includedbygraph visible="$INCLUDED_BY_GRAPH"/>
    <sourcelink visible="yes"/>
    <memberdecl>
      <classes visible="yes" title=""/>
      <namespaces visible="yes" title=""/>
      <defines title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <functions title=""/>
      <variables title=""/>
      <membergroups visible="yes"/>
    </memberdecl>
    <detaileddescription title=""/>
    <memberdef>
      <inlineclasses title=""/>
      <defines title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <functions title=""/>
      <variables title=""/>
    </memberdef>
    <authorsection/>
  </file>

  <!-- Layout definition for a group page -->
  <group>
    <briefdescription visible="yes"/>
    <groupgraph visible="$GROUP_GRAPHS"/>
    <memberdecl>
      <nestedgroups visible="yes" title=""/>
      <dirs visible="yes" title=""/>
      <files visible="yes" title=""/>
      <namespaces visible="yes" title=""/>
      <classes visible="yes" title=""/>
      <defines title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <enumvalues title=""/>
      <functions title=""/>
      <variables title=""/>
      <signals title=""/>
      <publicslots title=""/>
      <protectedslots title=""/>
      <privateslots title=""/>
      <events title=""/>
      <properties title=""/>
      <friends title=""/>
      <membergroups visible="yes"/>
    </memberdecl>
    <detaileddescription title=""/>
    <memberdef>
      <pagedocs/>
      <inlineclasses title=""/>
      <defines title=""/>
      <typedefs title=""/>
      <enums title=""/>
      <enumvalues title=""/>
      <functions title=""/>
      <variables title=""/>
      <signals title=""/>
      <publicslots title=""/>
      <protectedslots title=""/>
      <privateslots title=""/>
      <events title=""/>
      <properties title=""/>
      <friends title=""/>
    </memberdef>
    <authorsection visible="yes"/>
  </group>

  <!-- Layout definition for a directory page -->
  <directory>
    <briefdescription visible="yes"/>
    <directorygraph visible="yes"/>
    <memberdecl>
      <dirs visible="yes"/>
      <files visible="yes"/>
    </memberdecl>
    <detaileddescription title=""/>
  </directory>
</doxygenlayout>
