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

List:       kde-panel-devel
Subject:    [Panel-devel] Superkaramba Qt4 Port
From:       Vinay Khaitan <vkhaitan () gmail ! com>
Date:       2005-09-01 3:39:46
Message-ID: 56c53477050831203957ecfd64 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi people,

[mX] told me that superkaramba port has not happened and it doesn't compile 
with qt4, so I can help with it.
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).
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.
But Half of that was already done. If any one is interested in that, get it 
from
http://k.domaindlx.com/vkhaitan/superkaramba.tar.bz2 .
files ported are 

bar.o cpusensor.o imagelabel_python.o memsensor.o programsensor.o 
sensorparams.o textfilesensor.o
bar_python.o datesensor.o karamba.o meter.o richtextlabel.o sensorsensor.o 
textlabel.o
clickarea.o disksensor.o karambarootpixmap.o meter_python.o 
richtextlabel_python.o showdesktop.o textlabel_python.o
clickmap.o graph.o karambasessionmanaged.o networksensor.o rsssensor.o 
taskmanager.o uptimesensor.o
(35 files)

(put .cpp instead of .o)

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.

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.
Thanks
Vinay Khaitan

[Attachment #5 (text/html)]

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&nbsp; 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&nbsp;&nbsp;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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;cpusensor.o&nbsp;&nbsp;
 imagelabel_python.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;memsensor.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;programsensor.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 sensorparams.o&nbsp;&nbsp;textfilesensor.o</span><br style="font-family: courier \
new,monospace;"><span style="font-family: courier \
new,monospace;">bar_python.o&nbsp;&nbsp;&nbsp;&nbsp; \
datesensor.o&nbsp;&nbsp;karamba.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp \
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;meter.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
&nbsp;&nbsp;&nbsp;&nbsp;richtextlabel.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 sensorsensor.o&nbsp;&nbsp;textlabel.o</span><br style="font-family: courier \
new,monospace;"><span style="font-family: courier \
new,monospace;">clickarea.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;disksensor.o&nbsp;&nbsp \
;karambarootpixmap.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;meter_python.o&nbsp;&nbsp; \
richtextlabel_python.o&nbsp;&nbsp;showdesktop.o&nbsp;&nbsp; \
textlabel_python.o</span><br style="font-family: courier new,monospace;"><span \
style="font-family: courier \
new,monospace;">clickmap.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
graph.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
karambasessionmanaged.o&nbsp;&nbsp;networksensor.o&nbsp;&nbsp;rsssensor.o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 taskmanager.o&nbsp;&nbsp; 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>



_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


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