I’m apparently a bit thick, or just never done this before… what exactly do you mean?
hjh
See Network Monitor — Firefox Source Docs documentation - there is probably also something similar available for chrome.
The assets you probably need are
https://sc.dennis-scheiba.com/sclang.js
https://sc.dennis-scheiba.com/scsynth.js
https://sc.dennis-scheiba.com/sclang.data
https://sc.dennis-scheiba.com/sclang.wasm
https://sc.dennis-scheiba.com/scsynth.wasm
Ok, thanks. I tried some sort of network monitor in Chromium but it just wrote a big json file, not useful. I’ll try it in Firefox later.
sclang.data… extension classes would go in here?
hjh
Yes, this is the file where the class library is included, though I am unsure if you can modify that easily w/o a build?
As an alternative/hack, you can see my other suggested approach here: https://sc.dennis-scheiba.com/c/6898e9605c92ddf741061dc9d4aaa673
“Save all as HAR” doesn’t seem to be useful. I searched “how to save files from network monitor Firefox” and I see several unanswered threads.
A build is looking more attractive, tbh, but, probably have to be tomorrow.
hjh
You maybe have to select the proper filter in order to see the wasm/js files.
Or you can just do wget/curl the file list from above.
Just be aware that the build pipeline is rather complex b/c you need to setup emsdk.
It is probably easier to just fork from this branch GitHub - capital-G/supercollider at wasm-files · GitHub , add the files that you need to the ClassLibrary, push to trigger the CI and download the wasm build from CI - this way you can obtain a custom build w/o setting up emsdk etc.
OK, thanks, I did manage to get the five files (although sclang.data is empty, which I guess is not right).
Also, I forked your repository and cloned the wasm-files branch. I tried copying sclang.js / .wasm / .data into platform/wasm/sclang, and scsynth.js / .wasm into platform/wasm/scsynth. dev_server.py successfully serves directories, but the sclang interpreter isn’t doing anything (and this doesn’t have your slick editor). I’m guessing this might be because the build products should be stored somewhere else?
Fully understood that these sorts of packaging details are low priority until more of the core functionality is working.
For today, I’ll have to put this aside and write the proposal based on the assumption of core SC only, running off your website. There would be time over the next couple of months to try to get something working locally.
hjh