Kexi/Porting to Qt&KF 5

Note

Draft. Based on notes from the Calligra 2014 Sprint. Each step leads to compiling (running?) state.
Started by jstaniek (talk) 19:06, 7 July 2014 (CET).

1. Port Predicate lib to Qt 5
2. Move koproperty lib to a separate repo, make it Qt-only and port to Qt5
3. Move koreport lib to a separate repo, make it Qt-only and port to Qt 5
   1. Remove scripting or port scripting?
4. Port Kexi (without KexiDB/calligradb, reporting, KoReport) to Qt 5 and port Kexi to Predicate and the new koproperty/koreport
   1. Reimplement report scripting using a simple QtScript solution to keep backward compatibility with Kexi 2
   2. Remove then unused calligradb lib and parts of KexiDB lib
5. Improve Kexi stability after porting
6. -- Kexi 3.0 release here --
7. Make koreport lib dependent on Predicate and remove code/API that becomes redundant (e.g. KoReportData)
8. Add a new QtScript-based scripting module
9. Use the module in Kexi Reports too, keeping backward compatibility with Kexi 2 scripting (add unit tests before porting to be very sure that compatibility is kept)

Rules

• Use git scratch repos to avoid stress with buildbreaks
• Synchronize with (boud's?) branch of the Qt5 port
• Based on "Porting notes" below, keep porting of one aspect in one commit to simplify reviews
• Use the reviewboard for reviews
• Use kde-dev-scripts.git porting scripts, in particular
• convert-to-cmake-automoc.pl

TODO...

Notes and Status

TODO: details will go here

Predicate

It's a lib, so use the framework template (see Links).

Links

• Tasks at todo.kde.org (KDE Identity needed), public read-only view
• Framework repository template - use for creating new framework

Docs

• KF5: Porting Notes
• KF5 API docs
• Frameworks 5 build instructions

Background

• Notes from the 2014 Sprint Meeting