-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contour via wasm in browser? #304
Comments
😱 If you want to go that route, maybe I can help here and there. Some early remarks: |
But, @jerch, I do not want to backstab you and your actual project! :-) |
No worries, I am in exploring mode regarding wasm anyway.
Indeed, thats an interesting question. Imho the VT emulation part will be faster (2-3 times would be my guess), as long as the rendering can all be done within wasm. If not, you will suffer the same issues we have with our different renderers - any call to DOM stuff will be like hammering through a wall perfwise. |
Font rasterization is easely done in wasm via freetype library. I am more concerned how to get the list of available fonts and load these files. Either i provide a good set of default fonts insid the binary (wise choice as fallback) and/or there will be an API exposed the wasm object user can use to supply the desired font file. Do i have actually wcc SS to the host file system or is that at least possible? (Would be the best case). |
What is "wcc SS to the host file system"? Wasm is a sandbox with almost no access to anything outside. There are attempts to get limited system access abstracted (WASI), but as far as I understand it, thats not meant for browser wasm engines. Means you'd have to load the font files into wasm on your own by some sort of JS-API around it. |
Damn smartphones.... Let me repeat: Do i actually have access to the host filesystem But i think you already have me there answer. I would need a bridging API. |
I just checked. It at least is possible to run qt OpenGL apps in the browser through WebAssembly. This is officially supported.
So the only unknown would be how to execute local executables (shell) and how to read/write config.
The text was updated successfully, but these errors were encountered: