How to share KoUnit?

[Jaroslaw Staniek]

Hi,
For a good reason internal format of Kexi Report documents is modelled
after ODF specs. [0]
In particular units are. So in Calligra 2.x we started to use KoUnit
in libs/koreport and, by extension, in libs/koproperty.

Now it's not that easy after recent extracting both to KReport [1] and
KProperty [2] frameworks, respectively. For now both frameworks have a
copy of KoUnit, which is ugly and soon will be unusable because they
should share one.

Would you think it's time to start having a part of the ODF lib in a
separate repo. Who's going to maintain it?
>From the point of view of the entire suite, the above story isn't too important.

The issue of sharing the code between KProperty and KReport would be
solved by offering the shared classes in KProperty.
But interesting bit is then that Kexi would use these copies
(naturally, KoUnit renamed to something else, etc.) instead of the
originals from calligra/libs/.

Ideas?

PS: Similar challenge applies to KoLineStyleSelector, KoPageFormat,
KoDpi, KoRuler, KoViewConverter, KoZoomMode, KoZoomHandler.

[0] https://community.kde.org/Kexi/Plugins/Reports/Fileformat
[1] https://community.kde.org/Kexi/Porting_to_Qt%26KF_5#kreport
[2] https://community.kde.org/Kexi/Porting_to_Qt%26KF_5#kproperty

-- 
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