Kexi/Porting to Qt&KF 5: Difference between revisions
< Kexi
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]]) | 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).
- 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, reporting, KoReport) to Qt 5 and port Kexi to Predicate and the new koproperty/koreport
- Porting report scripting to 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