[Kde-imaging] Kipi plugin

todd rme toddrme2178 at gmail.com
Tue Aug 14 11:57:32 UTC 2012


On Tue, Aug 14, 2012 at 12:14 PM, Dmitry Ashkadov
<dmitry.ashkadov at gmail.com> wrote:
> 14.08.2012 13:02, Gilles Caulier пишет:
>
>> No. there is no plan to add openJPEG dependency to kipi-plugins (this
>> is why we use IM to limit dependency)
>>
>> But in digiKam core, where we have another batch process toll (Batch
>> Queue Manager), which is not shared with other KIPI host application,
>> we use a core JPEG2000 loader currently based on Jasper lib. We want
>> to port it to openJPEG.
>>
>> BQM tool from digiKam core is able to do the same task than KIPI batch
>> tool (in fact it must replace it). It miss some features not yet
>> implemented to disable KIPI batch tool.
>>
>> If you is interrested to port digiKam JPEG2000 loader from Japser to
>> OpenJPEG, let's me hear. Code is here :
>>
>>
>> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/dimg/loaders/jp2kloader.cpp
>>
>> Gilles Caulier
>
> Interesting... But I never used digiKam. gwenview is sufficient for me. Do
> you know why KDE uses jasper? It can open only simple jp2 and openjpeg seems
> to be more advanced. KDE applications open jp2 very slow. How digiKam opens
> jp2 files?
> I need a tool for batch converting jpg to jp2 with saving metainfo (exif).
> Maybe it's time to try digiKam...

What about implementing openjpeg support in IM?

-Todd


More information about the Kde-imaging mailing list