I want to add something to the "Stuff that can be removed" part of the
porting plan.
plugins/formulashape/ - I will write a new formula plugin based on libmathview.
flow/ - I want to re-write calligraflow based on Karbon libraries.
Yue
2015-03-21 13:56 GMT-07:00 Friedrich W. H. Kossebau :
> Am S
Two weeks ago or so Inge put it nicely on #calligra IMHO:
There are 3 phases of the port:
1. Initial port of buildsystem (done now, thanks Boud)
2. Readding everything to build (minimal port, using kdelibs4support)
3. Porting away from kdelibs4support and other deprecated stuff
So seems in the
Am Samstag, 21. März 2015, 11:01:27 schrieb Boudewijn Rempt:
> After a lot of frustration, koplugin now builds and links. That means that
> we can start porting the rest of the libraries.
Boud, thanks for wading through all that frustration. You know we all are
thankful for you having picked up t
On Saturday March 21 2015 11:03:21 Boudewijn Rempt wrote:
>doesn't support sharing the same area across different libraries, which is
>something we do a lot in Calligra. We have three options: remove all the
>areas (as I did in koplugin), make areas per library or create a new
Oh, another note:
the kde-dev-scripts allow us to port kDebug(AREA) to qcDebug() _but_ it
doesn't support sharing the same area across different libraries, which is
something we do a lot in Calligra. We have three options: remove all the
areas (as I did in koplugin), make areas per library or
After a lot of frustration, koplugin now builds and links. That means that
we can start porting the rest of the libraries. I'll begin with pigment.
Here are my notes:
Documentation:
http://www.proli.net/2014/06/21/porting-your-project-to-qt5kf5/
https://community.kde.org/Frameworks/Porting_Not
