[Digikam-users] open with external editor disappeared in recent beta

[Simon Frei]

Ok, no problem. My second question was just whether the warning should 
be modified to say
"digiKam will be compiled without desktop integration support."
instead of
"digiKam will be compiled without KDE desktop integration support."
The present might make non-KDE users think that they do not need it at 
all (it did for me).

On 29/05/16 21:58, Gilles Caulier wrote:
> No open with under Linux depend of libkio. No other alternative exists 
> yet, typically with Qt5 desktop integration. I hope that it will be 
> fixed in Qt later
>
> Gilles Caulier
>
> 2016-05-29 21:50 GMT+02:00 Simon Frei <freisim93 at gmail.com 
> <mailto:freisim93 at gmail.com>>:
>
>     I think you misunderstood me: I have all other optional widgets
>     installed and they are found. Only for the last compilation I
>     uninstalled the libkio (and only it) dependency, because I thought
>     I do not need it (I do not use KDE). However now you told me, that
>     the feature "open with" is removed when libkio is not found. So
>     now after reinstallation of libkio and recompilation of digikam
>     the "open with" feature is back. If "open with" is indeed possible
>     without libkio, it would be great if it was included also if
>     libkio is missing.
>
>
>     On 29/05/16 21:08, Gilles Caulier wrote:
>>     The KIO dependency do not want mean to drop this feature if non
>>     KDE desktop is used under Linux. At compile time we don't have a
>>     way to check if application will run under Gnome or KDE for ex.
>>     At run time yes, but for this feature, it's not used.
>>
>>     Typically, the KIO dependency is checked to activate or not the
>>     feature. But KIO as 2 possible way to be compiled :
>>
>>     - The core KIO to access on remote computer with different protocols
>>     - With widgets as optional (for this feature)
>>
>>     Perhaps the widget part is not compiled on your computer through
>>     packaging.
>>
>>     Gilles Caulier
>>
>>
>>
>>     2016-05-29 20:22 GMT+02:00 Simon Frei <freisim93 at gmail.com
>>     <mailto:freisim93 at gmail.com>>:
>>
>>         Hi Gilles,
>>
>>         That is the reason. I read the diffs since my last pull and
>>         there was something about kio. The following suggests that
>>         kio is only relevant together with KDE, so I removed it.
>>         Apparently it is generally needed for linux desktop
>>         integration (e.g. open with).
>>         PRINT_OPTIONAL_LIBRARY_STATUS("libkio"
>>         "https://projects.kde.org/projects/frameworks/kio"
>>         <https://projects.kde.org/projects/frameworks/kio> "(version
>>         >= ${KF5_MIN_VERSION})" "digiKam will be compiled without KDE
>>         desktop integration support." KF5KIO_FOUND)
>>         Maybe that should be adjusted?
>>         I will reinstall and recompile - thanks for your help.
>>
>>
>>
>>         On 29/05/16 06:35, Gilles Caulier wrote:
>>>         Hi,
>>>
>>>         No. This option is just optional if KIO component from KDE
>>>         is found. Typically, thsi option is only valid under Linux,
>>>         not under OSX and Windows because KIO is not able to handle
>>>         external applications with these OS. We need to use a native
>>>         solution instead.
>>>
>>>         So, the question is : What your environnement while your
>>>         recompile digiKam ? At configuration time, a details panel
>>>         give a feedback about the configuration done, especially
>>>         with desktop integration.
>>>
>>>         Best
>>>
>>>         Gilles Caulier
>>>
>>>         2016-05-29 1:36 GMT+02:00 Simon Frei <freisim93 at gmail.com
>>>         <mailto:freisim93 at gmail.com>>:
>>>
>>>             I recompiled digikam recently and now cannot find a menu
>>>             item to open a file in an external editor anymore. It
>>>             used to be possible to right click an image and select
>>>             something like open with (I do not remember the exact
>>>             name) which opened a list of image editors to choose
>>>             from, in which the image then gets opened. Has this
>>>             option been intentionally removed? Integration with
>>>             other image editors is key for me. Digikams main strenth
>>>             is image handling, as an editor, there are superior
>>>             options out there.
>>>             _______________________________________________
>>>             Digikam-users mailing list
>>>             Digikam-users at kde.org <mailto:Digikam-users at kde.org>
>>>             https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>>>
>>>
>>>
>>>         _______________________________________________
>>>         Digikam-users mailing list
>>>         Digikam-users at kde.org <mailto:Digikam-users at kde.org>
>>>         https://mail.kde.org/mailman/listinfo/digikam-users
>>
>>
>>         _______________________________________________
>>         Digikam-users mailing list
>>         Digikam-users at kde.org <mailto:Digikam-users at kde.org>
>>         https://mail.kde.org/mailman/listinfo/digikam-users
>>
>>
>>
>>
>>     _______________________________________________
>>     Digikam-users mailing list
>>     Digikam-users at kde.org <mailto:Digikam-users at kde.org>
>>     https://mail.kde.org/mailman/listinfo/digikam-users
>
>
>     _______________________________________________
>     Digikam-users mailing list
>     Digikam-users at kde.org <mailto:Digikam-users at kde.org>
>     https://mail.kde.org/mailman/listinfo/digikam-users
>
>
>
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20160529/09a5e051/attachment.html>