On 17 May 2012 07:40, Ankit Jain <ankit_1988ma...@yahoo.co.in> wrote:
> >I want to remove Qt 4 entirely while building calligra as I don't want > > any UI related thing that > >Qt supports and also I don't want to open any document-means I don't want > > to launch >calligra words, stage or anything. > > >I just want to use the calligraconverter utility and use it for document > > conversion. > >Is there any way to build calligra in this manner? > >My main purpose is to reduce the size so that I can port it to an android > > device as my > >main use is to only use calligraconverter utility. Dear Ankit, Qt 4 is not enough modular to let stripping its QtGui library. This is because certain fundamental Qt classes that are used in any Calligra app come from QtGui. One example is QColor. Reportedly, Qt 5 will be better in this area and Calligra will benefit here. As for the stronger request - removing Qt 4 entirely - I guess this won't be supported in entire Calligra. Should we have dedicated contributors and then maintainers, at least filters could be made C++-only, or like WebKit - offered in Qt and C++ versions. There's some theoretical gain in reducing dependencies for filters and the converter (getting more developers on board seems to be the most attractive to me) but I doubt it's true for the rest of Calligra. Please note that the non-visual frameworks of Calligra are already consisted of almost Qt-only code (I like this aspect a lot). And such Qt-only code is much more compact in terms of dependencies than anything you see the closest competitor, i.e. in LibreOffice. -- regards / pozdrawiam, Jaroslaw Staniek http://www.linkedin.com/in/jstaniek Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org) KDE Software Development Platform on MS Windows (windows.kde.org) _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
