[Kde-imaging] Getting started with kipiplugins

[Gilles Caulier]

Most of documentation is in libkipi >= 2.0.0 release.

http://api.kde.org/4.x-api/kdegraphics-apidocs/libs/libkipi/libkipi/html/index.html

Gilles Caulier


2013/6/19 Kevin Dalley <kevin at kelphead.org>

> Thanks. Built in a separate directory and installed, kxmlkipicmd can find
> the kipi plugins, though it isn't obvious what to do with the plugins. That
> may be part of the issue where the program isn't currently working.
>
> If I can understand what is supposed to happen, I can document this a bit
> for the future.
>
> Is there documentation for how to write a kipi plugin. I see the doxygen
> output, but there doesn't seem to be a starting point. Of course, I can
> modify other plugins, start with hello world, and move on from there.
>
>
> On 06/19/2013 12:13 PM, Michael G. Hansen wrote:
>
>> Hi Kevin,
>>
>> On 06/19/2013 12:45 AM, Kevin Dalley wrote:
>>
>>> I admit that I'm a bit lost.
>>> I don't see clear instructions and building and testing kipi plugins.
>>>
>>
>> There are some instructions here:
>>
>> http://www.digikam.org/**download/GIT<http://www.digikam.org/download/GIT>
>>
>>  I checked out digikam from git.
>>>
>>> Ran:
>>> cmake . -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON
>>> -DCMAKE_BUILD_TYPE=Debian -DDIGIKAMSC_USE_PRIVATE_**KDEGRAPHICS=ON
>>> -DENABLE_LCMS2=ON -DKDE4_BUILD_TESTS=on -DENABLE_PRIVATE_KDEGRAPHICS=**
>>> ON
>>>
>>
>> It is recommended to use a separate build directory for building, just
>> create a subdirectory next to the source directory and build there. This
>> has the advantage that you can easily delete a build when you want to
>> start over, and also does not mess up your source.
>>
>>  compiled.
>>>
>>> copied kxmlkipicmd_defaultui.rc to $HOME/.kde/share/apps/**kxmlkipicmd
>>>
>>> Ran:
>>>   ./kxmlkipicmd --selectedimages /home/kevin/tmp/4db62b8ab6cfd.**jpg
>>>
>>>
>>> No kipi plugins were found, my installed version of kipi is newer than
>>> the source code version.
>>>
>>
>> Strangely this program is not working on my system right now, either.
>>
>> However, as far as I know, loading kipi-plugins requires them to be in a
>> kde plugin directory. I usually install self-compiled stuff to
>> /usr/local and then on a terminal start:
>>
>> export KDEDIRS=/usr/local
>> kdeinit4
>>
>> This way, the plugins are loaded from /usr/local and not /usr. Note that
>> this kdeinit4 started here may interfere with other applications
>> running, so a normally started digikam may also start loading the
>> self-compiled plugins...
>>
>> Best regards,
>>
>> Michael
>>
>>
>>> How can I specify directories for the kipi plugins. I want to use them
>>> built in place.
>>>
>>> I had hoped that various README files would start me out with the
>>> correct steps.
>>>
>>> ______________________________**_________________
>>> Kde-imaging mailing list
>>> Kde-imaging at kde.org
>>> https://mail.kde.org/mailman/**listinfo/kde-imaging<https://mail.kde.org/mailman/listinfo/kde-imaging>
>>>
>>>
>> ______________________________**_________________
>> Kde-imaging mailing list
>> Kde-imaging at kde.org
>> https://mail.kde.org/mailman/**listinfo/kde-imaging<https://mail.kde.org/mailman/listinfo/kde-imaging>
>>
>>
> ______________________________**_________________
> Kde-imaging mailing list
> Kde-imaging at kde.org
> https://mail.kde.org/mailman/**listinfo/kde-imaging<https://mail.kde.org/mailman/listinfo/kde-imaging>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-imaging/attachments/20130620/861573e0/attachment.html>