// think through GET / PUT requests... defaults and particular instances... GET /path instantiates a new one of these, loads it. PUT /path walks to that module, updates relevant features. is this heavy? pointers all the way down
// make output boxes, html? post two gcode instructions through to those, from one input terminal box?
//development environment: 'require' means you can't really re-write on the fly, I think? oy push, recompile and resart? this is kind of what you want - to edit intentionally, saving a new thing, loading a new thing... module would have to save a string copy of itself, load that to browser... just push the file
// might have to wrap intputs / outputs into gcode.outputs / gcode.inputs, extends BaseClass (extends EventEmitter)
\ No newline at end of file
// maybe best is to try the click-to-add runtime, learn about server requests etc, then we'll know enough to start
