Ongoing pondering, wishing I could separate Lyte user-editable control structure script from locked, AOT'd synthesis engine. An example would be (live) coding something modal, params naturally structured as arrays of arrays, where the control structure could potentially hold many items, and the {receiving) synth engine would be lean. This probably means strings, Lyte send() to Lyte receive(). (It'd be pretty cool if Lyte had a # feature like Lua's get table length.)
Maybe Lyte could just go 100% script-to-script send() and receive(), give scripts port name(s) in Inspector, if names match, then send() and receive() will just work? There used to be a tool named Syphon for app-to-app porting around video that worked like this, a brilliant solution...
Ongoing pondering, wishing I could separate Lyte user-editable control structure script from locked, AOT'd synthesis engine. An example would be (live) coding something modal, params naturally structured as arrays of arrays, where the control structure could potentially hold many items, and the {receiving) synth engine would be lean. This probably means strings, Lyte send() to Lyte receive(). (It'd be pretty cool if Lyte had a # feature like Lua's get table length.)
Maybe Lyte could just go 100% script-to-script send() and receive(), give scripts port name(s) in Inspector, if names match, then send() and receive() will just work? There used to be a tool named Syphon for app-to-app porting around video that worked like this, a brilliant solution...