See our fork

[robin-swift]

I'm considering streamlining the project by using a wrapper around libembroidery to make our version of EmbroideryIO for the mobile viewer. We wouldn't have to replace it all in one go, so it would help to have your @tatarize help with swapping out the Java wrapped functions.

[tatarize]

Since I wrote this version later and based on libembroidery's work it has a built in encoder and the rest of the tweaks that I realized were needed this is going to be, at present, a better version. Since there's a series of small bugs in the libembroidery reading and writing schemes that were fixed in the intervening years. Also, part of the reason for needing this is the android code doesn't really shift easily to C++ or C. Hooks to natives are remarkably harder and it's significantly easier to have a java version of the same code written in native Java 6.

It's entirely possible to wrap that stuff in an NDK and use libembroidery once that library is up to more modernish standards or superior to this. Though that would likely happen within your fork as this would remain the same as it's been for years now.