[digiKam-users] Qtweb* dependency

[Gilles Caulier]

The geolocation Map code based on Qt Web module (to display web service
map) and Marble (to display local map) is more advanced than Qt Location.
For ex, Googlemaps is not supported by Qt Location. If we switch to Qt
Location, we will left GoogleMaps support, which is a big regression.

Other point : Marble, used by digiKam, also use Qt Web module internally.
living without Qt Web module is just impossible.

Best

Gilles Caulier

Le dim. 24 nov. 2019 à 03:43, Philippe Baril Lecavalier <pbl.ltx at gmail.com>
a écrit :

> Ok. What about the library Qt Location? That sounds more like what you are
> looking for, minus the over-engineered approach to require a whole web
> browser engine to get a couple of functions.
>
> On Sat, Nov 23, 2019 at 4:41 PM Gilles Caulier <caulier.gilles at gmail.com>
> wrote:
>
>> Hi,
>>
>> Qt web module are used in digiKam to displayed map for geolocation
>> support. This feature is very important and there is no option to disable
>> geolocation support at compilation time.
>>
>> Also, We start to use this Qt web module to open session in web service
>> for import/export files with the cloud.
>>
>> Best
>>
>> Gilles Caulier
>>
>> Le mar. 19 nov. 2019 à 19:20, Philippe Baril Lecavalier <
>> pbl.ltx at gmail.com> a écrit :
>>
>>> Pardon me if the issue was raised or discussed before, I could not find
>>> any trace of it.
>>>
>>> Why is qtwebengine/qtwebkit a dependency for digikam? My main use of
>>> digikam is to fetch images from my phone or camera. I don't see the need
>>> for an entire (and not a light one!) web engine here. Gwenview doesn't call
>>> for one to display images or their metadata.
>>>
>>> The issue for me? Not interested to build the whole creepy-chrome from
>>> scratch every time an update is pushed (Gentoo here, maybe 2 hours for
>>> qtwebkit, more for qtwebengine). If I used some KDE web browser, it would
>>> make sense. But it's not the case, and so I got to build a thing that takes
>>> longer than gcc itself solely for digikam (and presumably taking more space
>>> than digikam too).
>>>
>>> Suggestion: A flag to build digikam minus whatever feature calls for a
>>> web browser engine? If the whole application is based on it, I can
>>> understand that.
>>>
>>> I am not a C++/qt developer, so I'm sorry if I can't push an actual
>>> proposal any further. If I can help with testing, it's the least I can do.
>>>
>>> Philippe Baril Lecavalier
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20191124/7be8d7f4/attachment.html>