<br><br><div><span class="gmail_quote">2007/7/23, 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;">
> MpegEncoder<br>> PrintWizard<br>> CdArchiving<br>I don't know when but i like to be present (or try to do that by myself) for the above<br>plugins.<br>- CD-Archiving sholud change its name, i seem to remember a thread in which
<br>an English person dislike its name (Col can you point me to a good name?)<br>Moreover i don't like the label "CD" why CD? it can be also DVD but in future<br>an USB-key or any other Backup archive...<br>
Another issue I'd like to change, time allowing, is to use html-export plugin<br>instead of the old web export interface...<br>- Printwizard, in my little spare time i feel motivated to work on this and i have<br>some changes in mind so please let me know if you need it to be ported soon.
<br>- MpegEncoder, i changed something on that in past, but it is a little bit old,<br>it needs to be updated to modern technologies, but i had some feed backs<br>from people but no-one that has seriously taken it in maintainance .
<br><br>> FindImages : obsolete (for digiKam). New advanced search tool will do it in<br>> digiKam core using DB.</blockquote><div><br>In digiKam we have plan to do a big update of database content, including Haar matrix for each image to process fuzzy search.
<br> <br>Currently FindImage use a local cache in disk to store another type of image checksum. this way is too slow.<br><br>Also this plugin is not fully integrated in digiKam Album gui interface. There are few B.K.O reports about this problem.
<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;">> KameraKlient : obsolete (for digiKam). it will be never ported by digiKam
<br>> team.<br>Well I'm not happy to hear that, I can understand digikam is not interested<br>in that, but maybe kipi-plugins is, so plugins that are used by other hosts<br>should be supported anyway. </blockquote>
<div><br>In this case, others kipi hosts developpers must do this port (:=))). <br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You know digikam could also avoid slideshow,<br>but do we have to remove it for that?</blockquote><div><br>This is different. kipi slideshow use OpenGL. digiKAm slideshow tool is more simple and don't use OpenGL. This solve a problem about users who don't have openGL card can slide image as well.
<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;">I think to you as a kipi developer, once you told me "we are a team" and
<br>that should be.<br>Just a note, with old libexiv2 and digikam 0.9.1 my father could not download<br>images from his camera,</blockquote><div><br>I recommend to use last exiv2 stable when it's possible and digiKam
0.9.2 </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> but wow! he was lucky he could do that from<br>kameraklient using gwenview... so are you sure it isn't useful?
</blockquote><div><br>kameraklient is a un-maintened plugin Code source come from digiKam 0.6 release... It's a fork in fact...<br><br>Download options are more improved in digiKam camera interface.<br> </div></div>Gilles
<br>