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

From KDE Community Wiki
(Created page with "Draft. Each step leads to compiling (running?) state. Stered by ~~~~. # Port Predicate lib to Qt 5 # Move koproperty lib to a separate repo, make it Qt-only and port to Qt5 #...")
 
No edit summary
Line 1: Line 1:
Draft. Each step leads to compiling (running?) state. Stered by [[User:Jarosław|jstaniek]] ([[User talk:Jarosław|talk]]) 23:26, 7 July 2014 (UTC).
Draft. Each step leads to compiling (running?) state. Stered by [[User:Jarosław|jstaniek]] ([[User talk:Jarosław|talk]]) 19:06, 7 July 2014 (CET).


# Port Predicate lib to Qt 5
# Port Predicate lib to Qt 5

Revision as of 23:27, 7 July 2014

Draft. Each step leads to compiling (running?) state. Stered 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, 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