[Panel-devel] Superkaramba Qt4 Port

[Vinay Khaitan]

But anyway, I learned by this excercise about porting troubles and solutions 
:) as I learned some kicker internals with previous task.

On 8/31/05, Vinay Khaitan <vkhaitan at gmail.com> wrote:
> 
> 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
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20050901/6b30f05b/attachment.html