[Kde-imaging] RFC: how to identify an action from some KIPI plugin

[Angelo Naselli]

> Hi Angelo,
> I believe that the version of KIPI plugins doesn't matter at all. I have
> no idea about what version the original submitter uses, but I've
> reproduced the issue with Gentoo's libkipi-0.1.4 and
> kipi-plugins-0.1.0_rc1. That said, this version information isn't
> relevant at all, AFAIK.
It is, you've just said you're using kipi-plugins (note kipi-plugins not likipi)
0.1.0-rc1 that bug has been fixed into version 0.1.3 beta1 as written into 
the NEWS file. 
I believe with gentoo it's easy to backport (valerio could help you in that :) )
the new kipi-plugins, but since you need libkdcraw libkexiv2 and new libkipi 
as well i cannot force you tu update your system, but if you can at least 
download and test the svn version (kde 3 branch)
you can really say if it is still valid or not.

> > but from NEWS file i found out the following
> > 006 ==> 119537 : JPEGLossLess : Exif width and height are not corrected after lossless rotation.
> > http://bugs.kde.org/show_bug.cgi?id=119537
> > seems to say your problem is fixed IIUC. And that should mean the bug you're
> > referring to is fixed and duplicated of bug# 119537.
> 
> Unless I'm missing something important, this bugreport is totally
> irrelevant. Perhaps I wasn't clear enough, but the problem is that after
>  invoking that plugin, the already rotated image is rotated by KPA once
> again. This won't affect any other application, problem is that KPA
> fails to recognize that the plugin actually rotated the image.
hmm, IIUC your last, you said the problem is in the exif value that still
remains normal, after rotation. In such a condition KPA doesn't see
the file has been rotated, am i wrong?
Quoting reporter of bug 119537, "After I rotate my jpeg-images 90 or 270 degrees losslessly with 
kipi-plugins Exif-data in images are left to old values. They should be switched.",
seems to say the same...

> 
> > According to plugin_jpeglossless.cpp there are more than one actions
> > and related action name but I'm not the jpeglossless 
> > plugin guru :)
> 
> Indeed, that's why I want to identify this action and not all actions
> from that plugin. Note that the unportable part of my ugly patch is the
> blurb that is trying to identify the plugin, not the action.
To be honest i haven't seen your patch yet, leaving it to Gilles :)
 
> > Sure it would, libkipi should (*will*) change in incoming kde 4, so
> > any help, suggestions, patches are welcome ;)
> 
> Provide a unique name for both each plugin and each action. The
> applications should be able to identify each KAction instance alone, so
> perhaps its naming of "pluginName/actionName" is reasonable.
Col made a wiki page in which we can discuss kipi api changing proposal,
please add your comments there:  
http://wiki.kde.org/tiki-index.php?page=Kipi+API+Rework

Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-imaging/attachments/20070808/e998c128/attachment.pgp