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.

Index

Section 1: General

1.1. Who needs Colored Trails

1.2. Technologies used by CT

1.3 Who develops CT?

1.4 IDE configuration

1.5 Launching CT from command line

Section 2: CT architecture

2.1. The client, the server and the controller

2.2. Making it easy: the configuration file

2.3. Exchanging messages

Section 3: Configuring CT

3.1. Structure of the configuration file

3.2. Using the controller

3.2.1. Handling command-line arguments in the controller

3.3. Putting it all together: a simple example

3.4. Human and computer clients

3.5. Passing arguments to the configuration class

Section 4: Deep into CT

4.1. Elements of the server

4.1.1. The game status class

4.1.2. Create your own functionality: communication

4.2. Elements of the UI

4.2.1. Board

4.2.2. Transfer window

4.2.3. Proposal window

4.2.4. Moving

4.2.5. Find your way: the path finder

4.2.6. Hide it: partial visibility

4.2.7. Do what you want: arbitrary messages

4.2.8. Waiting for clients to complete an action

4.3. The CT API

Section 5: Logging

5.1. Logging the server output with Log4J

5.2. Logging experimental data

5.2.1. Logging to stdout

5.2.2. Logging to MySQL with ExperimentLogger

Section 6: Testing

6.1. Unit testing with JUnit

Section 7: Internationalization

7.1: Getting started with internationalization

Section 8: Extensions

8.1 Colored Trails and BDI: CTAPL

8.2 Integrating WEKA Classifiers

Section 9: Troubleshooting

Section 10: Conclusions