@z3dev There's one thing that still makes me use obj from my obj2jscad.js. It is that the deserialized obj loses the polygon vertices list and it needs to be rebuild from the geometries, unless I didn'k look at the right place. But as 99 % of the time the user won't use those data, I understand that the deserializer don't keep track of them.
@z3dev Hey! Thanks for the reply and the welcome, appreciated. I tried @danmarshall app and it works as I was expected. I tried the console.log with the web + debug console in safari and chrome (on mac) but didn't get anything printed.
It's any other post with other tools for debugging available or it's still in development? (I'm using vsc)
I have had similar thoughts about getting a drawing tool like this into jscad, I believe it could not only be useful for extruding simple shapes, but also, if constraints are possible, for the layout of all sorts of things.
@z3dev I'm currently working with furniture models, they are all hand made. I sliced 8 models (they are available here https://github.com/gilboonet/designs/blob/master/MEUBLES/readme.md, each picture open the corresp. model into jscad) and they are clean because my scripts (slicer and unflattener) can only produce patterns for models without errors (holes, non-manifold). It's certainly my process that met an unhandled condition. To produce 2 axes imbricated crosspieces, I need to slice and then split slices that are made of multiple separated pieces because crosspiece cut need to be done for each piece. As you said it is too complex to debug. I need to simplify my process, maybe voxelization could help.