digiKam

Professional Photo Management with the Power of Open Source

kipi-plugins 1.4.0 released…

by digiKam

Dear all digiKam fans and users!

digiKam team is proud to announce Kipi-plugins 1.4.0 !

kipiplugins1.4.0

kipi-plugins tarball can be downloaded from SourceForge at this url

See below the list of new features and bugs-fix coming with this release:

BUGFIXES FROM KDE BUGZILLA:

001 ==> IpodExport : 240469 : IpodExport fails to build with glib >= 2.25.
002 ==> MetadataEdit : 242624 : Wrong IPTC hyperlink.
003 ==> General : 239841 : I18n bug - missing extraction of messages in expoblending, flickrexport, metadataedit, …
004 ==> GPSSync : 246266 : Search for location when adding geo coordinates.
005 ==> PicasaWebExport : 247106 : Google picassa plugin does not work anymore since google changed parts of the interface.
006 ==> GPSSync : 246897 : GPSSync bad coordinate rounding.

Pixelpipe

I mentioned it before, I think this would be a huge gain for the kipi-plugins package. Wish submitted here: https://bugs.kde.org/show_bug.cgi?id=234726

Ask any person with the Nokia N900 and he can probably explain why this would be useful. Actually I got intrigued enough that I asked Pixelpipe for a developer key and are currently compiling Digikam. I am 99% sure I wont get anywhere since I am quite useless as a programmer though, just wanted to see if I can understand how you write the plugins and such.. You have any tutorials to recommend?

kipi-plugins dng converter with canon cr2

I use the current 1.4.0 version of kipi-plugins. This is a problem on the dng converter. I converted a lot cr2 to dng. Camera is one canon t1i 500d. All are now broken. The colours are wrong.
How i fix this? On travel i not have space on keep all cr2. I only have the broken dng now.

The red tint should be gone

The red tint should be gone with libkdcraw from KDE 4.5.1. But I also see the exif markernotes broken and have currently no clue why. Dng files from Nikon images are fine though.

upload progress bar?

Does the upload progress bar finally show progress within each file? That (and a kb/s indicator) would be enough reason for me to switch back from KFlickr…

Hello, i want to install

Hello,

i want to install kipi-plugins under kde 4.5.1 but it doesn’t work.
Follow error message it is shown.

But how can i install kipi-plugins?
i couldn’t find infos about libkipi.


– WARNING: you are using the obsolete ‘PKGCONFIG’ macro use FindPkgConfig
– PKGCONFIG() indicates that libkipi is not installed (install the package which contains libkipi.pc if you want to support this feature)
CMake Error at /usr/share/kde4/apps/cmake/modules/FindKipi.cmake:90 (message):
Could NOT find libkipi header files
Call Stack (most recent call first):
CMakeLists.txt:117 (FIND_PACKAGE)

– Configuring incomplete, errors occurred!

DigiKam progress…

Thanks for the new version! DigiKam development progress does increase very quick. New versions are released even quicker than it was before (before 1.2.0 version). The 1.2.0 was great for me and then I’ve upgraded to 1.3.0… Now I’m going to check if 1.4.0 is at least as stable as 1.2.0.

Window-Borders

I’m excited to try out the new version!
This may be a bit off topic, but I couldn’t figure it out by myself: how do I obtain that dark window-borders when using a dark theme? - is there a way to have only for digikam-windows a dark border?
cheers,
Heiko

Please remove libs from kdegraphics and make independant

Hi Digikam Team

I have a very stable KDE 4.4.5 running on Fedora 12 and I am forced to use Digikam 1.2.0/Kipi plugins 1.2.0…

Fedora 13 users also have the same problem - namely the kdegraphics/libs which aren’t actually KDE version specific are tied to the KDE version through the kdegraphics dependancies.

Neither fedora nor rpmfusion are supporting Digikam 1.3.0 or 1.40 on Fedora 12 or Fedora 13. Arghh!!!

Please remove these libs from KDE SC and make an independant libary package so that all users can enjoy the latest digikam releases by installing from repos..

facebook plugin permissions

I think facebook plugin needs to ask for additional permission to access photos, cause at the moment it can only access the profile pictures album.
FB has recently furtherly segmented the amount of permissions to request when accessing users’ photo albums.