Added new WIP content data types to the solution in a separate project.

Each content data type is defined in an XML schema (.xsd) which describes the structure and basic data types used in the content data type. Another XML schema defines the structure of the content XML files.

Apart from the XML schemas, each content data type is also represented by a C# class. Each class is implemented as a partial class in two separate files. One of these bears the class name, and contains hand-coded methods and properties not involved in the serialization of the content files. The other file is common to all the content types, and contains the auto-generated serializable C# representation of the XML content formats. This division of the different class parts ensures that new serializable classes can be auto-generated without affecting the manually implemented methods used in the classes.

None of the new content data types are used by the engine yet.
Added everything needed to auto-generate serializable C# classes from XML schemas. This is an integral part of the new design paradigm for the DeuterosX content data file formats.

This is not a project, just a folder, but I chose to place it inside the solution file structure anyway, since it will be used for implementing code for the solution.

Please read the Readme.txt file before using the contents of the folder.
Added a content file editor tool for the new content data types.

The tool is very much a work in progress, and will need to be expanded as new content data types are introduced. I realize I am not a very good GUI designer, so anyone who feels they can improve the user interface are welcome to do so. Still, the tool is usable in its current form, and does make quick work of generating content files. A new animation will typically only take a couple of minutes to make, provided that the needed graphics are available.

Be aware that the logic of the new content data types requires that all graphics are henceforth stored in tile sets.