thorstenb

4 ms·

1.
by thorstenb 2y ago
Most devs here use FF as their daily driver - that said, if you need to debug an emscripten-compiled c++ WASM application in the browser, then it's either printf-debugging, or Chrome + the C/C++ DevTools extension. Additionally, t
2.
by thorstenb 2y ago
> It’s going to be extremely hard to get even decent results without targeting real DOM instead of going pure-canvas, and you can’t get excellent results without doing so. One of the ZetaOffice (and LibreOffice) hackers here - and I have
3.
by thorstenb 2y ago
ZetaOffice is focusing on developers wanting to integrate it (be that a web app, or a desktop line-of-business application, e.g. via Eclipse RCP) - having the exact same code built across all platforms should make for excellent consistency
4.
by thorstenb 2y ago
Firefox is indeed a bit of a hit-and-miss these days (though we absolutely want to support it). Best experience currently is on Chrome(ium).
5.
by thorstenb 2y ago
Indeed can be done, proof of concept shown in this talk: https://www.youtube.com/watch?v=X8LwaDjcr7M Regarding sandboxing - everything WebAssembly is heavily sandboxed already, and requires cross-origin isolation in the bro
6.
by thorstenb 2y ago
That still seems to be there, even for gtk4: https://docs.gtk.org/gtk4/broadway.html (but it says, between the lines, mostly stale I guess) As an aside: one of the very first demos of LibreOffice in a browser (from the
7.
by thorstenb 2y ago
Yup, and it's all fully upstreamed in LibreOffice, see our blog ( https://blog.allotropia.de/category/libreoffice/ ), and the upstream wiki page: https://wiki.documentfoundation.org/Development&
8.
by thorstenb 2y ago
If you could file an issue please, at https://github.com/allotropia/zetajs/issues (with os version & hardware, if relevant)?
9.
by thorstenb 2y ago
ZetaJS is a browser-based version (using LibreOffice WebAssembly) - that should work (tm) on all reasonably modern browsers, including iOS. But see compat matrix for details: https://webassembly.org/features/
10.
Show HN: ZetaJS – client-side LibreOffice widget and automation in the browser(github.com)
5 points by thorstenb 2y ago|4 comments
11.
by thorstenb 5y ago
We already use cairo/freetype/skia to do essentially all the document rendering in software (not for the Qt prototype though), so that's not a big leap to get that blitted out. Incrementally then using more of html canvas to
12.
by thorstenb 5y ago
Qt clearly deserves the credit for having a WASM runtime that gets us a working GUI toolkit. But this was still a gigaton of work to pull off inside LibreOffice (starting many years ago, actually natively using Qt as one of the GUI toolkits
13.
by thorstenb 5y ago
Yep
14.
by thorstenb 5y ago
With LibreOffice, the nice thing is you can chose. if you want all of the above - install the native version.
15.
by thorstenb 5y ago
Longer-term, we need to move to browser-native GUI, yep. The nice bits though - the entire document loading, rendering & editing works in the browser now.
16.
by thorstenb 5y ago
Caching is a prob, due to the current size - what works here is: * FF: set browser.cache.disk.capacity to something >300MB, then set browser.cache.disk.max_entry_size to at least 150MB * Chrom{e|ium}: start browser from cmdline, via `chr