Jump to content

Digikam/CodingSprint2014: Difference between revisions

From KDE Community Wiki
Line 6: Line 6:


*KF5/Qt5 port status
*KF5/Qt5 port status
** libkexiv2 : done, still use KDE4Support, git branch frameworks
** libkexiv2 : done, still use KDE4Support, git branch frameworks
** libkdcraw : done excepted ThreadWeaver based classes, still use KDE4Support, git branch frameworks. 2 solutions : use new ThreaWearver API, or use QFuture + QThread API instead
** libkdcraw : done excepted ThreadWeaver based classes, still use KDE4Support, git branch frameworks. 2 solutions : use new ThreaWearver API, or use QFuture + QThread API instead
Line 14: Line 15:
** digiKam : todo
** digiKam : todo


Link to port documentation :
*Link to documentation to port code


- [https://community.kde.org/Frameworks/Porting_Notes KF5 port]
- [https://community.kde.org/Frameworks/Porting_Notes KF5 port]

Revision as of 07:04, 16 October 2014

KDE Graphics Coding Sprint 2014

The KDE Graphics coding sprint 2014 will take place at Berlin, Germany, from november 14h to 16th 2014.

Common Topics for Discussion and Coding

  • KF5/Qt5 port status
    • libkexiv2 : done, still use KDE4Support, git branch frameworks
    • libkdcraw : done excepted ThreadWeaver based classes, still use KDE4Support, git branch frameworks. 2 solutions : use new ThreaWearver API, or use QFuture + QThread API instead
    • libkipi : todo
    • libkface : todo
    • libkgeomap : todo
    • Kipi-plugins : todo
    • digiKam : todo
  • Link to documentation to port code

- KF5 port

- Qt5 port

- ECM - Extra CMake Module