@z3dev said in Additions for consideration...: @simonclark cool. FYI, there's a bezier function as part of path2 geometry which is based on the SVG algorithm. See src/geometry/path2/appendBezier() Thanks! I'm taking a look at this, and try to make sure the interfaces are similar. My goal was to create something that I could use as an easing function in scaling, rotating, etc. I've also updated the algorithm to support n'th dimensions, and n'th order polynomials (control points).

thanks @z3dev. I made some bad assumptions about what docs were relevant

Thank you. I only work with triangulated models for coding simplicity, even if later (for designs clarity) I usually remove walls between co-planar neighbours. I will certainly soon start to make V2 versions of my code, was only missing this, but for the moment I'm making a vanilla JS pattern editor.

@z3dev I update the docs with "npm run docs" and now documentation about color is available.

@hg42 you might be able to use the regl-renderer module directly. there's a couple of demo applications, which could be tweeked to reload a design.

@drew-pear can you provide the browser name and version? each has it's own set of quirks.

@z3dev for my purposes the type of api doesn't matter much, because I use a preprocessor (currently python, may be something like livescript in the future) that can generate whatever I need. Ideally I would use the lowest level. That said, I could eventually use javascript as a frontend directly. It's a whole different situation with jscad compared to openscad as a backend. My preprocessor generates a tree internally (which seems to be very similar to the vtree). So, the transition to jscad could also be from my tree to vtree... btw. I already created a new thread for further discussions, because I thought it would not fit well under "V2 hulls"): v2-status-and-testing-environments

Nevermind, I fixed everything simply by using triangles instead of polygons.

@johnwebbcole thanks for the lead in... There are still some critical changes happening to a few of the modules. So, publishing is not possible yet, as publishing is automated and publishes everything at the same time. And thanks for trying V2. We have a few other early adopters helping out with testing, and providing feedback. And for those who are looking for early access to V2, then please start here. I'll post more often going forward.

Welcome! Sure. There are several websites that already have custom layouts, custom controls, etc. Here's an example; http://www.knowhave.com/gear/worm.php

I didn't find exactly what is different between the two environments (normal jscad and min), could be getBounds() into min.js. But I fixed it using hard coded values, and it's ok. The aim of my app is to allow average user to select a 3d file then a script that will run on the model from this file and at the end create a pdf file with the cuts and folds needed to build the model. On my site I also put links to the jscad script I use to people can learn from them, but sadly if the first script was easy, it quicky gets difficult for beginners. The scripts app is here : https://gilboonet.github.io/OpenJSCAD.org/packages/web/scripts.html

@gilboonet thank you for that. after a few mis-steps and with the guidance of editor prompts, i came up with this which seems to work for the sphere with a sound hole. i'm tickled pink because i had wanted to provide form fields for the parameters also, but due to my newbieness, thought it would be additional html/javascripting. function main(params) { var sr = params.sphereradius; var sh = params.soundhole; var wt = params.wallthickness; var fn = params.fragmentnumber; return [ difference(sphere({r:sr+wt, center:true, fn:fn}), sphere({r:sr, center:true, fn:fn}), cylinder ({r:sh, h:-(sr+wt)})) ]; } function getParameterDefinitions() { return [ { name: 'sphereradius', type: 'number', initial: 47, caption: 'Sphere Radius' }, { name: 'soundhole', type: 'number', initial: 15, caption: 'Sound Hole Radius' }, { name: 'wallthickness', type: 'number', initial: 2, caption: 'Wall Thickness' }, { name: 'fragmentnumber', type: 'number', initial: 100, caption: 'Fragment Number' }, ]; }

@z3dev Hello, I didn't open an issue because it's V1, but I will do it so we could keep track of the solution I used. Yesterday I tried my little html5 app on my android tablet with Firefox and it works perfectly even the PDF creation part

And the answer is... I'm broke I was treating the center({axes:[true, true, false]}, object) like the old object({center:[true,true,false]}) which is not the case since primitives are now created centered at [0,0,0] by default. Since the primitive is created centered by default at [0,0,0], changing the axes on a new part doesn't really have an effect. Picking a consistent default is probably the 'right thing(tm)' to do since the old primitives where very inconsistent - round things like cylinders and sphere where centered on X/Y but not Z and cubes where created with a corner at [0,0,0]. Hopefully new docs will have little warnings for those transitioning from V1 to V2 and maybe some helpful examples for porting old designs over.