Posts made by z3dev

@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 sure.

here's the code https://github.com/z3dev/vue-components

this is only a viewer for a pre-compiled (JSON) design. V2 only!

@kevinos There's no documentation on embedding because there far too many frameworks. However, as you already researched, there are people embedding JSCAD in webpages.

Recently, I've been playing Vue, and have a simple Vue component which can render a JSCAD V2 geometry. It's kind of cute, but shows potential.

@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!)

HEADS UP! Please get the latest version of JSCAD V2, as there have been some BIG name space changes in the modeling API.

• math => maths
• geometry => geometries

These are the last major changes to the modeling API, as all big changes have been completed.

The WEB UI is now quite usable for creating designs. It's best to drag-n-drop project folders to the window, and work with the pieces via a favorite editor. If "Enable auto reload" is checked then changes will be detected, and rendered again.

For those wanting to get hold of JSCAD V2, it's still in 'early adoption' mode. But you can get started here.

And a BIG THANKS for everyone that has provided feedback. Keep those comments coming!

@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.

@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()

@simonclark Nice innovations to V2.

I think some others will be interested in the automatic VM launch, and configuration. Please consider adding a pull request to the V2 branch.

I'm also excited to see another use of the new extrude functions.

Funny... I don't remember math.bezier() There was talk about adding bezier() to the primitives, but no time. Again, please consider adding a pull request to the V2 branch.

Hi Simon,

When you say 'contributing' the I'm guessing that you are going to work with JSCAD V2. Please follow the notes in Early Adoption of V2.

The JSCAD V2 API is different, so you'll also need to see the documentation. You can generate the documentation as well by running..

npm run docs

There will be a full set of documentation in the 'out' directory, i.e. HTML files. Just open 'index.html' with any browser.

Cool. But be careful as the boolean operations can create polygons with more than three (3) vertices. Also, some of the primitives create polygons with four (4) vertices.

JSCAD V2 is moving along, with recent changes focusing on the WEB UI. Some annoying bugs have been fixed so get the latest and greatest changes from the V2 branch.

One of the features of JSCAD V2 are themes. Those are now working properly, and there are some new themes as well.

Another area of improvement has been the support for projects. One of the main goals of JSCAD V2 has been the support of reusable of components, especially from other members. You should be able to use the same projects via CLI (command line) or WEB UI. It's kind of 'alpha' but please try assembling some projects.

For those wanting to get hold of JSCAD V2, it's still in 'early adoption' mode. But you can start here to get started.

And a BIG THANKS for everyone that has provided feedback. Keep those comments coming!

@gilboonet are you using the 'dark' theme?

yeah. there's still some issues in the web UI.

@gilboonet nice example.

I understand now. Those vec3 functions return a Float32Array, which is NOT an Array.

For now, you can use ES6 javascript syntax to make things easier.

vol = transforms.translate([ ...d2 ], vol)

By the way, the latest V2 branch has a fix for the documentation on colors.

@gilboonet said in little V2 feedback:

Functions like translate or size attribute of a primitive that need an array doesn't accept a variable containing an array but only a litteral array. Are there coding basics to know to work with vec3/vec2 ?

You should be able to do this...

let mysize = [2, 3, 4]
let myshape = primitives.cuboid({size: mysize})

@gilboonet said in little V2 feedback:

I wasn't able to use color library, and the generated doc about modeling/color is empty, so maybe it is not available for the moment, or did I miss something during installation ?

Ooops! There's a little name issue in the documention. Will be fixed soon.

@gilboonet thanks for the nice feedback.

FYI, you can generate documentation as well, if you need some documention on the new functional API.

npm run docs

And open 'index.html' found in the 'out' directory.

@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.

@hg42 your 'stateless' pipeline seems feasible using the desktop app, however that has not been ported over to V2 yet.

and as you already understand, the current V2 demo.html is specialized for running as a single page application, with lots of special functionality. this is probably not going to work well in the pipeline, even after massive hacks.

the core of V2 is pretty solid now, so i'm working on some of the remaining items in the V2 check list.

one of those is a 'minimum' viewer for V2. if anyone has some ideas or requirements for this then now is the time for some feedback.