<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial">I agree, I'm guessing that's already in the works, I
hope some of the talk will be done at planned meeting times, and I hope
the designs and discussions will be logged.<br>
<br>
I'm a dreamer.<br>
</font><br>
Vinay Khaitan wrote:
<blockquote cite="mid56c53477050831203957ecfd64@mail.gmail.com"
type="cite">Hi people,<br>
<br>
[mX] told me that superkaramba port has not happened and it doesn't
compile with qt4, so I can help with it.<br>
I
started doing the same. Ran qt3to4 porting tool and then using
Qt3Support layer, I started changing code manually to make it
compile(with keeping an eye over changed KdelIbs api like
kdatastream.h).<br>
Then I happen to talk to werr in #superkaramba and he told me
that there is no use of porting it to Qt4 so, as most of it will be
rewritten, when integrating with plasma. So I finally left doing that.<br>
But Half of that was already done. If any one is interested in that,
get it from<br>
<a href="http://k.domaindlx.com/vkhaitan/superkaramba.tar.bz2">http://k.domaindlx.com/vkhaitan/superkaramba.tar.bz2</a>
.<br>
files ported are <br>
<br>
<span style="font-family: courier new,monospace;">bar.o cpusensor.o
imagelabel_python.o memsensor.o programsensor.o
sensorparams.o textfilesensor.o</span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">bar_python.o
datesensor.o karamba.o meter.o richtextlabel.o
sensorsensor.o textlabel.o</span><br
style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">clickarea.o disksensor.o karambarootpixmap.o meter_python.o
richtextlabel_python.o showdesktop.o
textlabel_python.o</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">clickmap.o
graph.o
karambasessionmanaged.o networksensor.o rsssensor.o
taskmanager.o uptimesensor.o</span><br>
(35 files)<br>
<br>
(put .cpp instead of .o)<br>
<br>
I
found when talking with werr, that Most of the trouble now is that
Design is not finalized. We dont know what will remain, what will be
ousted. The previoius task I left because of the same reason, because
Design would be different.<br>
<br>
In my personal opinion, after akademy is finished, we should first make
a clear outline of design of kicker,kdesktop,superkaramba
integration(possibly with full flow chart and tentative class
hierarchy). It will help people like me to understand what developers
have things in mind.<br>
Thanks<br>
Vinay Khaitan<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Panel-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Panel-devel@kde.org">Panel-devel@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/panel-devel">https://mail.kde.org/mailman/listinfo/panel-devel</a>
</pre>
</blockquote>
</body>
</html>