QMSH

Overview

The quick-mesh sandbox is a simple browser-based build of the quick-mesh kernel - which aims to make the process of trying quick-mesh easier and safer.

Essentially this experimental tool enables you to run quick-mesh scripts directly in your browser without having to install additional software.

The primary aim is to make it easy to get to grips with the grammar if you are still on the fence as to whether or not quick-mesh is for you.

Vitally: unlike web-based modelling solutions which take the thin-client approach - this sandbox executes client-side meaning your scripts are never transmitted to a server and that you can also use it without a network connection.

Note: that relative to the native quick-mesh applications (such as the command-line kernel and mobile editor) this sandbox comes with both benefits and limitations.

The key benefits are portability, safety and greater simplicity in setup. The main limitations are reduced efficiency, reduced functionality and reduced usability.

Specifically the sandbox is slower than the native applications and exposes only a core subset of the features supported natively. Put simply the sandbox is not a replacement for the QMSH-Kernel or the QMSH-Editor - rather it is intended as a supplementary tool for portable, environmentally isolated testing.

Instructions

In order to use the sandbox you will need a Web-GL enabled browser - to display the generated 3D polyhedral entities. You will also need to ensure that Javascript is enabled - to coordinate the application's interactive elements. You will (optionally) also require a browser supporting Web-Assembly - in order to juice the mesh-assembly process' runtime relative to the use of pure Javascript.

When you are ready to use the sandbox - select one of the following build variants - which launches the corresponding version of the sandbox in a new browser tab.




Note: the build variants present exactly the same user-interface. The main difference between them is the manner in which the kernel's native code is compiled for the web. The Javascript variant maps to setting the Emscripten flag -s WASM=0 - whereas the Web-Assembly variant is compiled with the default behaviour.