Hi Loren,
It's not "Sword" per se, but I have ported my King James Pure Bible Search
(KJPBS) software to WASM (in addition to VNC, WebChannel, and native platform
executables). It is also in Qt. I even had it running as a "WASM" before WASM
-- back in the early days of Emscripten-Qt.
My main
All right. I'll definitely be looking into it. In fact, right now I'm working
on setting up Sword in my Github Actions build for Linux, and WebAssembly will
come as soon as Linux, macOS, and Windows all build Sword fine.
___
sword-devel mailing list:
Oi. That's going to be really ... interesting. Modules aren't particularly
small, though they rarely exceed 6-8 files except in the case of those
biggest image-based modules. You might be best to auto-scan the list of
available languages, and generate a different copy of your app for each
language
Thanks for the suggestions, Greg. One positive thing for me is that I am using
Qt, and Qt has a macro Q_OS_WASM that is defined when you are building for
WASM. I'm planning to use this, if necessary, to circumvent WASM limitations by
removing/rethinking features when in WASM. Also, settings that
I looked into it back in the asm.js days and, at the time, couldn't even
get the asm.js stuff to work. I haven't touched it since WebAssembly came
along and seems to have really standardized things. I've heard of some very
complex things being transpiled into WASM, that gives great hope that
someth
First and foremost: I promise that I will try to not bug y'all with any more
questions for a while (at least, not with questions not on this topic).
Does anybody know if Sword works with WebAssembly? The reason that I ask is
here: https://lorendb.github.io/TotalReqall/wasm/TotalReqall.html. (Not
