Complete JsonImplementation

[Cataract92]

There're two problems right now:

1. If we put a Visual in the VisualC the .json file gets huge, because basicly the whole model gets stored in there. And to deserialize every object needs a non-parameter Constructor, which is impossible if we use 3rd party stuff. To pass this problem i gave the VisualC a string instead of a visual and it should generate a Visual once created and store itself in the Visual.visualcs. There comes the second problem...
2. Because the visual has to create his visual itself based on the modeltype-string, i had to impelemt an Init()-function which gets called after the deserialize, because while deserialize (on constructor-call) i don't have the modeltype yet. (In deserialzisation the fields get their values AFTER making the new instance of the object).

But now we have a function in the component. Which you wanted to get rid of in the first place.
So do you allow one Init()-function in some components or do you want to make some kind of Info-class again? Which i don't want.

[Cataract92]

Changed! Now every component needs at least 2 Constructors: One without any parameters which gets called after deserialization (read in EntitiyBlueprint). This one doesn't necessary needs to have any initialization, because the real initialisation happens on creating a entity. And another one with a component of its own type as a parameter, which gets called while creating an entity based on the blueprint. This constructor should copy all necessary informations.