New issue 152 by taroleo: Type-safe configuration objects for tracks
http://code.google.com/p/utgb/issues/detail?id=152
Please describe a summary of the new feature (in a paragraph):
The current track implementation uses properties for configuring options of
tracks. However, property-based implementation has several drawbacks. For
example, we cannot detect spelling errors in the configurations, type
errors (e.g., int or string? ), etc. Finding these human errors in
using/debugging UTGB is difficult.
To improve this, each track should provide a configuration object (class),
which can be serialized into Silk, and also can be deserialized from Silk.
Please provide any additional information below: