Serialization

[Cleptomania]

A big part of the re-work for 2.0 was separating parsing from the API definition. This is what enabled support for TMX to come in 2.0, but also was the foundation for being able to save maps.

This isn’t a super straight forward process, as we do a lot of normalizing/converting of data as it’s loaded in, so it’s not quite as simple as “just dump the JSON back to a file”, especially when it comes to the TMX format.

We basically need to reverse the parsing process in order to do this. The goal for 2.1 is to have this for the JSON, with ability to save TMX/TSX likely to follow in a 2.2 release, however depending on how this turns out we could see both in 2.1.

If all of the other desired features are good and JSON serialization is done then we’ll probably save TMX serialization for 2.2, as that process is definitely going to be a bit more involved than JSON.

[Cleptomania]

This is now targeting version 2.4. It will likely take priority after the work on classes and custom property types, which is intended to be the focus of 2.3