Geraint
In case it's helpful: you can also translate the entire CLAP plugin API directly to WebAssembly modules. This means you can ship just the `.wasm` with no supporting JS, so...
You'd still need logic to check for those properties though, wouldn't you? And I suspect there might not be much shared logic for how those arguments are actually used. Even...
I do see how setting properties (on the `_impl` static library?) would mean new settings propagate nicely to all the functions. I feel that's a separate (and substantial!) refactor though,...
Sounds great. 😄 A note/question: because there are custom copying commands for both `RESOURCE_DIRECTORY` and `COPY_AFTER_BUILD`, there are two (conditional) calls to `add_custom_command()`. This worked OK when I tested it,...
@baconpaul Hey - did you manage to take a look at this?
@baconpaul Bump
@baconpaul Thanks for catching that - I've removed the extra commit.
@abique I think the requirements-check is best done from inside the page. Websites manage this OK (outside of ancient enterprise workplace tools which don't work in Firefox or whatever 😄),...
@abique For the starting URI length, can we somehow fix the capacity at `CLAP_PATH_SIZE`? 1kB seems long enough, gives more consistency from hosts, and avoids an extra method in the...
I think it'd be good to set a fixed size, because what is a plugin meant to do if the host gives it a smaller capacity? The maximum length varies...