@z3dev Got it! I'll try to update the engine with this:
https://github.com/jscad/OpenJSCAD.org/tree/master/packages/web

There is a nice V2 example from one of the openjscad users here:
https://github.com/sdaau/openjscad_example_selfhost_spa_webpage

maybe this is something you can use ?

@Alasdair-McAndrew sure.

check out the recent post by @crysislinux

i haven't seen anyone embed V2 into a web page yet, but that will happen soon.

awesome! one less thing i need to do this week 🙂

I guess my other question about a progress bar in the viewer is either not possible, or too fiddly to be practicable?

This hasn't been requested before but some kind of progress indication should be possible.

Can you create a new issue for this?

@BarbourSmith a very good question.

In V2, the best approach is to make a project folder. And then organize the parts as desired, including sub-directories.

project/ - index.js // this file is the entry point, and exports main - tube.js - subassembly/ - index.js

By the way, if the project works with the CLI, then the same project should work with the WEB UI as well.

there is also a nice effort from one of the users.

https://github.com/jscad/OpenJSCAD.org/issues/666

it is a self hosted example. Maybe that is the direction you want ?

@zorglups there's a bug in the V1 proxy script, remote.pl, and this prevents files to be loaded properly if the file (URL) does not have a proper extention.

a fix has been made, and the V2 website is running the fixed version of remote.pl

but you need to provide a URL which accesses a V2 design, such as...

https://www.jscad.xyz?uri=https://www.thingiverse.com/download:8705160

OR

https://www.jscad.xyz#https://www.thingiverse.com/download:8705160

@BarbourSmith I saw your post but didn't reply as I wasn't sure it was about. I already tried on V2 the function that splits a solid into pieces as it is something that i use a lot : https://jscad.xyz/#https://raw.githubusercontent.com/gilboonet/gilboonet.github.io/master/demos/gig2i.js The function is scission3d() and the source is here : https://github.com/gilboonet/gilboonet.github.io/blob/master/demos/gig2i.js

@z3dev Thanks for the comments.

I do think a catalogue in the website would definitely increase popularity of JSCAD.
This will attract people who never got interested in JSCAD --- those who don't know how to code and can't use any CAD software.

Sadly, most of them might be only end users and cannot directly help the development of the JSCAD project.
As far as I know, the people in this community are all fully capable of both programming and 3D modelling.

Maybe there can be a mechanism which can discover what those "end users" need most, and help the develop team to build accurate designs for those users.

@z3dev Just I did!

@z3dev thank you. For now I would only like create a viewer element within an angular application. Is there a release of v2 on the public npm registry? I've had a look but can't seem to find it. If not, please could you point me to instructions on how to build it? I'd like to host it on my private registry for the rest of the work I intend to do.

@juanccilleruelo thanks for pointing that issue. the link has been changed.

@Cid-Zhang Thanks! And, welcome!

Your models look very cool. I'm sure that others will enjoy creating various hinged shapes as well.

Please let us know if you need some assistance with JSCAD. There are lots of very experienced users in the group.

@irevdev welcome!

the README files for the packages will provide some information on installation and initial use. See packages/cli, packages/web, packages/desktop

the currently available application (www.openjscad.org) is on the master branch. and there is major development on V2 branch.

we are asking for people to become 'early adopters' if interested in V2. there's been some good progress lately with the creation of the initial v2 packages. more to come in the next few weeks.

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

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