[Kde-imaging] Any one documented the KDE 3 to KDE 4 port for a kipi-plugin

[Gilles Caulier]

I have annoted few links in KDE4PORT files from digiKam project to
help on port to KDE4/Qt4.

Look on the top of this file :

http://websvn.kde.org/trunk/extragear/graphics/digikam/KDE4PORT?revision=816535&view=markup

Note: Laurent Montel can process a lots of script to batch KDE4 port
in your KDE3 code. I recomend you to contact him by mail
(montel at kde.org) or IRC ("lmontel" - #kde-devel)

Gilles Caulier

2008/6/8 Marcel Wiesweg <marcel.wiesweg at gmx.de>:
>> Hi,
>>       Did someone document the steps taken for porting the kipi-plugin in
>> KDE 3 to KDE 4 ? I am looking for more like the best practices or
>> experience instead of the Options (which the QT website offers in the
>> Porting to QT 4 documentation).
>>
>> Do ppl generally modify the KDE 3 to make is as close to the porting
>> guidelines and then port it or its better to leave KDE 3 code as it is and
>> directly work on porting only for the new copy of the code that will go in
>> to KDE 4 directory ?
>
> I dont see so much you can change in KDE3 to prepare for KDE4; we usually
> copied the code to trunk, then ran the automatic tool, then made the
> necessary manual work to make it compile, then looked the the code works
> again, and then removed remaining Qt3Support classes.
> As to removing Qt3Support, this should be done ultimately, but it is not
> strictly necessary for some cases. For example, we still base our icon view
> in digikam on Q3 classes because a complete rewrite is planned for later, and
> view classes have changed a lot.
> The other example would be actions, the move to QAction is necessary and
> should be done while porting (maybe it doesnt compile without, dont know
> anymore)
>
> Marcel
>
>
>>
>>
>> Vardhman
>
>
> _______________________________________________
> Kde-imaging mailing list
> Kde-imaging at kde.org
> https://mail.kde.org/mailman/listinfo/kde-imaging
>