- Bearbeitet
[Skeleton Viewer] Bone/SlotNames
Hi,
I think it would be incredibly useful for the skeleton viewer to display the names of bones and slots. I am primarily a programmer and my artist has access to spine. If i wanted to manipulate a slot or a bone, through the API I would have to ask him to open spine up and look at the bones/slots and tell me their name.
Although we do have a naming convention for slots and bones, typos do happen. And it would be annoying if he isn't around to answer my queries. The only alternative at the moment is to trawl though the JSON file, even in pretty print that's not fun.
I think the skeleton viewer is an unappreciated tool, and would like to see it have some more features
Cheers
If we add enough features to the Skeleton Viewer, we'd end up with Spine! The trial can be used to open a Spine project or import a JSON file if you only need to review the data with a Spine license. I do agree the Skeleton Viewer could use some more features, but I think more useful than just viewing the data would be features to play/queue multiple animations on different tracks, multiple skins at once, etc.
Writing tools specific to your apps is easy and can really be helpful. If Skeleton Viewer doesn't do everything you need, it's very easy to extend.
Nate schriebIf we add enough features to the Skeleton Viewer, we'd end up with Spine!
The trial can be used to open a Spine project or import a JSON file if you only need to review the data with a Spine license. I do agree the Skeleton Viewer could use some more features, but I think more useful than just viewing the data would be features to play/queue multiple animations on different tracks, multiple skins at once, etc.
Writing tools specific to your apps is easy and can really be helpful. If Skeleton Viewer doesn't do everything you need, it's very easy to extend.
super late reply but i'll take it
I remember thinking "If we add enough features to the Skeleton Viewer, we'd end up with Spine", when I wrote this post. But I still think that having a light weight, "read-only" way to view the JSON data would be handy to a lot of people.
That is a good point about the trial version, Thanks. Although I do think it would be nice for a light weight version to view the skeleton data. I did send an email (which I just saw as writing this reply) as I intended to fork the repo, and improve the skeleton viewer. As you said, the skeleton viewer being able to support queuing animations and being able to view multiple skins would be helpful to the artists - At least until the editor supports it. This is something the artists here are frustrated by.
I was able to sift through your Git and find the skeleton viewers repo, but unfortunately I have yet to touch the code. but it is a 4 day easter weekend this week, so I might attack it.
cheers!