![]() ![]() I have to admit I'm a bit torn, but I'm leaning in favor of translating to Python. Or to actually just code these formats into python? Oh, are you interested in contributing? That'd be great!ĭid you want an audit of the libembroidery code to fix up the errors there. I might be finishing up my current project pretty soon and was wondering which way you wanted to go for these? Read( "C: \\Users \\Tat \\PycharmProjects \\pyembroidery \\sequin.dst") And some of these things might get progressively easier with lambda functions.ĭx = decodedx( byte, byte, byte) ĭy = decodedy( byte, byte, byte) (DST for example calls 3x JUMP and if so needs a TRIM, and a bunch of jumps in a row doesn't actually matter, you can ignore the jumps and jump to the final destination.) And there might be some more preferred Pythonic way of doing such things that I wouldn't know. And there's a lot of important work done in transcoding files into a stabilizing middleformat. ![]() Obviously such things needs a bit more stuff like a datastructure to actually hold all the data we read in triggering the stop(), colorchange(), move(), stitch(), some metadata and some colors, some threads, and some thread metadata. Read("C:\\Users\\Tat\\PycharmProjects\\pyembroidery\\tree.dst") I do think that the MobileViewer java code is better than libembroidery code, as reading a file into move(), trim(), end(), color_change(), and stop() has a lot of notable benefits, and using the pixel-space to embroidery space at 1:1 is clearly beneficial as well as implementing coordinate system y-flips etc, during the reads and writes is generally more proper.ĭx = decodedx(byte, byte, byte) ĭy = decodedy(byte, byte, byte) But, once the reverse engineering has been done, coding this up in other formats is not actually that hard. There's just a strong need to test that code against itself and keep it as simple and reasonable as possible. There's not a lot of code that needs transcoding. Most of the work is ensuring strong compatibility with something that is ultimately kind of jiggered from understanding various export utilities and files kicking around. I recently wrote out a pretty good cursory first draft overview of many of those formats on the edutech wiki (the PES info is a copy of the wiki on fno7's libpes work I strongly contributed to).Ī quick look will properly show you that the formats aren't actually wildly complex (reading such a file is often downright trivial). But, often checking various parts require a bunch of rather tedious work comparing various hex elements for various outputs, and proper files found in the wild. Most of the serious functional awesomeness of the libembroidery work is simply by establishing the read and write of the files it does a good job outlining the actual format. I might be finishing up my current project pretty soon and was wondering which way you wanted to go for these? Did you want an audit of the libembroidery code to fix up the errors there. ![]()
0 Comments
Leave a Reply. |