Okay then. A simpler solution would be an OpenSCAD Jupyter kernel that accepts an OpenSCAD program as input, writes it to a *.scad file, runs the openscad program to create a *.stl file, sends the captured stdout/stderr + the STL back to the client over Jupyter protocol. The client displays the console output and the triangle mesh. This would lack fast preview capability, and you still need an interactive user interface for the client side, which lets you scale and rotate the 3D object in its viewport. Adding customizer support significantly complicates this. On 30 May 2018 at 15:25, Torsten Paul <Torsten.Paul@gmx.de> wrote: > On 05/30/2018 09:17 PM, doug moen wrote: > >> To do this, you need to create a clean separation of the >> OpenSCAD GUI from the OpenSCAD kernel. Put the kernel in >> a separate library and formalize the API that connects >> the kernel and the GUI. >> > > > That might be the perfect solution, but I'm pretty sure > it's not needed to get a working solution. Otherwise > Thingiverse Customizer would not exist. > > > ciao, > Torsten. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >