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

List:       kde-core-devel
Subject:    Re: "Cornelius's grand plan" - Merging KDElibs into Qt
From:       Matt Williams <lists () milliams ! com>
Date:       2010-10-31 12:04:28
Message-ID: AANLkTi=QVC3oeHFT3kH6GY86tex3izz9FUSjWi6k5R=o () mail ! gmail ! com
[Download RAW message or body]

On 31 October 2010 11:53, John Tapsell <johnflux@gmail.com> wrote:
> On 31 October 2010 11:33, Mark Kretschmann <kretschmann@kde.org> wrote:
>> Hey all,
>>
>> after reading the whole thread that started with Chani's mail ("why
>> kdelibs?"), I think the noise level has become a bit too much there.
>> Cornelius had proposed this rather daring idea:
>>
>> http://lists.kde.org/?l=kde-core-devel&m=128842761708404&w=2
>
>
> Sounds great.  This should probably be done by picking a specific
> technology in KDE, and adapting it and merging it to work in Qt.
>
> A wonderful place to start would be kioslaves imho.  This is something
> which has a real advantage, is relatively self-contained, and would
> provide a big advantage.  Possibly it needs to be merged more with the
> Qt API though.

So, if we decided that we wanted to merge KIO slaves into Qt, what
would the steps we go through be? If we're going to be doing this with
a number of classes we need to have a process which ensures that the
code is Qute enough, KDE still compiles against it (with minimal/no
code changes) etc.

Obviously things like this will be BIC? Even with wrapper classes in
KDE? So I guess we can't just jump and do this for KDE 4.6 -- it's
going to force us into taking some very big steps like jumping to KDE5
or at least boosting the soversion of the libs.

-- 
Matt Williams
http://milliams.com

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