<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Saturday 14 February 2009 09:07:54 Gilles Caulier wrote:<br>
> 1/ All export plugins with the same interface : Flickr and PicasaWeb need<br>
> to be redisigned from GUI point. <br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Agreed. We could probably make them more consistent as we move them to same ground.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> 2/ When gui is done, a reflection to group all export plugins to a same plugin must be done. <br>
> 3/ After that, we must study a way to integrate gui in kipi hosts, typipically in digiKam, remote<br>
> folder view in left sidebar, and plugin settings view on the right sidebar.<br>
> icon view from the middle must host remote folder view content. libkipi<br>
> must be adapted for that.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>You mean like integrating plugins into main window of KIPI host?<br>
Personally, for import/export plugins it is important to be able to do operation in background, as upload/download can take some time. Currently the export dialog block main KIPI application and this makes it harder to use.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
Luka</p></body></html>