Serializer and Serializable #102

New issue

Closed

opened 2021-04-30 09:26:49 +02:00 by kazhnuz · 0 comments

kazhnuz commented

2021-04-30 09:26:49 +02:00

Owner

The following parent class could be that:

The Serializable class would be able to know it's serialized field (it would be a simple list of string). The getData functions would go in all the serializedFields list and return a table with all those fields, and if a field is a Serializable, it would return its getData. The setData would put data from a table in all those fields.
The Serialize would be a Serializable, that also contain a serialize and deserialize variables, that would simply put handle using binser to put data into a file.

This would cleanup a LOT of our code, and simplify a lot data saving. Metadata could be handled by a second serializer, that would read data from the game class and serialize/deserialize iteself each time the class save.

For the moment, serialized files (gamesave, options and metadata) are handled by specific class using binser. It would be simpler to create parent class that would handle that, especially as with time we will add more options and feature to the game. The following parent class could be that: - The Serializable class would be able to know it's serialized field (it would be a simple list of string). The getData functions would go in all the serializedFields list and return a table with all those fields, and if a field is a Serializable, it would return its getData. The setData would put data from a table in all those fields. - The Serialize would be a Serializable, that also contain a serialize and deserialize variables, that would simply put handle using binser to put data into a file. This would cleanup a LOT of our code, and simplify a lot data saving. Metadata could be handled by a second serializer, that would read data from the game class and serialize/deserialize iteself each time the class save.