For a long time now we have been planning to extend the amount of information we store in the database for the next version, 0.10, which will run on KDE4. As the database is the central storage and digikam is built around it, such a move involves deep structural changes. We have done preparations, discussed on the mailing list what we want and what we need, made up documentation, and then sat down to code.
So during the last weeks I have been working on implementing the new database schema, and tonight I have merged my commits.As this is the first time that our ideas have found their way into real code that you can build and use from SVN (although you should not use digikam trunk SVN for production currently) it is time to give some insight.
I will give a short overview on digikam's history, what we have reached now and what we intend to do with all the information that we find now at hand.

For a long time now we have been planning to extend the amount of information we store in the database for the next version, 0.10, which will run on KDE4. As the database is the central storage and digikam is built around it, such a move involves deep structural changes. We have done preparations, discussed on the mailing list what we want and what we need, made up documentation, and then sat down to code.
So during the last weeks I have been working on implementing the new database schema, and tonight I have merged my commits.As this is the first time that our ideas have found their way into real code that you can build and use from SVN (although you should not use digikam trunk SVN for production currently) it is time to give some insight.
I will give a short overview on digikam's history, what we have reached now and what we intend to do with all the information that we find now at hand.

Pigment is the new name of what was KritaColor in the good old 1.6 days. With some improvements, like a cleaner API, and more shared source code, mostly thanks to templates (in 1.6, more than 60% of the code was duplicated, either directly in the library or in the various plugins).

One of the biggest drawback was color conversion. KritaColor was created to abstract color, in such way that filters, tools or any other algorithms in Krita didn't have to care about the color space of an image. And in fact, it was first conceived around the lcms library, which is a color management library which handles ICC color space, that means RGB, CMYK, LAB, grayscale,... in integer 8bit or 16bit. But Krita also supports High-Dynamic Range color space, which are mostly floating points color space in 16bit or 32bit. And unfortunately in KritaColor, when a color space was not handled by lcms, colors were first convert to LAB/Integer 16bit, but that meant losing High-Dynamic Range information, as for those color space a lot of important information is stored near 0.0 or above 1.0, information lost when converting to an integer color space, not counting the conversion from 32bit to 16bit.

Dear all digiKam fans and users!The digiKam development team is happy to release 0.9.3-beta1. The digiKam tarball can be downloaded from SourceForge as well.
(0.9.3 will probably be the last release before we will switch over to KDE4 which will see a totally revamped digiKam.)New features of the camera interface:

• The camera interface is now used to import new images into collections.
• There are new options to download pictures and delete them from the camera at the same time.
• Support of Drag & Drop to download files from camera window to album window.
• A progress bar has been added to indicate the available space in the Album Library Path

read more

Dear all digiKam fans and users!The digiKam development team is happy to release 0.9.3-beta1. The digiKam tarball can be downloaded from SourceForge as well.
(0.9.3 will probably be the last release before we will switch over to KDE4 which will see a totally revamped digiKam.)New features of the camera interface:

• The camera interface is now used to import new images into collections.
• There are
  

Today marks a big achievement in the development of Scribus 1.3.5. As of now, we no longer use Qt3 or its support classes. YAY. A big job - one that started out as very simple but right at the end took awhile to get finalised. Its a nice feeling to have that sorted and now [...]

This week end, the team have voted to choose the splashscreens used with next release. You can seen the pictures below:

digiKam 0.9.3 (KDE3) : Laurenz Gamper



Showfoto 0.7.0 (KDE3) : Joel Koop

read more

This week end, the team have voted to choose the splashscreens used with next release. You can seen the pictures below:

digiKam 0.9.3 (KDE3) : Laurenz Gamper



Showfoto 0.7.0 (KDE3) : Joel Koop

Recently, i redesigned the camera interface to be more homogenous with the rest of digiKam (album view, light table and image editor)



The old implementation used a simple dialog to host camera interface contents. This way been an huge limitation to add new options for the future. Also, the dialog layout been not optimum.

Now, we use a status bar, a tool bar and a standard menu. On status bar, a widget provide a speed way to change thumbs size. Also, this version is able to show XMP metadata.