Kexi/Porting to Qt&KF 5: Difference between revisions

Revision as of 21:01, 5 September 2014

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).

Port Predicate lib to Qt 5
Move koproperty lib to a separate repo, make it Qt-only and port to Qt5
Move koreport lib to a separate repo, make it Qt-only and port to Qt 5
1. Remove scripting or port scripting?
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
Improve Kexi stability after porting
-- Kexi 3.0 release here --
Make koreport lib dependent on Predicate and remove code/API that becomes redundant (e.g. KoReportData)
Add a new QtScript-based scripting module
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

TODO...

Status

TODO: details will go here

Links

Tasks at todo.kde.org (KDE Identity needed), public read-only view
KF5: Porting Notes

@@ Line 12: / Line 12: @@
 # Make koreport lib dependent on Predicate and remove code/API that becomes redundant (e.g. KoReportData)
 # Add a new QtScript-based scripting module
-# Use the module in Kexi Reports too, keeping backward compatibility with Kexi 2 scripting
+# 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==