About
What is KIPI?
One of the nicest things about KDE Photo Management Programs like "digiKam", "KPhotoAlbum", "GwenView" and "ShowImg" is how easily its functionality can be extended, by using plugins. Plugins can manipulate image files in almost any way that users can. Their advantage is that it is much easier to add a capability to the host application by writing a small plugin than by modifying the host application core. Many valuable plugins have C++ source code that only comes to 100-200 lines or so.
Kipi plugins are additional functions for the KDE Images Managment Host Programs. They can add extra menus and shortcuts, and extend the host programs features. You can install as many or as few as you like, from within host programs.
More information on using and enabling the plugins you want is available in the host program handbook.
Plugins
Browse plugins by left menu
How can I contribute?
Mailing List
If you want to implement a new plugin, add Kipi support to a new graphic application, or just speak about it, you're welcome to join the kde-imaging@kde.org mailing list.
The mailing-list archives can be consulted at this url.
IRC Channel
You can meet KIPI developers on #kde-imaging IRC channel (Freenode).
Bug reports and Wishes
For bug reports and wishes, please use the KDE Bug Tracking System.
Download
Released versions
Source
- kipi-plugins-0.1.5.tar.bz2
- libkexif-0.2.5.tar.bz2
- libkexiv2-0.1.7.tar.bz2
- libkipi-0.1.6.tar.bz2
- libkdcraw-0.1.4.tar.bz2
Mandriva 2006
By Angelo Naselli
- kipi-plugins-0.1.2-0.1.20060mdk.i586.rpm
- libkexif0-0.2.4-0.1.20060mdk.i586.rpm
- libkexif0-devel-0.2.4-0.1.20060mdk.i586.rpm
- libkipi0-0.1.4-0.1.20060mdk.i586.rpm
- libkipi0-devel-0.1.4-0.1.20060mdk.i586.rpm
Slackware 10.2
By Mark Tucker
SuSE 10.0
Links2Linux.de has KIPI packages for SuSE:
Get from SVN
If you want to try the latest development version, you need to grab Kipi from the KDE SVN. It's located in the kdeextragear-libs module.
You can either get the source code using SVN like this:
% cd libs
% svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin
If you want to test a single module, kipi-plugins for instance, you can:
% cd libs
% svn co svn://anonsvn.kde.org/home/kde/branches/extragear/kde3/libs/kipi-plugins
% svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin
The current KDE SVN tarballs of the host applications which support Kipi can be downloaded from this link.
Install from sources
Kipi must be compiled and installed before compiling the host applications.
Compiling libKipi
The dependencies are:
- Common:
- AutoConf >= 2.5
- AutoMake >= 1.6.0
- KDE 3.x
- libkexif:
- libexif >= 0.5.7
- kipi-plugins:
- gphoto2 2.x
- imlib2 >= 1.1.0
- ImageMagick >= 5.5.4
- MJPEGTools >= 1.6.0
- dcRAW >= 5.02
The procedure is listed below:
export KDEDIR=KDE_installation_dir_on_your_system
make -f Makefile.cvs
./configure --enable-debug=full
make
su
make install
Enabling Kipi support in host applications
The host application compilation options to use Kipi are:
- digiKam : no option. Native support.
- KimDaBa : use --enable-libkipi option with the ./configure script in kdeextragear-2 CVS module.
- ShowImg : use --enable-libkipi option with the ./configure script in kdeextragear-2 CVS module.
- Gwenview : use --enable-kipi option with the ./configure script in kdeextragear-1 CVS module.
Team
Here it is, KIPI development team: