Hello, since I wasn't able to find much info on savable I'm gonna ask this. I'm currently using serializable to save data in my game such as maps and monsters.
Should all these be changed into savable or is savable only meant to be used to save models?
PS. Now that I written this, the question sounds a little bit dumb.
Chemfy said:
Hello, since I wasn't able to find much info on savable I'm gonna ask this. I'm currently using serializable to save data in my game such as maps and monsters.
Should all these be changed into savable or is savable only meant to be used to save models?
PS. Now that I written this, the question sounds a little bit dumb.
It doesn't really matter. The Savable system is supposed to be more efficient than java's serialization, but of course it is also more cumbersome because you must define the save/load methods. I have used the Savable system successfully for various non-model data so it works fine for non-models as well. :)
I did wonder in the past why the Externalizable interface wasn't used (not that it makes much difference really - just semantics)