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

List:       kde-core-devel
Subject:    Re: PieChart widget
From:       "=?UTF-8?Q?Rafael_Fern=C3=A1ndez_L=C3=B3pez?=" <ereslibre () gmail ! com>
Date:       2007-09-21 10:33:10
Message-ID: 93f85fee0709210333sc92705q6a9ce5d192e78f10 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (text/plain)]

Hi Jos and all,

As this widget cannot be introduced in kdelibs for 4.0 and we have to copy
it into Dolphin anyway it makes no difference here, but my idea is slightly
different from yours on "do not duplicate work".

We are libraries. KDE has powerful libraries. Our aiming (among others) is
to provide our libraries as powerful as we can (as well as complete as we
can) without the need of relying on external stuff.

Qt offers widgets. KDE offers widgets. It doesn't make any sense to me the
"code duplicating" of having a KDChart copy on each program that wants to
draw a chart. That is nosense.

Apart from the problem that this implies. Let's suppose KOffice, Dolphin and
Krita use KDChart. So they both 3 have a copy of KDChart on their folders
(code duplicating). Even worse, imagine KDChart is updated with a several
security problem or a really nice feature, or something that makes it appear
very very different: inconsistent desktop if KOffice update their copy and
Krita or Dolphin doesn't.

From my point of view this is not a work duplicating, but your proposal is a
code duplicating, that is always really bad.

If you are developing an external app and you don't find a chart class on
kde libs, I will find it fine to use KDChart for instance.


Bye,
Rafael Fernández López.

[Attachment #3 (text/html)]

Hi Jos and all,<br><br>As this widget cannot be introduced in kdelibs for 4.0 and we \
have to copy it into Dolphin anyway it makes no difference here, but my idea is \
slightly different from yours on &quot;do not duplicate work&quot;. <br><br>We are \
libraries. KDE has powerful libraries. Our aiming (among others) is to provide our \
libraries as powerful as we can (as well as complete as we can) without the need of \
relying on external stuff.<br><br>Qt offers widgets. KDE offers widgets. It \
doesn&#39;t make any sense to me the &quot;code duplicating&quot; of having a KDChart \
copy on each program that wants to draw a chart. That is nosense. <br><br>Apart from \
the problem that this implies. Let&#39;s suppose KOffice, Dolphin and Krita use \
KDChart. So they both 3 have a copy of KDChart on their folders (code duplicating). \
Even worse, imagine KDChart is updated with a several security problem or a really \
nice feature, or something that makes it appear very very different: inconsistent \
desktop if KOffice update their copy and Krita or Dolphin doesn&#39;t. <br><br>From \
my point of view this is not a work duplicating, but your proposal is a code \
duplicating, that is always really bad.<br><br>If you are developing an external app \
and you don&#39;t find a chart class on kde libs, I will find it fine to use KDChart \
for instance. <br><br><br>Bye,<br>Rafael Fernández López.<br>



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