Kexi/Porting to Qt&KF 5: Difference between revisions
< Kexi
(→Links) |
(→Links) |
||
Line 13: | Line 13: | ||
# Add a new QtScript-based scripting module | # 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 | ||
==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== | ==Links== | ||
*[https://todo.kde.org/?controller=board&action=show&project_id=7 Tasks at todo.kde.org] (KDE Identity needed), [https://todo.kde.org/?controller=board&action=readonly&token=11341e5f4059520ee1abdef93c530123499f6b73c1725c56c6999e750859 public read-only view] | *[https://todo.kde.org/?controller=board&action=show&project_id=7 Tasks at todo.kde.org] (KDE Identity needed), [https://todo.kde.org/?controller=board&action=readonly&token=11341e5f4059520ee1abdef93c530123499f6b73c1725c56c6999e750859 public read-only view] | ||
*[[Frameworks/Porting Notes|KF5: Porting Notes]] | *[[Frameworks/Porting Notes|KF5: Porting Notes]] |
Revision as of 18:51, 13 August 2014
- 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
- 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
- Reimplement report scripting using a simple QtScript solution to keep backward compatibility with Kexi 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
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