99f8cba35f
* Updated config doc comments. * Check undefined without typeof. Discussion: https://stackoverflow.com/a/22053469/187883 * Use transparent bg color by default if alpha is true. * Set bg color on parent to avoid flash. * render->create (so it doesn't seem like it's about drawing). * Sorted members. * Use addEventListener, else only the last player event handler is used. * Set the initial animation when loaded, not whenever track 0 is empty. * If an animation is not specified, play an empty animation. * If an animation is set in success(), don't set any animation. * Don't clearTracks in setAnimation, don't use AnimationState in calculateAnimationViewport -- those prevent mixing. * setAnimation returns the TrackEntry. * Added addAnimation and setViewport. * Expose play() and pause(). * Keep control bones inside the canvas. * LoadingScreen scales down. * Set minimal CSS so no external CSS is needed when !showControls. * Use screen instead of world coordinates for control bone hit detection, so it works at any size. * Choose closest control bone instead of last.
Spine Runtimes
This GitHub project hosts the Spine Runtimes which are needed to use Spine 2D skeletal animation data with various game toolkits.
Licensing
You are welcome to evaluate the Spine Runtimes and the examples we provide in this repository free of charge.
You can integrate the Spine Runtimes into your software free of charge, but users of your software must have their own Spine license. Please make your users aware of this requirement! This option is often chosen by those making development tools, such as an SDK, game toolkit, or software library.
In order to distribute your software containing the Spine Runtimes to others that don't have a Spine license, you need a Spine license at the time of integration. Then you can distribute your software containing the Spine Runtimes however you like, provided others don't modify it or use it to create new software. If others want to do that, they'll need their own Spine license.
For the official legal terms governing the Spine Runtimes, please read the Spine Runtimes License Agreement and Section 2 of the Spine Editor License Agreement.
Documentation
See the Spine Runtimes Guide for detailed information about using the Spine Runtimes. The Spine documentation page provides further information about tools and data formats. For runtime specific documentation, refer to the README.md file in each runtime directory.
Bugs, enhancements, and tasks
Review our backlog of bugs, enhancements, and tasks in the spine-runtimes and spine-editor issue trackers. Our roadmap provides a more convenient view of the same issue tracker information.
Versioning
The default branch on GitHub is stable and works with data exported from the latest, non-beta version of the Spine editor. New development is done in an X.X-beta branch, which may be a work in progress. Important changes to the runtimes can be reviewed in the CHANGELOG.md file. Occasionally the Spine Runtimes are tagged with the specific Spine editor version they work with.
It is highly suggested to freeze the Spine editor version to match the Spine Runtimes source being used and to update them in lock step. See the Spine Runtimes Guide for more information.
Contributing
In order to merge your contributions, we need a signed contributor license agreement (CLA) from you. You can send a copy of the CLA to contact@esotericsoftware.com.
When possible, it is best to base your contributions on the current beta branch (X.X-beta). Please be sure to follow the style and formatting you find in the respective runtime code to which you are contributing.