<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>I am wondering what darktable, GIMP and other projects relying on exiv2 going to do...</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: NeiNei <neinei@gmx.net> </div><div>Date: 2017-04-28 7:31 AM (GMT-07:00) </div><div>To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org> </div><div>Subject: Re: Exiv2 bug reports </div><div><br></div></div>Hi there,<br><br>the long awaited release of Exiv2 v0.26 should be released today <br>according to http://dev.exiv2.org/boards/3/topics/2830<br>However, I do not know wether or how it will change the situation for <br>DigiKam.<br>As far as I understood Gilles thoroughly checks for alternatives in <br>order to ensure a working, evolving and reliable metadata editor for <br>DigiKam.<br><br>NeiNei<br><br>On 25.04.2017 22:38, Gilles Caulier wrote:<br>> Hi Marcel,<br>><br>> This is a more simple solution, always based to C++ with ExifTool :<br>><br>> http://owl.phy.queensu.ca/~phil/cpp_exiftool/<br>><br>> This basis o this interface must do the job for all common call done by<br>> digiKam in Exiv2. Of course the tags syntax must be ported from Exiv2 to<br>> ExifTool.<br>><br>> The second problem is the Perl stuff.. Here, also there is a solution to<br>> provide a machine compiled Exiftool in digiKam as a ressource. This will<br>> improve very well the performances. As i can see, LightRoom use this<br>> solution in background (yes I see Exiftool used while testing).<br>><br>> ExifTool.exe precompiled already exists for Windows for ex. So it's<br>> possible to do for all platforms.<br>><br>> There is some reponse about this topic here :<br>><br>> http://stackoverflow.com/questions/1237286/how-can-i-compile-my-perl-script-so-it-can-be-executed-on-systems-without-perl-i<br>><br>> Gilles<br>><br>> 2017-04-25 12:53 GMT+02:00 Marcel Wiesweg <marcel.wiesweg@gmx.de<br>> <mailto:marcel.wiesweg@gmx.de>>:<br>><br>> Gilles, just my viewpoint from someone who used to code a little bit<br>> at free<br>> time:<br>><br>> Using an out-of-process solution like exiftool has the bonus that<br>> crashes dont<br>> crash digikam.<br>> It has the drawback of performance; metadata reading is quite<br>> expensive in<br>> some situations. Inter-process communication can be a pain.<br>><br>> If it's based on Perl, this can be a problem for easy deploying on other<br>> platforms. And I dont know if you speak Perl really well.<br>><br>> We have invested greatly in our exiv2-based infrastructure. There<br>> are hundreds<br>> of bug fixes and problem solutions in the code that depends directly<br>> on exiv2<br>> via C++.<br>><br>> In order to port all this logic, and to optimize IPC, you'd need<br>> custom parts<br>> in the other process - probably written in Perl? - that need to be<br>> developed<br>> by digikam and kept up to date with digikam.<br>><br>> In the end, make a calculation if all this work is really worth it.<br>><br>><br>> Marcel<br>><br>> ><br>> > I seriously plan Exiftool migration. It will take a while but at least<br>> > Exiftool is alive and constructive... I'm in contact with Exiftool<br>> team...<br>> ><br>> > Voilà. This is just the viewpoint from an human who code a little<br>> bit at<br>> > free time...<br>><br>><br><br></body></html>