I'm not sure how hard (or feasible) it would be, but It would be great if we could compile Squash to JavaScript using emscripten.
I think the only real architectural change would be that we would have to have a file telling Squash where to find plugins instead of relying on enumerating them (see #176). Other than that it's probably mostly about making sure plugins are compatible, where the big issue will probably be endianness.
It would also probably make sense to ifdef out some of the convenience APIs (to reduce the compiled size) and provide an easy to use JS wrapper instead.
I'm not sure how hard (or feasible) it would be, but It would be great if we could compile Squash to JavaScript using emscripten.
I think the only real architectural change would be that we would have to have a file telling Squash where to find plugins instead of relying on enumerating them (see #176). Other than that it's probably mostly about making sure plugins are compatible, where the big issue will probably be endianness.
It would also probably make sense to ifdef out some of the convenience APIs (to reduce the compiled size) and provide an easy to use JS wrapper instead.