Ed Kolis
Ed Kolis
I think we need the concept of a reference to an object that doesn't actually exist, but the reference itself can still exist.
I wonder if the new C# generic attributes will let stringifiers handle generic types?
Wait, aren't there times we do want to store a real object, like a design when it's being created?
I suppose those could be marked with a special attribute. That would also prevent unexpected objects from being inserted into the game state!
As it turns out, I was able to do this using GameReference and ModReference attributes hooked into the serializer rather than stringifiers. These changes will be included with the changes...
Actually, this didn't quite work out; there is a need for a two step deserialization process where first all the objects are instantiated, and then they are all linked together...
Perhaps it's time to create some proper view models, rather than just using the models themselves for that purpose. That way the models could contain the IDs only and the...
#292 is the view model issue
View models are linked to a specific view. They're not necessarily linked to a specific model; a view model could contain data from zero, one, or many models.
Really the reference properties should go in a data model, and then the actual properties would go in the domain model, and computed properties would go in the domain model...