-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation for CachedMeshContent #105
Conversation
- Uses default Json instance now and moves custom serializer to Texture class. - All getters for cached content are synchronized. - Renamed classes to be consistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I've made a few minor changes (some of which are not directly related to the PR).
Most importantly: You should minimize the number of custom Json { }
serializer objects. In your implementation, every instance of CachedModel3dContent
used its own instance, which can be a performance hit.
I have one final request: I would like to see a unit test that makes sure that serialization and deserialization works as expected. Test would look as follows:
- Load toy model
- Serializer
Model3d
- De-serialize
Model3d
- Check of two instances are identical.
If it simplifies things, the unit test can be added to the m3d
module.
I have now added two unit tests to the m3d module.
|
Merged! Thank you :-) |
This pull request implements the CachedMeshContent and solves issue #97.