Skip to content

openscad/openscad-playground

Repository files navigation

OpenSCAD Playground

Open the Demo

image

This is a limited port of OpenSCAD to WebAssembly, using at its core a headless WASM build of OpenSCAD (done by @DSchroer), wrapped in a UI made of pretty PrimeReact components, a React Monaco editor (VS Codesque power!), and an interactive model-viewer renderer.

It defaults to the Manifold backend so it's super fast.

Enjoy!

Licenses: see LICENSES.

Features

  • Automatic preview on edit (F5), and full rendering on Ctrl+Enter (or F6). Using a trick to force $preview=true.
  • Customizer support
  • Syntax highlighting
  • Ships with many standard SCAD libraries (can browse through them in the UI)
  • Autocomplete of imports
  • Autocomplete of symbols / function calls (pseudo-parses file and its transitive imports)
  • Responsive layout. On small screens editor and viewer are stacked onto each other, while on larger screens they can be side-by-side
  • Installable as a PWA (then persists edits in localStorage instead of the hash fragment). On iOS just open the sharing panel and tap "Add to Home Screen". Should not require any internet connectivity once cached.

Roadmap

  • Add tests!
  • Persist camera state
  • Support 2D somehow? (e.g. add option in OpenSCAD to output 2D geometry as non-closed polysets, or to auto-extrude by some height)
  • Proper Preview rendering: have OpenSCAD export the preview scene to a rich format (e.g. glTF, with some parts being translucent when prefixed w/ % modifier) and display it using https://modelviewer.dev/ maybe)
  • Rebuild w/ (and sync) ochafik@'s filtered kernel (openscad/openscad#4160) to fix(ish) 2D operations
  • Bundle more examples (ask users to contribute)
  • Animation rendering (And other formats than STL)
  • Compress URL fragment
  • Mobile (iOS) editing support: switch to https://www.npmjs.com/package/react-codemirror ?
  • Replace Makefile w/ something that reads the libs metadata
  • Merge modifiers rendering code to openscad
  • Model /home fs in shared state. have two clear paths: /libraries for builtins, and /home for user data. State pointing to /libraries paths needs not store the data except if there's overrides (flagged as modifications in the file picker)
  • Drag and drop of files (SCAD, STL, etc) and Zip archives. For assets, auto insert the corresponding import.
  • Fuller PWA support w/ link Sharing, File opening / association to *.scad files...
  • Look into accessibility
  • Setup OPENSCADPATH env var w/ Emscripten to ensure examples that include assets / import local files will run fine.
  • Detect which bundled libraries are included / used in the sources and only download these rather than wait for all of the zips. Means the file explorer would need to be more lazy or have some prebuilt hierarchy.
  • Preparse builtin libraries definitions at compile time, ship the JSON.

Building

The project uses a webpack-based build system that reads library metadata from libs-config.json to automatically download, clone, and package OpenSCAD libraries and dependencies. This replaces the previous Makefile approach with a more standard, maintainable solution.

Prerequisites:

  • wget or curl
  • Node.js (>=18.12.0)
  • npm
  • git
  • zip
  • Docker able to run amd64 containers (only needed if building WASM from source). If running on a different platform (including Silicon Mac), you can add support for amd64 images through QEMU with:
docker run --privileged --rm tonistiigi/binfmt --install all

Local dev:

npm run build:libs  # Download WASM and build all OpenSCAD libraries
npm install
npm run start
# http://localhost:4000/

Local prod (test both the different inlining and serving under a prefix):

npm run build:libs  # Download WASM and build all OpenSCAD libraries
npm install
npm run start:production
# http://localhost:3000/dist/

Deployment (edit "homepage" in package.json to match your deployment root!):

npm run build:all  # Build libraries and compile the application
npm install

rm -fR ../ochafik.github.io/openscad2 && cp -R dist ../ochafik.github.io/openscad2 
# Now commit and push changes, wait for site update and enjoy!

Build your own WASM binary

The build system fetches a prebuilt OpenSCAD web WASM binary, but you can build your own in a couple of minutes:

  • Optional: use your own openscad fork / branch:

    rm -fR libs/openscad
    ln -s $PWD/../absolute/path/to/your/openscad libs/openscad
    
    # If you had a native build directory, delete it.
    rm -fR libs/openscad/build
  • Build WASM binary (add WASM_BUILD=Debug argument if you'd like to debug any cryptic crashes):

    npm run build:libs:wasm
  • Then continue the build:

    npm run build:libs
    npm run start

Adding OpenSCAD libraries

The build system uses a webpack plugin that reads from libs-config.json to manage all library dependencies. You'll need to update 3 files (search for BOSL2 for an example):

  • libs-config.json: to add the library's metadata including repository URL, branch, and files to include/exclude in the zip archive

  • src/fs/zip-archives.ts: to use the .zip archive in the UI (both for file explorer and automatic imports mounting)

  • LICENSE.md: most libraries require proper disclosure of their usage and of their license. If a license is unique, paste it in full, otherwise, link to one of the standard ones already there.

Library Configuration Format

In libs-config.json, add an entry like this:

{
  "name": "LibraryName",
  "repo": "https://github.com/user/repo.git", 
  "branch": "main",
  "zipIncludes": ["*.scad", "LICENSE", "examples"],
  "zipExcludes": ["**/tests/**"],
  "workingDir": "."
}

Available build commands:

  • npm run build:libs - Build all libraries
  • npm run build:libs:clean - Clean all build artifacts
  • npm run build:libs:wasm - Download/build just the WASM binary
  • npm run build:libs:fonts - Download/build just the fonts

Send us a PR, then once it's merged request an update to the hosted https://ochafik.com/openscad2 demo.