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

There have been several discussions about how to build transitions between shapes. Hull and Minkowski are good at combining shapes but don't really provide the workflow described here. Here's one from a while back.. Can we extrude arbitrary and changing 2D shapes along a 2D/3D path? I would hope that some of the folks here could provide some tips.

Hello, you can do something like what I did on this post : https://openjscad.nodebb.com/topic/104/slicing-again-simplifying-code.

@z3dev thanks for your answer, i will check that. Any idea of the release date of the V2? Thanks again. Best regards

@kaosat-dev thanks for your reply i haven't test it yet (I just saw it today). i will tell you if it's works for me. Best regards

That's very good job, looks promising.

Hi @LinGuanfu ! Visually that seeems correct: if you click on help/question mark do you have a menu with a list of examples ? also looking at the console output it seems the two instances are created correctly. Please try opening a design in both panels (or drag & droping a jscad file/folder). The css is not finished and could use some tweaking (or might not be a perfect fit for all use cases, but should be easy to change

@viktor-hedefalk said in Vanilla js/npm in browser?: Or does it resolve those at upload time? Gonna test that… No, it can't do that? That would be the worst security thing ever on a browser to allow… Just watched the tutorial series to the end of part 4 - and the cliffhanger for part 5: https://youtu.be/hnLLNmP_mzA?t=646 "In the next part we will get to how you can split up your design into multiple files…"

Thank you. I will try something similar, it just needs to add a parameter to choose a design number, if the table of random values doesn't have values for this number they are randomly feeded, else they are used for the rendering. Such "mechanism" could be handy for designs using both random values and more than one viewing mode.

@z3dev This looks absolutely amazing ! Lots of uses cases (I am a sucker for 2d in 3d haha)

The simple solutions are always the best. Taking a super thin slice is a great idea, and maybe even the best. The core library will be for core functions, as we expect others (like you) to contribute some really nice high level functionality, such as slicing. If we get the core library rock solid then anything is possible. Projections on to arbitrary planes is on the wish list, but not there yet. Thanks for the awesome posts!