What's new in KReport & KProperty & Predicate

[Jaroslaw Staniek]

Update:
- cmake build scripts for KProperty and KReport are largely following
the conventions of KF5 and e.g. KDiagram
- KProperty now uses CamelCase filenames and (mostly) the convention
of KProperty prefix for class names (so the KoProperty namespace is
removed)
- Consider KProperty are almost ready for placing in the final
repository. Example app in examples/ subdir works.
- part of the KReport is ported to use QLatin1String where needed,
also some includes are fixed; Adam is helping with this right now

TODO:
- more QLatin1String and include fixes for KReport
- port KReport to the new KProperty naming conventions
- some test app for KReport would help us to verify it without waiting
for Kexi to be ported

Feel free to test and report any ideas/issues.

On 3 April 2015 at 01:07, Jaroslaw Staniek <staniek at kde.org> wrote:
> Hi,
> There's a number of new commits in the temporary repos [0].
> A short update and proposed plans.
> Let's make them work, test them so they're not blockers for porting
> Kexi anymore.
>
> (we're assuming KF5 frameworks are installed from packages or built
> with the great kdesrc-build tool [1])
>
> KProperty:
> - builds and installs
> - includes changes from Adam [2]
> - includes all changes from calligra/2.9
> - headers install to include/KProperty
>
> KReport:
> - includes changes from Adam [3]
> - TODO: more build would work if "find_package(KProperty REQUIRED)" works
> - TODO: add the central CMakeLists.txt, like in KProperty, for now we
> have to build kreport/src/.
> - TODO: install headers to include/KReport
>
> Predicate:
> - not much recently, needs more patches ported from calligra/2.9,
> please help with this
> - soon also this [4]
>
> All three:
> - TODO: dig in their central CMakeLists.txt files to make them
> configure similarly to KF5 packages so line such as "find_package(....
> REQUIRED)" adds necessary include path for the users of the libs;
> volunteers needed here
> - TODO: once we have all three usable, porting scripts will be in use
> - Note: no calligra activities from the 'frameworks' branch of
> calligra affect these 3 libs because the 'frameworks' branch no longer
> contains their code (so no merges from 'frameworks' are expected, only
> small merges by hand for bugfixes from calligra/2.9)
>
> [0] https://community.kde.org/Kexi/Porting_to_Qt%26KF_5
> [1] https://community.kde.org/Frameworks/Building
> [2] https://git.reviewboard.kde.org/r/123038/
> [3] https://git.reviewboard.kde.org/r/123039/
> [4] https://git.reviewboard.kde.org/r/122015/
>
> --
> regards, Jaroslaw Staniek
>
> KDE:
> : A world-wide network of software engineers, artists, writers, translators
> : and facilitators committed to Free Software development - http://kde.org
> Calligra Suite:
> : A graphic art and office suite - http://calligra.org
> Kexi:
> : A visual database apps builder - http://calligra.org/kexi
> Qt Certified Specialist:
> : http://www.linkedin.com/in/jstaniek



-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek