Re: Not working as expected?
Posted: Wed Jun 02, 2021 5:17 pm
Quite a while ago LiveCode had a "stab"at producing something that would run in a web-browser, and it did,
after a fashion. That was later abandoned, and I don't know why that was.
Now there is a new version.
Now here are my expectations (for what they are worth):
1. If I make a LiveCode stack I know that I can run off standalones from it to run on Windows, Linux and Macintosh in an extremely
easy and straightforward way.
2. I know that I can run off standalones to run on Android and iOS with a bit more fiddling around.
My personal experience is that making standalones for Windows, Linux and Macintosh results in standalone executables that
98% of the time reproduce the functionality of the source stack as well as its appearance (and that 2% can, normally, be ironed
out without undue effort).
My expectations re something that can be viewed on a web-browser
(regardless of the underlying operating system that web-browser is running on) are
similar to my expectations of a standalone on the three desktop platforms I mentioned.
So, for the sake of argument, the very simple stack I prepare of a slideshow of my holiday snaps should look
almost identical in a web-browser to a standalone, and its functionality should be the same.
Or, to get a bit more technical, a web-based version of my Devawriter Pro (that leverages non-standard Unicode fonts)
should allow end-users everything that a desktop standalone offers.
This is also the way I understand what is written here: https://livecode.com/
"Create native applications for iOS, Android, Windows, Mac, Linux, Server & The Web all from the same code."
Reading about Emscripten: https://en.wikipedia.org/wiki/Emscripten
"Emscripten allows applications and libraries written in C or C++ to be compiled ahead of time and run efficiently in web browsers, typically at speeds comparable to or faster than interpreted or dynamically compiled JavaScript. With the more recent development of the WebAssembly System Interface (WASI)[5] and WebAssembly runtimes such as Node.js, Wasmtime,[6] and Wasmer,[7] Emscripten can also be used to compile to WebAssembly for execution in non-Web embeddings as well."
Tells me nothing that has any obvious connexion with LiveCode . . .
after a fashion. That was later abandoned, and I don't know why that was.
Now there is a new version.
Now here are my expectations (for what they are worth):
1. If I make a LiveCode stack I know that I can run off standalones from it to run on Windows, Linux and Macintosh in an extremely
easy and straightforward way.
2. I know that I can run off standalones to run on Android and iOS with a bit more fiddling around.
My personal experience is that making standalones for Windows, Linux and Macintosh results in standalone executables that
98% of the time reproduce the functionality of the source stack as well as its appearance (and that 2% can, normally, be ironed
out without undue effort).
My expectations re something that can be viewed on a web-browser
(regardless of the underlying operating system that web-browser is running on) are
similar to my expectations of a standalone on the three desktop platforms I mentioned.
So, for the sake of argument, the very simple stack I prepare of a slideshow of my holiday snaps should look
almost identical in a web-browser to a standalone, and its functionality should be the same.
Or, to get a bit more technical, a web-based version of my Devawriter Pro (that leverages non-standard Unicode fonts)
should allow end-users everything that a desktop standalone offers.
This is also the way I understand what is written here: https://livecode.com/
"Create native applications for iOS, Android, Windows, Mac, Linux, Server & The Web all from the same code."
Reading about Emscripten: https://en.wikipedia.org/wiki/Emscripten
"Emscripten allows applications and libraries written in C or C++ to be compiled ahead of time and run efficiently in web browsers, typically at speeds comparable to or faster than interpreted or dynamically compiled JavaScript. With the more recent development of the WebAssembly System Interface (WASI)[5] and WebAssembly runtimes such as Node.js, Wasmtime,[6] and Wasmer,[7] Emscripten can also be used to compile to WebAssembly for execution in non-Web embeddings as well."
Tells me nothing that has any obvious connexion with LiveCode . . .