Hi all, Here’s a quick update outlining the progress from Weeks 4 & 5 of the Rust–UNO binding project.
Over the past two weeks, I focused on understanding the UNO bridges mechanism and began laying the groundwork for it here: https://gerrit.libreoffice.org/c/core/+/187853 After further discussion, we’ve decided to continue enhancing the existing work in the following patch instead: https://gerrit.libreoffice.org/c/core/+/186425 This approach focuses on accessing UNO objects implemented in C++ from the Rust side via FFI, using Codemaker-generated wrapper code. The main goal is to enable calling existing UNO functionality from Rust, even if we don’t (yet) support implementing UNO objects fully in Rust. Next Steps This week, I’ll focus on: Diving into Codemaker to understand how it generates Rust bindings. Using the generated Rust code to: Query UNO interfaces. Call loadComponentFromURL and similar methods directly from Rust, without routing through temporary C++ scaffolding (as noted in rust_uno/src/examples/load_writer.rs). Best regards, Mohamed
