[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: koreports dependencies (was koffice)
From:       Adam Pigg <piggz1 () gmail ! com>
Date:       2010-02-28 15:05:33
Message-ID: 4b8a863e.0f67f10a.2614.606e () mx ! google ! com
[Download RAW message or body]

Thomas Zander wrote:

> On Saturday 27. February 2010 14.02.43 Cyrille Berger wrote:
>> On Friday 26 February 2010, Adam Pigg wrote:
>> > SVN commit 1096573 by piggz:
>> >
>> > Move koreport to /libs (used by kexi and kplato)
>> > Fix kexi and kplato builds
>> 
>> and breaks build when kchart is disabled. The dependency between koreport
>>  and other modules (especially applications) needs to be removed.
> 
> Talked a bit with Adam on IRC and he asked me to write an email with a
> summary In base; libraries (in koffice/libs) can not depend on stuff
> outside of the libs.
> 
> 
> * the CMakeFile.txt has a -DHAVE_KWORD which luckily seems to be unused.
> But should be removed.
> * The KoReportKSpreadRenderer class depends on the kspreadcommon library
> in order to allow reports to be written to ods.
> This should be changed to get rid of the dependency. I think the ods
> fileformat is pretty simple and maybe just using libkoodf and
> QXmlStreamWriter would do the trick.
Ive looked at the file format for ODS, and its pretty simple, i dont suppose 
this will take much work.
> * It depends on kdchart. Which means it turned into GPL and the libs in
> koffice/libs should all be LGPL. It also can't depend on it because
> kdchart is outside of kofficelibs.
> On IRC I suggested to move the classes that depend on kdchart for
> KOffice2.2 somewhere else and come up with a better solution for 2.3 or
> later.
Licensing issues arent my forte, ideally i'd probably use KChart for 
charting, but would that have the same issues?
> 
> I also notice that KoReportKSpreadRenderer looks a lot like KoShape.
> KoShape obviously has more features, but it does look to me like someone
> should do the research to see if koreports can't use flake and get all
> these issues solved much in the same way that flake solved these issues
> for the rest of KOffice.
> 
Open for patches :), the more devs the better!

> Adam, JS, Dag; suggestions please :)
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]