Blender files can have armature such as circles, cubes, cylinders, a dragon or any other 3D shape.
A armature can be represented as a group of vertices and data about those vertices, such as their normals or UV coordinates.
Armaturees can also have metadata, such as the name of it's parent armature (useful for vertex skinning).
blender-armature-to-json seeks to be a well tested, well documented exporter for blender armature metadata.
You can write data to stdout or to a file. At the onset it will be geared towards @chinedufn's needs - but if you have needs that aren't met feel very free to open an issue.
@see https://docs.blender.org/manual/en/dev/modeling/armature/introduction.html - Armature Introduction @see https://github.com/chinedufn/blender-actions-to-json - Exporting blender armatures / actions
Settings for your armature's current action and (optionally) it's previous action.
All of the data about a Blender armature that we've exported from Blender. A BlenderArmature should have all of the data that you need to implement skeletal animation.
Settings for how to interpolate your BlenderArmature's bone data. These can be used to do things such as:
The pose bones at an individual keyframe time
Something went wrong in the Blender child process that was trying to parse your armature data.
A bone in an armature. Can either be a dual quaternion or a matrix. When you export bones from Blender they come as matrices - BlenderArmature lets you convert them into dual quaternions which are usually more favorable for when implementing skeletal animation.
An error when trying to flatten your exported data across multiple files into one HashMap of armature name to armature data.
Convert ArmatureeshByFilename into a HashMap<ArmatureName, BlenderArmature> that flattens all of the armatures across all of the files into one HashMap.
Given a buffer of standard output from Blender we parse all of the armature JSON that was
written to stdout by