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

List:       koffice-devel
Subject:    Re: Using KChart
From:       David Faure <faure () kde ! org>
Date:       2007-01-19 9:26:17
Message-ID: 200701191026.17701.faure () kde ! org
[Download RAW message or body]

On Thursday 18 January 2007 11:35, Boudewijn Rempt wrote:
> I was for a separate module mainly because accepting stuff in kdelibs is a 
> long process, longer than simply creating a new toplevel module.

Wow. I beg to differ. A new toplevel module means everyone has to change his build scripts
and all (including the dashboards, coverity, etc.). That's a much more tedious process 
for everyone than importing something into kdelibs. If *that* is the reason for a 
new toplevel, then it's a wrong reason.
And the reason importing something into kdelibs needs discussion is that since we'll keep
BC on it for the whole 4.x timeframe, it has to have a good API. But that's true for kdepimlibs
and for any new kdefoolibs that we create, if we do! The BC requirements are the same...
But, yes, the decision process is still lacking on this. However more apps need it, more reason
we have to have it in kdelibs or some kdefoolibs, as was said.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
_______________________________________________
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]