tatarize

Using a AbstractLaserProperty as a simple drop in replacement for vector and raster settings works fine. In the lasercutter settings it changes the structure of the XStream on the visicut...

Using the RasterBuilder works fine assuming BlackWhiteRaster is backed by a RasterElement class that you can get access to. So that part of my driver rewrite will have to hold...

It seems like some breaking changes might be preferable at this point. #115 for example is fine. But, I feel like even if I nudge things to be properly untangled...

#116 starts to replace some functions with things that should be absolutely identical. I've since thought of a different transition route. Since the only raster that isn't easily backed by...

You should remove the LaserScript stuff. If the LibLaserCut library is well done and clean. A properly scripting language would be a great example application that uses LibLaserCut. Much better...

As an interesting bit of math that serves as part of the basis of https://github.com/inkstitch/inkstitch project there's an interesting bit of math behind fills of vectorized shape geometries that says...

Conceptually the core idea behind block processes would be sort of expanded since it's the chief stacking of contexts. Though in that case we can see that `begin` pushes a...

Should it tho? Also, there's a straight 'opacity' value on objects that is unrelated to their fill or stroke. They didn't disable the rendering, they just made it invisible, it's...

I must be missing somebody about #35, what about it takes any time to implement? I debated affixing a color object directly when I did vpype-embroidery, it seems like you'll...

You're not modifying the API in breaking ways. You're adding a some functionality to it. Usually that's always safe and the real risk is you can't take it back after...