Just uploaded a new version of Zay-ES along with a brand-spanking-new Zay-ES-Net extension library.
Both releases have accompanying javadoc. The new network layer has been through limited testing but it would surprise me greatly if there aren’t still bugs lurking in there.
Changelog for Zay-ES core:
Removed the direct DefaultEntityData reference from DefaultEntity
Removed the direct reference to DefaultEntityData from DefaultEntitySet.
Added a protected isReleased() method to DefaultEntitySet so subclasses
can check released state.
Added a protected method for accessing the change queue.
Added a method to DefaultEntitySet.Transaction for directly injecting
added entities. (Useful for when entities are loaded asynchronously.)
Added an internal optimization to DefaultEntitySet that avoids attempting
to re-retrieve a component that was removed.
Added a protected registerComponentHandler() method to DefaultEntityData
so that subclasses can customimze component handler implementations.
Removed the SpiderMonkey dependency from core Zay-ES
Just uploaded a new release of Zay-ES.jar and its javadocs. Nothing really changed except formatting which will throw line numbers off in stack traces so I thought I’d post a new version.
Changes:
Reformatted source code to be closer to normal Java coding conventions.
Added some Javadoc here and there.
Removed unused methods update() and clear() from DefaultEntity
Just uploaded a new release of Zay-ES-Net with some bug fixes.
Changes:
Modified RemoteEntityData.RemoteEntitySet.release() to check
to see if the connection is still connected before sending
the release message.
Fixed a bug where really eager sendUpdate() calls were causing
thread contention with entity set creation. This would be
especially true for large sets and short update cycles.
Fixed a similar future-bug for resetting the filter, too,
though that one would be much harder to time just right, ie:
even more bizarre if seen in the wild.
Yeah, I need to improve the docs on the main zay-es site with some of my own. The docs linked above were written by the community and are nice but it would be nice to have something official and homed closer to the code.