<br><br><div><span class="gmail_quote">2007/3/6, Angelo Naselli <<a href="mailto:anaselli@linux.it">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 16:01, marted́ 6 marzo 2007, Valerio Fuoglio (thewally) ha scritto:<br>> > I would to post a message to Valerio about KDE 4 port : If we want to have<br>> > kipi-plugins ported to win32, the imlib2 depency need to be removed from
<br>> > slideshow plugin. imlib2 is used to load and cache image files. imlib2 is<br>> > not used to render image on screen (with 2D slideshow part)<br>> ><br>> > imlib2 is a problem with Win32. its depand of X11 header indeep. The
<br>> > solution is to use a QT cache mechanism like the new opengl viewer plugin<br>> > do<br>><br>> Ok, few days ago, I've sent an implementation pf imlib2 for slideshowgl<br>> (as I've understood, it's needed by libkdcraw) to Angelo for testing. So,
<br>> if it will works, will be used only for qt3 branch.<br>... who didn't test :/<br>from my point of view if you think is ok you can release it, i haven't<br>plann aney release yet, but sure we can do another qt3 one sooner or later.
<br>><br>> Do I have understood well? Is imlib2 needed into slideshow's code by<br>> libkdcraw?</blockquote><div><br>is imlib2 is require by libkdcraw ? (:=))), well no...<br><br>remember than the libkdcraw return a QImage with the embedded preview picture from RAW file. The image data are converter to a imlib2 image container to be stored in the imlib2 cache.
<br><br>I recommend you to remove the imlib2 depency now, if you can of course... It's more clean and very easy to do. The cache implementation is already done in OpenGL viewer. Just adapt the imlib2 interface from Slideshow to use Qt implementation instead imlib2 and that all...
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">><br>Gilles?<br><br>Anyway the idea is to have a branch in which to work under kde4, but
<br>using svn it's the same working in trunk for that. Let's wait for extragear group<br>answers.</blockquote><div><br>fine. We must work like other KDE parts...<br><br>Gilles</div></div><br>