https://bugs.kde.org/show_bug.cgi?id=383715

Stefan Brüns <stefan.bru...@rwth-aachen.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WAITINGFORINFO
             Status|UNCONFIRMED                 |NEEDSINFO

--- Comment #1 from Stefan Brüns <stefan.bru...@rwth-aachen.de> ---
Ok, I have looked into the presentation code, and I am not quite sure which is
the best way forward:

1. Just port the code to QOpenGLFunctions [1], fixing any differences between
GL and GLES and be done with it.
2. Do a complete overhaul of the code and port it to QML

1. would fix the imminent problem with GLES, but would not fix the various
problems visible in the current code:

- There are 3 different widgets (non-GL, GL, Ken Burns( with large amounts of
duplicate^Wtrippled code
  a) event handling
  b) widget constructor
  c) ...
- feature set is different, e.g. Ken Burns lacks any overlays (filename,
comments)
- Overlay rendering between non-GL and GL is different
- Overlay aspect ratio is wrong for GL when using reduced resolution
- Overlay text antialiasing is broken
- Ken Burns uses blurred images (image is loaded at screen resolution, but the
upscaled and translated)

My proposal would be to port the presentation widgets to QML, while keeping the
PresentationLoader and PresentationContainer classes:
1. Code a presenter capable to show a series of images
2. Add text overlays
3. Add back all effects, one by one

If this approach seems acceptable, I would start a branch therefor. Timeline
would be 1 month for the first step (1.), one week for (2.) and about 2 effects
per week thereafter.

[1] http://doc.qt.io/qt-5/qopenglfunctions.html

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to