Data format change and Critical Fixes

So, as it turned out my little sexpr syntax used for value notation Nu's serialization format was not usable beyond its intended purpose. That was fine, until it wasn't.

Since I found out it's just going to be too difficult to write an importer for an existing animation package, and not likely very usable, I decided to use said syntax to enable encoding effects in the upcoming Effect system.

What I found out very quickly, however, was that the syntax was too hard to use for this purpose.

So rather than adding an additional syntax (and make everyone's lives worse forever), I decided to fix up the existing syntax. So now instead of specifying a collision expression like this -

[PolygonShape | [0, 0 | 5, 5 | 0, 5] | 0, 0]]

we do the following -

[BodyPolygon [[0 0] [5 5] [0 5]] [0 0]]

• which removes the | that are, in most cases, lexically redundant.

Also, you'll notice that the name of the physic body shape types have changed.

So, if you've got a lot of data, you're going to have to convert it in order to get it to work with the new system. Fortunately, the conversion process is straight-forward. But because this is a data-breaking change, I've ticked the minor version number.

Additionally, there were some critical bug fixes.

Here are the changes in detail -

Fixed AddressConverter bug. … 7c06d21
Started working on Effect system. f345bfd
Fixing notation usage. 16f66e7
Converted IRPG to new notation. b993e8b
Updated documentation. 7d5d6db
Now again working on Effect system. 948492c
Added Nu.init invokation manually. 27589a3
Fixed serious MutantCache bug! X/ 4b225f6