I have a build from online/engine. I can edit a presentation in Impress. However, I cannot run it. The according items in the menu are inactive. Is that a problem in my build, or is that something general?
Definitely general: the slideshow code has been removed, because it isn’t used by Online.
There is a whole separate JavaScript implementation somewhere under browser/
That’s too bad. It makes it harder to exchange code with LibreOffice.
PowerPoint has separate settings for animating SmartArt diagrams. Currently, these aren’t being processed. If you want to improve this, how could you test it during implementation?
If you follow the documentation at Build Collabora Office for Windows | Collabora Office - Community Page, you get the usual document edit UI and also you can start the slideshow using Slideshow → From Beginning on the notebookbar. Does that help?
1 Like
That means, I need a second clone with a different autogen.input and do the changes to online/engine there as well?
Why was running a slide show removed?
We are working to build both Collabora Office and Online out of the same source tree for Linux, and of course for Windows Collabora Office is the supported UX we are building.
Removing the legacy slideshow means we can drop multiple canvas implementations (many of them with differences in rendering), and unify on currently the tiled rendering - but soon the new vector-stream - which will use the browser to render much of the graphic pipeline. That shares code, reduces the amount of code, moves rendering cost into another thread (or process), and of course makes maintenance easier.
The browser rendered / vector-stream stuff may be a good way to integrate the animations that you’re looking at around SmartArt diagrams as we start to work on that more.
I hope that explains some of the rationale; there are big maintenance benefits to removing per-platform code and re-using the browser infrastructure that we want to capture.
Hi Regina, that was Noel & me removing the code there. Since it was unused for both Online and Desktop, as the animations / slideshow code is now pure TypeScript (it lives below browser/src/slideshow/*).
Having authored the original c++ version there many years ago, I have to say that a browser + JS or TS is simply a nicer, faster & less bothersome way to implement such an animation framework.