office-gobmx/slideshow
Stephan Bergmann 5f2bc59ee9 Drop remaining boost/shared_pointer debug functionality
...most of which had already been removed with
4e35473790 "remove boost/shared_ptr foo".
4c657f5a1a "Properly #if these debug hooks" had
noted that slideshow/source/engine/smilfunctionparser.cxx "still indirectly
includes boost/scoped_ptr.hpp via. boost/spirit", but lets assume that nobody
actually relied on this functionality (and however it would actually work in
practice).

Change-Id: Ib8ccfcd8019d7b03b138aee1ac026a2f7bd5d402
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165082
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <stephan.bergmann@allotropia.de>
2024-03-21 12:28:32 +01:00
..
inc/pch simplify and modernise ScopedBitmapAccess 2023-12-07 09:32:14 +01:00
opengl
qa UnoApiTest::loadFromURL -> UnoApiTest::loadFromFile 2024-01-03 07:51:28 +01:00
source Drop remaining boost/shared_pointer debug functionality 2024-03-21 12:28:32 +01:00
test c++20: use std::erase(_if) instead of std::remove(_if)+erase (part 11) 2023-11-19 13:41:30 +01:00
util
CppunitTest_slideshow.mk
CppunitTest_slideshow_engine.mk CppunitTest_slideshow_engine: inherit from UnoApiTest 2022-11-22 12:49:06 +01:00
IwyuFilter_slideshow.yaml
Library_OGLTrans.mk Drop remaining boost/shared_pointer debug functionality 2024-03-21 12:28:32 +01:00
Library_slideshow.mk Drop remaining boost/shared_pointer debug functionality 2024-03-21 12:28:32 +01:00
Makefile
manifest.txt
Module_slideshow.mk tdf#149969 slideshow: handle loop from the animation of a media shape 2022-09-02 12:30:49 +02:00
Package_opengl.mk
README.md

Impress Slideshow Engine

3D Transitions

The 3D transitions are slideshow transition engine using OpenGL and are located in slideshow/source/engine/OGLTrans/. They were initially written by GSOC student Shane.M.Mathews. Radek has later polished the code a bit, added few new 3D transitions, added infrastructure for vertex and fragment shaders. Wrote few transitions with fragment shader too.

Physics Animation Effects

Physics animation effects are simulated by external 2d physics engine library Box2D. They don't directly call Box2D functions but instead use the wrapper in:

  • slideshow/source/inc/box2dtools.hxx
  • slideshow/source/engine/box2dtools.cxx

The wrapper has two corresponding classes to manage the Box2D world and Box2D bodies.

When a physics animation starts, a Box2DWorld is initiated and populated with every shape that is part of the foreground (which are shapes that do not belong to the master slide and not a background shape).

After creation until the end of the slide (not the whole slideshow) the Box2D World isn't destroyed and reused. But the bodies that represent the shapes in the slide get destroyed when there's a point in time that there's no physics animation in progress. And recreated when another physics animation starts.

If there are multiple physics animations in parallel only one of them takes the role of stepping through the simulation.

If there are other animation effects that go in parallel which change the shape position, rotation, or visibility - they also report the change to Box2DWorld. These updates are collected in a queue in Box2DWorld and processed before stepping through the simulation. To achieve convincing results these updates are performed by setting the Box2D body's linear velocity or angular velocity instead of setting directly it's position or rotation.