[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: Mark <markg85 () gmail ! com>
Date: 2010-10-31 12:20:32
Message-ID: AANLkTik5iDU1LOZ_=W-hFYwFb-pexemJf_g3OXgkJ4g4 () mail ! gmail ! com
[Download RAW message or body]
On Sun, Oct 31, 2010 at 12:33 PM, 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
>
>
> It's a very controversial idea. However, I think it is so refreshing
> that it deserves some more thought. Personally, I think the idea is
> great, if we can overcome some of the obvious road blocks. I would
> love to read some honest and direct thoughts from you guys.
>
>
> What do you think about it?
>
> --
> Mark Kretschmann
> Amarok Developer, Software Engineer at KO GmbH
> Fellow of the Free Software Foundation Europe
> http://amarok.kde.org - http://www.fsfe.org - http://www.kogmbh.com
>
Oh wow, some seriously big things are going on here. Anyway, i don't see all
KDE's parts be "merge-able" in Qt the way they are now. Lets take for
example the status bar.. The one Dolphin and Konqueror use is quite a bit
different from QStatusBar thus either QStatusBar has to be changed
or Dolphin and Konqueror have to change.
But i wonder if "merging" is the way to go.. since Qt itself wants to be
more modular : http://labs.qt.nokia.com/2010/10/26/qt-is-going-modular/ it
might be a good idea to consider splitting kdelibs into Qt modules to get
closer with Qt.. some example modules would then be:
Kio - KDE IO handling
KUi - KDE UI widgets
K... - ...
It might be needed that KUi parts that are fairly close to their Qt
counterparts get merged in QtGui and others that are just to different stay
in a separate module (KUi).
And if it are all Qt modules then the move from module to Qt core
(where appropriate) seems relatively easy.
Besides i think the step from the current kdelibs to Qt modules is a lot
easier then going for a merge.
Just my thoughts.. I certainly keep an eye on this thread ^_^
[Attachment #3 (text/html)]
<div class="gmail_quote">On Sun, Oct 31, 2010 at 12:33 PM, Mark Kretschmann <span \
dir="ltr"><<a href="mailto:kretschmann@kde.org">kretschmann@kde.org</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">
Hey all,<br>
<br>
after reading the whole thread that started with Chani's mail ("why<br>
kdelibs?"), I think the noise level has become a bit too much there.<br>
Cornelius had proposed this rather daring idea:<br>
<br>
<a href="http://lists.kde.org/?l=kde-core-devel&m=128842761708404&w=2" \
target="_blank">http://lists.kde.org/?l=kde-core-devel&m=128842761708404&w=2</a><br>
<br>
<br>
It's a very controversial idea. However, I think it is so refreshing<br>
that it deserves some more thought. Personally, I think the idea is<br>
great, if we can overcome some of the obvious road blocks. I would<br>
love to read some honest and direct thoughts from you guys.<br>
<br>
<br>
What do you think about it?<br>
<font color="#888888"><br>
--<br>
Mark Kretschmann<br>
Amarok Developer, Software Engineer at KO GmbH<br>
Fellow of the Free Software Foundation Europe<br>
<a href="http://amarok.kde.org" target="_blank">http://amarok.kde.org</a> - <a \
href="http://www.fsfe.org" target="_blank">http://www.fsfe.org</a> - <a \
href="http://www.kogmbh.com" target="_blank">http://www.kogmbh.com</a><br>
</font></blockquote></div><br><div>Oh wow, some seriously big things are going on \
here. Anyway, i don't see all KDE's parts be "merge-able" in Qt the \
way they are now. Lets take for example the status bar.. The one Dolphin and \
Konqueror use is quite a bit different from QStatusBar thus either QStatusBar has to \
be changed or Dolphin and Konqueror have to change.</div>
<div><br></div><div>But i wonder if "merging" is the way to go.. since Qt \
itself wants to be more modular : <a \
href="http://labs.qt.nokia.com/2010/10/26/qt-is-going-modular/">http://labs.qt.nokia.com/2010/10/26/qt-is-going-modular/</a> \
it might be a good idea to consider splitting kdelibs into Qt modules to get closer \
with Qt.. some example modules would then be:</div>
<div>Kio - KDE IO handling</div><div>KUi - KDE UI widgets</div><div>K... - \
...</div><div><br></div><div>It might be needed that KUi parts that are fairly close \
to their Qt counterparts get merged in QtGui and others that are just to different \
stay in a separate module (KUi).</div>
<div><br></div><div>And if it are all Qt modules then the move from module to Qt core \
(where appropriate) seems relatively easy.</div><div>Besides i think the step from \
the current kdelibs to Qt modules is a lot easier then going for a merge.</div>
<div><br></div><div>Just my thoughts.. I certainly keep an eye on this thread \
^_^</div><meta http-equiv="content-type" content="text/html; charset=utf-8"><meta \
http-equiv="content-type" content="text/html; charset=utf-8">
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic