@kevinos no problem. so, JSCAD designs are actually Javascript functions which perform calcuations, create geometry, perform operations with geometry, and finally return the geometry of interest. const {primitives} = require('@jscad/modeling') const main = () => { let object1 = primitives.circle({radius: 22, segments: 36}) object1.color = [1,0,0,1] return object1 } module.exports = {main} The return of object1 from main() is a 2D geometry, i.e. a geom2 object. In the WEB UI, this object is passed to the 'rendering' function, and shows up on the screen as a red circle. The Vue component requires 2D/3D geometries as well. And as a Vue component, it can live inside another Vue component (or application). This is the rendering piece only. The JSCAD WEB UI is doing a whole lot more underneath. It loads all the code, evaluates (compiles?) each piece of code, and finally executes the main() function. If you want this functionality then there's some more plumbing required.

@kevinos welcome! The JSCAD model (code) is required as the compilation is completed by the browser. So, you will have to find ways to obfuscate the code.

@DrShoggoth This is great! Thanks for sharing!

@SimonClark this is cool. thanks for sharing. FYI, this functionality will behave far better after the next update, which folds full numeric precision back into the library. (And 10X improved speed is included for free!)

Nice! I'll pull it down tonight.

@SimonClark no problem. and welcome to the world of jscad development. so, each of the packages are managed via 'lerna'. lerna is kind of cool because it automatically detects the dependencies and links everything together during the 'bootstrap' phase. once everything is linked together, then you can make changes to any of the code, and rerun tests, or run CLI / WEB. also, each of the packages can be tested individually. for example, you can change directories to packages/modeling, and run the tests using 'npm test'. if there's too much noise then you can move the *.test.js files into a temporary directory, and test something special by creating another *.test.js file. AVA is the test harness of choice. It's cool.

@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