[Kde-imaging] [RFC] moving to kde4

Gilles Caulier caulier.gilles at gmail.com
Tue Mar 6 15:34:45 CET 2007


Like Marcel said in digiKam ML, you can seen than for Amarok we have

- trunk == KDE4/QT4/Cmake
- stable == KDE3/QT3/autotools

Sound like we will port KDE4 implementation of kipi and co in trunk and
maintain KDE3 in stable branch.

Personally, when my computer will host KDE4/QT4 developement env., i will
start to port the shared library : libkipi, likexiv2, and libkdcraw. Later,
i will digiKam and DigikamImagePlugins. kipi-plugins will be done at end,
accordinly with maintatiner.

I would to post a message to Valerio about KDE 4 port : If we want to have
kipi-plugins ported to win32, the imlib2 depency need to be removed from
slideshow plugin. imlib2 is used to load and cache image files. imlib2 is
not used to render image on screen (with 2D slideshow part)

imlib2 is a problem with Win32. its depand of X11 header indeep. The
solution is to use a QT cache mechanism like the new opengl viewer plugin do
(i have not verified if th opengl slideshow part use a cache mechanism).
Perhaps a shared implementation in kipi-plugins/common folder is the best
way to prevent redondant code...

What do you think about ?

Gilles

2007/3/6, Angelo Naselli <anaselli at linux.it>:
>
> Hi,
> last week talking with Gilles, we wondered when we could
> start working to move kipi & co. and digikam to kde4.
>
> To avoid that every single extragear project branches by
> itself, shoulden't be better to create an extragear branch for
> that?
>
> WDYT?
>
> Regards,
>         Angelo
>
> _______________________________________________
> Kde-imaging mailing list
> Kde-imaging at kde.org
> https://mail.kde.org/mailman/listinfo/kde-imaging
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-imaging/attachments/20070306/008852f8/attachment.html 


More information about the Kde-imaging mailing list