Version 40 by Bart Kamphorst
on Jan 14, 2011 20:19.

<< Changes from 39 to 40
compared with
Current by Bart Kamphorst
on Jan 14, 2011 20:31.

 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 h2. Introduction
  
 Use the following links to navigate through the tutorial. If you are a beginner, we advise you to start from "Section 1: What CT is" and linearly advance forward. More experienced users may directly go to their topic of interest.
  
 h1. Index
  
 h2. Section 1: Introduction
  
 h4. 1.1. [Who needs Colored Trails|coloredtrailshome:Who needs Colored Trails|Who needs Colored Trails]
  
 h4. 1.2. [Technologies used by CT|coloredtrailshome:Technologies used by CT|Technologies used by CT]
  
 h4. 1.3 [Who develops CT?|coloredtrailshome:CT development|Who develops CT?]
  
 h2. Section 2: Getting started
  
 h4. 2.1 [IDE configuration|coloredtrailshome:IDE Configuration]
  
  
 h4. 2.2 [Launching CT from command line|coloredtrailshome:LaunchCommandLine]
  
  
 h2. Section 3: CT architecture
  
  
 h4. 3.1. [The client, the server and the controller|The client, the server and the controller]
  
  
 h4. 3.2. [Making it easy: the configuration file|coloredtrailshome:The configuration class|The CT configuration class]
  
  
 h4. 3.3. [Exchanging messages|coloredtrailshome:Exchanging messages|Exchanging messages]
  
  
 h2. Section 4: Configuring CT
  
  
 h4. 4.1. Structure of the configuration file
  
  
 h4. 4.2. [Using the controller]
  
 h5. 4.2.1. [Handling command-line arguments in the controller|Handling command-line arguments in the controller]
  
  
 h4. 4.3. Putting it all together: a simple example
  
  
 h4. 4.4. [Human and computer clients]
  
 h4. 4.5. [Passing arguments to the configuration class]
  
 h2. Section 5: Deep into CT
  
  
 h4. 5.1. Elements of the server
  
  
 h5. 5.1.1. The game status class
  
  
 h5. 5.1.2. Create your own functionality: communication
  
  
 h4. 5.2. Elements of the UI
  
  
 h5. 5.2.1. [Board|The Board|Elements of the UI: the Board]
  
 h5. 5.2.2. Transfer window
  
 h5. 5.2.3. Proposal window
  
 h5. 5.2.4. Moving
  
  
 h5. 5.2.5. Find your way: the path finder
  
  
 h5. 5.2.6. Hide it: partial visibility
  
  
 h5. 5.2.7. Do what you want: arbitrary messages
  
  
 h5. 5.2.8. [Waiting for clients to complete an action|Waiting for clients to complete an action]
  
  
 h4. 5.3. [The CT API|http://viki.eecs.harvard.edu/ct/javadoc|The CT API]
  
  
 h2. Section 6: Logging
  
  
 h4. 6.1. [Logging the server output with Log4J|coloredtrailshome:Log4J logging|Log4J logging]
  
  
 h4. 6.2. [Logging experimental data|coloredtrailshome:Logging experimental data|Logging experimental data]
  
  
 h5. 6.2.1. [Logging to stdout|coloredtrailshome:Logging to stdout|Logging to stdout]
  
  
 h5. 6.2.2. [Logging to MySQL with ExperimentLogger]
  
 h2. Section 7: Testing
  
 h4. 7.1. [Unit testing with JUnit|coloredtrailshome:Unit testing with JUnit]
  
 h2. Section 8: Internationalization
  
 h4. 8.1. [Getting started with internationalization]
  
 h2. Section 9: Extensions
  
 h4. 9.1. [Colored Trails and BDI: CTAPL|coloredtrailshome:Colored Trails and BDI (CTAPL)|Colored Trails and BDI: CTAPL]
  
 h4. 9.2. [coloredtrailshome:Integrating WEKA Classifiers]
  
 h2. Section 10: Troubleshooting
  
  h4. 10.1. [Client cannot connect to server / Connection refused|coloredtrailshome:Connection Refused]
  
 h2. Section 11: Conclusions