*@Matthias* thank you for your introduction :) I thought of that possibility (WebAssembly), but that isn't a happy path for the following reasons:
- Porting from C++ (or Rust) to WebAssembly is a big effort and not as "simple" as it might sound. - The result will most likely result in one or several binary Wasm modules totalling more than 100MBs, making it slow to load, and unusable in mobile browsers. So far the best approach to a browser based version I figured out is still to start from scratch using TypeScript. Since all the tough questions (rendering, design patterns, etc) have already been answered in OpenOffice, I came here for help as my C++ is at best, basic, and apprehending such a huge code base alone seems... unrealistic. I have found, and tested, this github repository ( https://github.com/Hufe921/canvas-editor), which goes in the right direction (using html canvas). I have built a UI around it to get a feel of the thing ( https://docs-9ef.pages.dev/), but the internal data structure (and by extension the rendering engine) isn't quite complete enough to handle a full ODT/DOCX spec. Help Wanted :) -- Mickaël Cassy On Tue, May 20, 2025 at 10:12 PM juan francisco Minor <juanfmi...@gmail.com> wrote: > How about translating to rust? > > Regards, > Juan Minor > > > On May 20, 2025, at 9:42 AM, Damjan Jovanovic <dam...@apache.org> wrote: > > > > On Thu, May 15, 2025 at 9:22 AM Mickael cassy <mickael.ca...@gmail.com> > > wrote: > > > >> Hello Everyone, > >> > >> I am working on the idea of building browser editors that > >> handle OpenDocument format and OOMXL as first-class citizens. > >> > >> I have identified a few points of interests in order to get an idea of > the > >> effort required: > >> > >> - *Rendering engine*: How to design the rendering engine, what code > >> architecture will allow enough flexibility to render both formats in > >> browsers as closely as possible to what OpenOffice and Microsoft > Office > >> would. > >> - *Internal data structure*: I plan to support collaboration using > CRDT, > >> I suppose that has an impact as to how the internal data structure > >> should > >> be designed. > >> > >> So I am coming here to see if anyone would be willing to help me figure > out > >> these points and maybe join me on such a journey. > >> > >> Have a good day! > >> -- > >> Mickaël Cassy > >> > > > > > > One possibility might be to compile OpenOffice to WebAssembly, which > allows > > running C/C++ in web browsers. However that's probably an extremely > > difficult port, needs its own UNO bridge, needs a different graphics > > framework in main/vcl, needs to load libraries and read arbitrary files > (if > > that's even possible in WebAssembly), and will have many limitations. > > > > Regards > > Damjan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
