by OpenXTalkPaul » Fri Sep 23, 2022 12:57 pm
I edited the original post
worldescortspag wrote: ↑Fri Sep 16, 2022 1:44 pm
Sorry, I'm extremely busy lately, but now some end Summer things like pool closing are out of the way so I should have more free time to donate.
Still making progress I think and also plotting out the next moves.
Did some preliminary research a while back into wrapping the Emscripten/HTML5 Engine with Electron (which includes Chromium v8 or v9 engines and Node.js, macOS universal native runtimes).
You can install Electron and something called 'natifier' with 'Homebrew' on macOS, from most Linux repos, as well as in FreeBSD Ports list.
Natifier will wrap ANY web-site as an app, cross-platform in that it runs on any platform that has chromium and node builds.
nativefier --name 'OpenXTalkietron' '
https://openxtalk-org.github.io/OpenXTalk-Playground/''
I have become very interested in all of this stuff lately, wrapping JS, WASM modules, HTML5 APIs, Node libraries, and I really think there's a case to made there for enabling OXT to be hardware agnostic into the future, not to mention gaining all of the benefits of a web rendering engine and full access to everything JavaScript and Node.js, including OS native things and shell access, as well as being able to run in multiple processes (similar in architecture to Crhome which runs each web-page in it's own process).
Additionally the work done to port the Engine is very interesting to me, I mean web assembly is still intermediate but it's compiled so its faster than interpreted, but its compiled into a hardware agnostic bytecode format (very much like Extension Builder does).
Obviously more of the engine can be either compiled into .wasm modules or hooked in to any chromium APIs or APIs that exist in our Electron wrapper engine (which includes API for native file system access, among other extremely useful APIs), or hooked into a Node library, or even hooked into a C++ library via JS FFI (just as Extension Builder has the ability to do).
If not the entire IDE running inside Electron (or similar such as DeskGap) wrapper via the Emscripten engine, then at minimum I would want there to at least be an Electron wrapper as a deploy option for that HTML5 tab of standalone builder (the one that currently contains only a single check-box).
I edited the original post ;-)
[quote=worldescortspag post_id=2274 time=1663335879 user_id=1714]
Sorry, I'm extremely busy lately, but now some end Summer things like pool closing are out of the way so I should have more free time to donate.
Still making progress I think and also plotting out the next moves.
Did some preliminary research a while back into wrapping the Emscripten/HTML5 Engine with Electron (which includes Chromium v8 or v9 engines and Node.js, macOS universal native runtimes).
You can install Electron and something called 'natifier' with 'Homebrew' on macOS, from most Linux repos, as well as in FreeBSD Ports list.
Natifier will wrap ANY web-site as an app, cross-platform in that it runs on any platform that has chromium and node builds.
nativefier --name 'OpenXTalkietron' 'https://openxtalk-org.github.io/OpenXTalk-Playground/''
I have become very interested in all of this stuff lately, wrapping JS, WASM modules, HTML5 APIs, Node libraries, and I really think there's a case to made there for enabling OXT to be hardware agnostic into the future, not to mention gaining all of the benefits of a web rendering engine and full access to everything JavaScript and Node.js, including OS native things and shell access, as well as being able to run in multiple processes (similar in architecture to Crhome which runs each web-page in it's own process).
[/quote]
Additionally the work done to port the Engine is very interesting to me, I mean web assembly is still intermediate but it's compiled so its faster than interpreted, but its compiled into a hardware agnostic bytecode format (very much like Extension Builder does).
Obviously more of the engine can be either compiled into .wasm modules or hooked in to any chromium APIs or APIs that exist in our Electron wrapper engine (which includes API for native file system access, among other extremely useful APIs), or hooked into a Node library, or even hooked into a C++ library via JS FFI (just as Extension Builder has the ability to do).
If not the entire IDE running inside Electron (or similar such as DeskGap) wrapper via the Emscripten engine, then at minimum I would want there to at least be an Electron wrapper as a deploy option for that HTML5 tab of standalone builder (the one that currently contains only a single check-box).