In port, i have use QT4/KDE4 API we it possible to remplace old QT3/KDE3 API.<br><br>But this job can be long to do and to test. Like no kipi hosts have been ported yet under KDE4, we cannot test plugins port. So i recommend to delay all complex code port (especially about GUI/widgets part) to use QT3/KDE3 -> QT4/KDE4 compatibility port lib (Q3... and K3... class).
<br><br>To resume : <br><br>- all simple QT3/KDE3 -> QT4/KDE4 port can be done as well<br>- all complex QT3/KDE3 -> QT4/KDE4 port will use temporally Q3.../K3... transition class.<br><br>Gilles<br><br><br><div><span class="gmail_quote">
2007/6/13, Vardhman Jain <<a href="mailto:vardhman@gmail.com">vardhman@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Does a port mean that we remove the QT 3 specific APIs which are not deprecated in QT 4 by using some similar QT 3 methods or by we are free to use QT 4 only APIs to replace them meaning the code won't compile without KDE/QT 4 ? and is therefore not backward compatible
<br><br><br>Vardhman<br><div><div><span class="e" id="q_11323de87e435280_1"><span class="gmail_quote">On 6/12/07, <b class="gmail_sendername">Gilles Caulier</b> <<a href="mailto:caulier.gilles@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
caulier.gilles@gmail.com</a>> wrote:</span></span></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span class="e" id="q_11323de87e435280_3">
<br><br><div><div><span><span class="gmail_quote">2007/6/12, Angelo Naselli <<a href="mailto:anaselli@linux.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
anaselli@linux.it</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alle marted́ 12 giugno 2007, Gilles Caulier ha scritto:<br>> 2007/6/12, Angelo Naselli <<a href="mailto:anaselli@linux.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">anaselli@linux.it</a>
>:<br>> ><br>> > Alle luned́ 11 giugno 2007, Gilles Caulier ha scritto:
<br>> > > and now JPEGLossLess kipi-plugin is ported to KDE4...<br>> > Great, anyway i'd like to discuss the plugins category.<br>> > We can't change them now or, I believe, hosts applications like digikam,
<br>> > should be patched for that. But in kde4 they should.<br>> > I mean printwizard maybe it's not an export plugin, even Renchi said it<br>> > into a bug report,<br>> > moreover ipod export could be moved to export category instead. Maybe some
<br>> > cotegories<br>> > are useless or should be renamed.<br>> > So please any opinion here is welcome.<br>><br>><br>> I propose to change category of plugins in KDE3 _without_ add new<br>> categories. Like this host do not be recompiled.
<br>hmm if I move printwizard from export to tools or images for instace,<br>don't you have to patch digikam to load that and add to digikam's<br>customized menus?<br>I'm sure it's not a gwenview problems since they are inserted by category into
<br>Plugins menu, but digikam is different am I wrong?</blockquote></span></div><div><br>no, it's the same. Look in digikam/digikam/digikamapp.cpp for details<br><br>Gilles</div></div><br>
<br></span></div>_______________________________________________<br>Kde-imaging mailing list<br><a href="mailto:Kde-imaging@kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Kde-imaging@kde.org
</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-imaging" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://mail.kde.org/mailman/listinfo/kde-imaging</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://vardhman.blogspot.com</a><br>
<br>_______________________________________________<br>Kde-imaging mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Kde-imaging@kde.org">Kde-imaging@kde.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://mail.kde.org/mailman/listinfo/kde-imaging" target="_blank">
https://mail.kde.org/mailman/listinfo/kde-imaging</a><br><br></blockquote></div><br>