- Edited
Spine Runtime License Questions
- Edited
Hello,
One of my hobbies is making user interface skins for LibGDX. I release these for free as learning tools and as free assets for the LibGDX community. Now that I'm learning Spine, I see great potential for using Spine to create animated UI's.
My questions are in regards to the Spine Runtime License. I'm not very good at understanding legalese. It's clear to me that the developer that uses my assets will need to own a Spine License. I'll also have to include part of the Spine Runtime License with my project. Which part exactly? Exhibit B makes it sound like no one would be able to use the assets that I produce in a new project. Is that correct? That would defeat part of my objectives.
Any insight would be appreciated. Thank you.
My UI's: https://ray3k.wordpress.com/artwork/
Spine Runtime License: https://esotericsoftware.com/files/license.txt
See Section 2, it grants right for the Spine Runtimes. This means by licensing Spine you get rights to use the Spine Runtimes. It's true that if someone else (eg someone who is using your assets) wants to make use of the Spine Runtimes, they would need a Spine license.
It's great you help out the libgdx community. Do you have any screenshots of your scene2d skins? Did you know Spine is built using libgdx and scene2d?
Thanks for your response.
Neon UI is my most popular one for some reason.
Metal UI is one of my favorites to share because it goes to show that you should never need to use Swing again.
An example of the fun things you can pull off in Scene2D.UI.
There's more in the link I provided.
And yes, I'm fully aware of Spine's relation to LibGDX and I'm forever grateful for your contributions to the library. Spine is the one software I use to explain why I still use Java and LibGDX.
These are great! I love the C64 skin, that is amazing!! :happy:
Wow, them are some great skins!
Thank you for the feedback guys. That really means a lot to me!