Making openscad-playground importable as a React component

[Reiss-Cashmore]

Hi,

I wanted to use the Playground in a React project I'm working on but the current setup with the playground means you tend to have to bend your project's toolchain around the way openscad-playground is currently set up.

So, I did some work to get openscad-playground built using a vite toolchain into an exported, importable React component / library.

https://github.com/Reiss-Cashmore/openscad-component

I've published the package here: https://www.npmjs.com/package/openscad-playground

Would there be appetite for me bring this work within the main project? Maybe a toolchain on the side responsible for building the NPM package if you want to stick with Webpack for the main development?

I'd rather not have to maintain this downstream, although the changes to the playground source are very minimal so merging upstream changes wouldn't be terrible.

[Reiss-Cashmore]

Source for a simple test app is here showing it's usage in a fully working project is here: https://github.com/Reiss-Cashmore/openscad-component/tree/main/test-app

[t-paul]

It sounds like this needs some discussion on the scope of the different repos involved.

Here's my current understanding:

• openscad - the main source repo
• openscad-wasm - build environment for the WASM version of OpenSCAD using unchanged code from openscad
• openscad-playground - a specific application using the WASM version providing the "playground"

Essentially all of the playground work was done by @ochafik so he probably will provide his views on the topic.

So I'm not sure where a react component would fit in best, I actually was hoping at some point we could have something between openscad-wasm providing the core and full applications that can provide things like a simple viewer component. This would feel like the best place to also have some re-usable components. I'm not sure how your work fits that, but it sounds like it might be close.

[Reiss-Cashmore]

It sounds like this needs some discussion on the scope of the different repos involved.

Here's my current understanding:

• openscad - the main source repo
• openscad-wasm - build environment for the WASM version of OpenSCAD using unchanged code from openscad
• openscad-playground - a specific application using the WASM version providing the "playground"

Essentially all of the playground work was done by @ochafik so he probably will provide his views on the topic.

So I'm not sure where a react component would fit in best, I actually was hoping at some point we could have something between openscad-wasm providing the core and full applications that can provide things like a simple viewer component. This would feel like the best place to also have some re-usable components. I'm not sure how your work fits that, but it sounds like it might be close.

Appreciate the response, happy to take direction on where this would be best placed to live. It does sound like what I've done would fit in with what you've described with it slotting into openscad-wasm especially if I, you or someone else builds and exposes the components for different front end / mobile (thinking react native) environments. I may be up for exposing a Vue version personally.

Interested to hear on the other maintainers take :)