Playback client library.

[foobit]

It would be useful to have a separate client library that would minimally:

1. Read a VPaint .vec file (from file or memory)
2. With a specified frame number, return that frame's triangle mesh data (optionally with color vertex information).

The client library could be used for:

• Standalone VPaint .vec player
• Incorporate it into business applications/presentations
• Used in games for animated sprites (what I would use it for)

I started looking at the source to see if the Editor, Qt, and OpenGL could be separated easily.

Thanks for making a powerful and easy to use animation tool!

[dalboris]

Thx for the input, I totally agree! That would not only be super useful, but also help adoption. I'm planning at a full rewrite in a 1-2 years time frame. At that time, things would be more modular and should allow this. In fact, I'll keep this specific case in mind to ensure that the architecture allow it.

On January 24, 2017 6:18:29 PM Scott Ramsay [email protected] wrote:

It would be useful to have a separate client library that would minimally:

1. Read a VPaint .vec file (from file or memory)
2. With a specified frame number, return that frame's triangle mesh data (optionally with color vertex information).

The client library could be used for:

• Standalone VPaint .vec player
• Incorporate it into business applications/presentations
• Used in games for animated sprites (what I would use it for)

I started looking at the source to see if the Editor, Qt, and OpenGL could be separated easily.

Thanks for making a powerful and easy to use animation tool!

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/dalboris/vpaint/issues/86