sunkai

Hi,

I am a new user of Spine, and am currently familiarising myself with the trial version of the software.

This means that I am unable to export the animation data from Spine to see its format or schema.

If have found the following example of a JSON data file:

http://esotericsoftware.com/spine/files/example.json

Is it the case that Spine only exports its data using JSON, or can it also export using XML? Is this also true for its Texture Packer functionality as well?

Whether you use JSON or XML in a project is largely determined by its data requirements, and the tools that you are using. For most data storage purposes, they are interchangeable.

At runtime, it's best to use a single format, so that you only need to use a single library to parse your static data. In my case, all of my tool chain uses XML to store its data.

There are robust scripts to convert JSON to XML, and vice versa, so if Spine only exports JSON, then I can convert the data files in a custom baking step.

I'm mostly interested in whether there are well defined schema (JSON or XML) for the data file formats, so that I can get an idea of how the data is organised, and how it will need to be parsed at runtime.

Sunkai.
sunkai
  • Сообщения: 2

Søren

Spine exports JSON not XML, I don't know if this is something Nate want to look into at some point, but I doubt it.

You can find the documentation for JSON here http://esotericsoftware.com/spine-json-format/
and how it can be used here http://esotericsoftware.com/spine-using-runtimes/
More will be added to both those pages soon.
Аватара пользователя
Søren

Shiu
  • Сообщения: 2443

Nate

JSON or binary are the only export formats for animation data. The texture packer exports the "libgdx" texture atlas format, which is a simple, text, line-based format. The runtimes have source for parsing this format in many languages.
Аватара пользователя
Nate

Nate
  • Сообщения: 11260


Вернуться в Editor