Supporting different script types

[hrgdavor]

Initial concern is about making sure we can run jscad V2 scripts and V3 scripts.

Still I would like to go further and have a system to be able to run manifoldcad scripts and jscad V1 scripts.

Different projects aim to hide some details to reduce boilerplate code, so they provide enviroment for the script with a number of globals that can be used without script writer knowing where they come from. This is problematic, as it obscures how the system works.

Ideally the scripts should converge to be normal JS files/projects that could be run easily from node and boilerplate should be reduced by providing better utility libraries and minimizing script dependence on special running enviroment.

editor idea

allow hiding some of boilerplate in editor

script structure idea 1: node project

Script is a folder with package.json and jscad version and any other dep lib version is declared there

script structure idea 2: single file script with metadata in comment

• // @jscadui-type: jscad-v1 or by *.jscad extension
• // @jscadui-type: jscad-v2
• // @jscadui-type: jscad-v3
• // @jscadui-type: manifoldcad
• // @jscadui-type: openscad - or by *.scad extension

script structure idea 2: single file script with import maps

it would be single line comment with json // @jscadui-import: {} and editor would help with ui to edit it

could take ideas from deno https://deno.land/manual@v1.35.1/basics/import_maps or browser improt maps