[digiKam-users] Gimp, Kimageformats, Digikam, sun is shining...

[Gilles Caulier]

Bad news : KDE frameworks KF5 version 5.55 require Qt 5.10 at least to
compile.
The Linux AppImage bundle use Qt 5.9.7 LTS. KF5 5.55 do not compile with
this version (i tried to hack).

So i updated at least to KF5 5.54 with is the last version compatible with
Qt 5.9.7 LTS.

This is another point that i hate to seen KDE not compatible with the Qt
long time support version. Passing to Qt 5.11 introduce regression and i
don't want to pass to Qt 5.12 until the LTS is declared by Qt team.

Including new Qt version in AppImage is complicated and require time. I
want to do it for the moment.

And i want to not talk about MAcOS support where Qt is only compatible with
more recent Apple SDK. So if we use Qt 5.12 in OSX package, it will be only
compatible with more recent version of MAcOS. The backward compatibility is
limited.

Funny, the only bundle which use Qt 5.12, and which is compiled with KF5
5.55, is... the windows installer. Thanks MXE cross compiler team which
support well last Qt version.

To resume : only the Windows installer of digiKam 6.1.0 has KImageFormat
framework with last XCF support...

Gilles Caulier

Le ven. 15 févr. 2019 à 14:06, Gilles Caulier <caulier.gilles at gmail.com> a
écrit :

> This week end, i will rebuild all bundles with KF5 5.55 and see where is
> the problem.
>
> I fear, in fact that we need later to do a XCF image loader as well in
> digiKam core, to not depend of KimageFormats, which is not well
> maintained...
>
> Perhaps the idea is to extend the plugin loader in digiKam 6.1.0 to permit
> to  write image loaders as plugins for better flexibility.
>
> Gilles Caulier
>
> Le ven. 15 févr. 2019 à 11:32, <leoutation at gmx.fr> a écrit :
>
>> On 1/30/19 2:28 PM, Gilles Caulier wrote:
>> > Right,
>> >
>> > Depending how the implementation progress, this will be available in
>> > next KF5 framework release.
>> >
>> > This want mean too, that i need to update the KF5 version to use in all
>> > bundles, without to see any side effects.
>> > KF5 is huge and a small change can introduce a dysfunction into a large
>> > application as digiKam, even if we still to use 15% of KF5.
>> >
>> > Remember that KF5 inter-dependencies between each components still
>> > important. This is a real problem, for ex, if we want to use a
>> KTextEdit
>> > widget with spell checking
>> > feature, this explode the needs to compile. This is why KTextEdit is
>> > banned for digiKam for the moment (we needs to wait a pure Qt5
>> > implementation in QTextEdit).
>> Hi
>> Some days ago, kimageformats was upgraded to last 5.55 in Arch. I
>> recompiled digikam-git. Same issue, gimp-2.10 .xcf thumbnails are not
>> displayed in digikam...
>>
>>
>> >
>> > Gilles Caulier
>> >
>> > Le mer. 30 janv. 2019 à 14:20, <leoutation at gmx.fr
>> > <mailto:leoutation at gmx.fr>> a écrit :
>> >
>> >     Hi
>> >     Good news for Digikam and Gimp users, I see a lot of work on
>> >     kimageformats to solve .xcf issue :)
>> >     https://cgit.kde.org/kimageformats.git/log/?qt=grep&q=xcf
>> >
>> >     --
>> >     Maderios
>> >
>>
>>
>> --
>> Maderios
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190219/d24c1a1f/attachment.html>