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

From KDE Community Wiki
mNo edit summary
No edit summary
Line 1: Line 1:
Draft. Each step leads to compiling (running?) state. Started by [[User:Jstaniek|jstaniek]] ([[User talk:Jarosław|talk]]) 19:06, 7 July 2014 (CET).
Draft. Based on [http://mail.kde.org/pipermail/calligra-devel/2014-July/011603.html notes] from the [[Calligra/Meetings/Spring_2014_Sprint|Calligra 2014 Sprint]]. Each step leads to compiling (running?) state.  


# Port Predicate lib to Qt 5
# Port Predicate lib to Qt 5
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
Started by [[User:Jstaniek|jstaniek]] ([[User talk:Jarosław|talk]]) 19:06, 7 July 2014 (CET).

Revision as of 20:43, 9 July 2014

Draft. Based on notes from the Calligra 2014 Sprint. Each step leads to compiling (running?) state.

  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, reporting, KoReport) to Qt 5 and port Kexi to Predicate and the new koproperty/koreport
    1. Porting report scripting to 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

Started by jstaniek (talk) 19:06, 7 July 2014 (CET).