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

From KDE Community Wiki
No edit summary
Line 26: Line 26:


==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=d39ee567c32511a5f32e69054902b64a4118930be455b4cf7a9c7b83fe87 public read-only view]'''
*[https://lists.kde.org/?l=calligra-devel&m=140480621024543&w=2 Notes from the 2014 Sprint Meeting]
*[https://lists.kde.org/?l=calligra-devel&m=140480621024543&w=2 Notes from the 2014 Sprint Meeting]
*[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]]


[[Category:Kexi Porting]]
[[Category:Kexi Porting]]

Revision as of 11:51, 8 January 2015

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

TODO...

Status

TODO: details will go here

Links