This is a breaking change for direct implementers of AppState as they must
add a getId() method. (Which is also a good time to evaluate if they should
be extending AbstractAppState or BaseAppState and/or if their life cycle is
implemented correctly. e.g.: BulletAppState is breaking the AppState contract
a bit.)
* First attempt at building android-natives.
* Use OpenJDK because native build is broken without
* Try OpenJDK 10
* Try openJDK 9
* Try openJDK11 again but "enable" the EE Module
* OpenJDK 11 has no Java EE Module anymore.
* Try to fix Android Header Generation
* Fix invalid flag error with javac by removing empty quotes
* Try to fix build of decode.
* Remove jni generated headers from the repository.
* Adjust .gitignore as those header files won't appear at that location anymore
* Fix Android Build: Fill the jme3-android-native headers during the build of jme3-android. This works because jme3-android-native already depends on jme3-android.
Due to technical reasons, the headers share the same location and thus the include directives have been adjusted slightly.
* Copy jni headers to the jni directory.
* Adjust the path slightly
* Try to silence android sdk's license print out
* Also fix openAL
* Solve task name conflict
* Really silence license now
* Tasks seem shared but Strings are not...
* Only build Android-Native
* Trying to reduce the amount of dependencies needed.
* Remove even more dependencies
* Even more removal
* Prepare Deployment
* Fix Deployment
* Cleanup: Remove feature branch from branches for travis.
* Revert a few unnecessary things
* Removed NDK Comments.
in that it delays serialization until the message is requested. This should
fix the issue where the initial server messages would sometimes fail to
deserialize because the serialization registration message hadn't been processed
before the other messages in the block were deserialized. Now each message will
be deserialized as it is encountered.
In the end the fix was simple enough that it's probably only a 2-3 line change to
MessageProtocol in JME 3.2 if someone wants to back port the fix. (Just queue
up ByteBuffer instead of Message.)
interface and strictly implement the to/from ByteBuffer protocol. In the future
this will allow the message protocol to be swappable. Also moved out the buffering
aspect since often buffers need to be created 'on the fly' and are separate from
the protocol. This will allow me to play with fixing the issue related to messages
being deserialized before the serialization registry message has been processed by
swapping out the GreedyMessageBuffer implementation for a LazyMessageBuffer implementation.
* Updated CONTRIBUTING.md
Added "Customs around integration, branching, tagging, and releases" section to contribution guide.
* Clarify that the admonition to squash PRs is directed at integrators
* Add support for gltf morph names.
* Fix formatting stuff
* Add morph name to be saved
* Testing changes to gltf plugin
* Review changes
* Fix comments
* Fixes for review
* Remove getMorphNames from Geometry class
* jme-core: IndexBuffer fixes & API improvements
As discussed in:
https://hub.jmonkeyengine.org/t/indexbuffer-suggestions-improvements-consistency/42022/4
* [Fix] createIndexBuffer(int, int): return IndexByteBuffer as well for
vertexCount < 128
* [Enhancement] Make put(int i, int value) fluid interface
* [Enhancement] Add relative put(int i) to allow easier chaining (parity
with other buffer implementations)
* [Enhancement] Add getFormat() to allow setting an IndexBuffer to a
Mesh directly without type inspection.
* [Fix] Fix WrappedIndexBuffer
API changes make it possible that IndexByteBuffer is now a valid type
for outBuf, leverage the new getFormat() method to set the buffer to the
mesh regardless of its type.
* Update VirtualIndexBuffer to @72f8019566fa4d1379caa820c0c9dc000f489444
* #1121-updateBound() call for PQTorus geometry updates
* World bounds test added for #1121
* World bounds test enhancements for #1121
* Updated test comment
Previously if particlesPerSec was constantly set timeDifference could never grow large enough to emit a particle as timeDifference was reset to zero each time. This fixes that problem while still ensuring that timeDifference can't have grown very very large (leading to huge numbers of particles being emitted) by capping the timeDifference at the point where its just about to emit a particle.
Discussed at https://hub.jmonkeyengine.org/t/particle-emitter-cannot-emit-particles-if-its-emissions-per-second-is-updated-every-frame/41930/2
