kolAflash's comments

On: ZetaOffice: LibreOffice in the Browser

[kolAflash]

This demo is read only.

https://zetaoffice.net/demo2.html

https://github.com/allotropia/zetajs/tree/4e071799d6318ac683...

On: ZetaOffice: LibreOffice in the Browser

[kolAflash]

You mean the one about Kasidy Yates? ;-)

On: ZetaOffice: LibreOffice in the Browser

[kolAflash]

COOL (Collabora Online) requires some extra infrastructure. See this previous post.

https://news.ycombinator.com/item?id=42251940

I use COOL every day. But I haven't set it up on my low end home server yet, because of the extra resources needed.

[gbraad → kolAflash]

I am aware of the additionals, like COOLWSD. But since they run this in their Android apps, it seems this can already be Pi-ready

On: ZetaOffice: LibreOffice in the Browser

[kolAflash]

If "the browser" != [Chromium], but [Chromium, Firefox, Safari, Ladybird, ...], then I'm pretty happy with that. I consider it's much better then having Windows, iOS or GApps-Libraries-For-Android as de facto standard OS.

Surely, my beloved Debian would be the much more perfect OS for everyone ;-)

On: ZetaOffice: LibreOffice in the Browser

[kolAflash]

Got our eyes on that idea ;-)

I'll be the first one celebrating if I can add a WASM LibreOffice to my private, low end (Raspberry Pi alike) Nextcloud home server.

On: ZetaOffice: LibreOffice in the Browser

[kolAflash]

Being one of the ZetaOffice (and LibreOffice) hackers, I use Firefox as my primary browser. And I really don't like using software only Google knows how to support (=> Chromium). Sometimes I even think about migrating to SeaMonkey

But for example, you unfortunately can't properly debug multi threaded WASM code in Firefox.

https://bugzilla.mozilla.org/show_bug.cgi?id=1589908

Have a look at the Firefox developer tools' debug tab with this page opened. And it will list the threads (web workers) named with some randomized UUID. Impossible as a daily development driver :-/

https://zetaoffice.net/demo2.html

Chromium's Sources tab properly shows each thread's name. So I can easily spot "em-pthread_1" which contains the LibreOffice main thread.

But have a look at this line and you'll spot some extra code I added for running in Firefox :-)

https://github.com/allotropia/zetajs/blob/8258649a7b98fd6af9...

If you have an idea for how to fix a Firefox specific problem, please file an issue and I promise to check if we can integrate the fix.