sorry. (for the record) REPL is old acronym for Read-Evaluate-Print Loop, is that thing you get in interpreted languages (forth/lisp/ruby/python/lua/sclang) where you can type a statement or a bunch of statements (a âchunkâ) and the interpreter Evaluates them and tells you what happened.
the maiden editor includes a REPL for the lua layer and one for the sclang layer.
its assumed that you may indeed want to try things out with the lua REPL while composing scripts. (the lua scripting layer is basically where high-level musical decisions are made - which parameters are to change when, in response to what.)
as noted, simply editing the contents of a script file will not actually do anything until you execute the script again (with one button) but you can evaluate individual lua/sclang chunks in real time, and they will execute in the same VM /interpreter environment as the scripts.
by design, itâs assumed that you wonât actually be changing the supercollider code on the fly - the sound engines are Classes, which require sclang to restart. this decision has Reasons (efficiency of execution, catching errors earlier, more structured code) but it is basically arbitary, and someone more into dynamic programming with supercollider could easily build their own layer conforming to the same OSC protocol.
[aside] again. i donât know about yall, but i donât actually like programming and making music at the same time; for me, norns will live in a pedalboard. i am very much in favor of Not Programming and making things that are fun for Not Programmers.
custom kernel thanks to the efforts and expertise of various lines members (not me!). base system is debian-ish. more details later.
Can we run our own processes alongside?
of course. though the norns controller process can already talk to any device accessible by libudev/libevdev. permissions managed by udev rules as is âright and proper.â soundplane will be a bit of a project, but itâs on the drawing board for sure.