Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Generating vector graphics for laser cutters

Name: Anonymous 2015-07-14 20:02

I'm looking for a way of generating vector graphics in the following formats for the use of a laser cutter: PDF, SVG perhaps DXF
What I've done so far is write everything in good old postscript and directly cut that.

Now that has some serious problems, one I don't want to deal with it, postscript is a pain in the ass. It's easy to learn, intuitive but I haven't been able to get accustomed to it. Too weird, too little utility stuff like debugging or access to the data structure ultimately used for rendering.

What I also need: Short test cylces, so no sepples, java or other compiled shit. (That goes for cairo as well)
Some ready way to talk to a web server, I want to have my parametic models available at a site, fill out some form and then download a finished layout.

OpenScad would work but it hasn't got real support for 2D graphics, and it's limitations are kind of annoying, you can't even allocate any memory so fuck that.
I'm considering processing, but I'm fishing for alternative solutions.

Name: Anonymous 2015-07-18 16:11

>>17

I think it's pretty clear what my intentions are when you pay attention to the context of the thread, not just the topic.
For you, i'm looking for a library that helps me write programs that generate laser cutting paths. Most of the stuff I do is parametric, where I define the dimensions of some parts of the assembly and the rest gets calculated. There is some repetition and modularity, for instance finger (woodworking) joints are defined as custom paths which take into account the material thickness, the length of the edge and the sort of joint (which part of the assembly so they fit).
Currently I only compensate for the kerf of the laser in cases where it's needed as part of the custom path algorithm.

What I intent on doing (what's not possible with postscript without too much hassle) is returning an outline of a complete closed path and after that some sort of strip packing algorithm that turns the different part into a layout.
I suspect this last part to be a performance issue, but since it's just an algorithm that isn't subject to constant change it can be done with a compiled language.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List