The zeta.js library provides the facilities to run an instance of ZetaOffice integrated in your
web site, allowing you to control it with JavaScript code via the LibreOffice
UNO technology.
Use cases range from an in-browser office suite that looks and feels just like its desktop counterpart, to fine-tuned custom text editing and spreadsheet capabilites embedded in your web site, to a headless zetajs instance that does document conversion in the background.
For a detailed description of zetajs, see the Starting Points documentation.
(Technically, zeta.js provides a wrapper on top of the
Embind-based JavaScript scripting
capabilities for LibreOffice. But it aims to provide a nicer, more idiomatic JavaScript experience,
and completely hides the underlying machinery. In the future, it may even move away from that
underyling Embind layer, in a backward-compatible way.)
To see a demo of zetajs in use, visit zetaoffice.net/demo.
Check out the examples in the examples folder. We recommend to start with the standalone example.
Those examples are configured to run without requiring an own LibreOffice WASM (LOWA) build. They make use of the ZetaOffice CDN.
Visit zetaoffice.net to learn more about ZetaOffice, its CDN and how to host ZetaOffice yourself.
Using the official versions from zetaoffice.net is the recommended way for most users. Only read on if you intend to build or debug LOWA itself.
See how zetajs makes scripting LibreOffice WASM easy:
const css = zetajs.uno.com.sun.star;
const desktop = css.frame.Desktop.create(zetajs.getUnoComponentContext());
let xModel = desktop.getCurrentFrame().getController().getModel();
if (!xModel?.queryInterface(zetajs.type.interface(css.text.XTextDocument))) {
xModel = desktop.loadComponentFromURL(
'file:///android/default-document/example.odt', '_default', 0, []);
}const xText = xModel.getText();
const xParaEnumeration = xText.createEnumeration();
for (const xParagraph of xParaEnumeration) {
const color = Math.floor(Math.random() * 0xFFFFFF);
xParagraph.setPropertyValue("CharColor", color);
}Some examples come with a package.json and can be run according to their README.md with npm. The other examples just need to put into a webserver with the following HTTP headers set.
Cross-Origin-Opener-Policy "same-origin"
Cross-Origin-Embedder-Policy "require-corp"
Add this line right before </body> in qt_soffice.html and replace EXAMPLE_FILE.js with the example you choose.
Then add the mentioned files to the webroot.
<script type="text/javascript">Module["uno_scripts"] = ['zeta.js', 'EXAMPLE_FILE.js']</script>
One way to run some of the provided example and test code is to serve those files next to qt_soffice.html, along with some include.js that looks like
Module.uno_scripts = [
'zetajs/source/zeta.js',
'zetajs/test/smoketest.js',
'zetajs/examples/simple.js'];
(or whatever the paths where you serve them, relative to qt_soffice.html; zeta.js always needs to come first), and to build LOWA with an EMSCRIPTEN_EXTRA_SOFFICE_PRE_JS=/path/to/include.js configuration option (e.g., as a line in autogen.input), with /path/to adapted accordingly. (The test/smoketest.js code requires a LibreOffice configured with --enable-dbgutil to have the org.libreoffice.embindtest UNOIDL entities available.)
By default the exmaples load a precompiled ZetaOffice from https://cdn.zetaoffice.net/zetaoffice_latest/
You may have a look into the respective config.sample.js file of each demo to use another WASM build. You may compile an own LOWA build. There the folder workdir/installation/LibreOffice/emscripten/ will contain the files for the webroot. If the host the WASM binary on another origin then the example code you will need to set a CORS header.
First off, please search existing issues first, before filing a new one (see search on github).
If you think you've found a security problem, feel free to contact one of the project maintainers in private, for responsible disclosure.
For any LibreOffice questions (code, api, features), you'll find us on the LibreOffice IRC channel - changes to LibreOffice core then go through TDF's development process and gerrit code review system.
For changes to the zetajs library, just raise a pull request here, and make sure you've got permission to contribute your changes under the MIT license. For that, we use the Developer Certificate of Origin (DCO):
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
When submitting a pull request, to make this certification please therefore add a sign-off line to your commits:
Signed-off-by: Random J Developer <random@developer.example.org>
Use your real name (sorry, no pseudonyms or anonymous contributions).
This project is tested with BrowserStack.