https://bugs.kde.org/show_bug.cgi?id=512375
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from [email protected] --- >It would just be much nicer if it could use upstream gmic-qt I do the upstream and i validate the usage with digiKam at each Gmic-Qt stable release. >or make it possible to have just one gmic-qt that can be built for >gimp/krita/digikam/... No, as we patch the GMicQt API to be compatible with digiKam API. The original way to communicate between the host application and the plugin is complex, slow, and not necessary (it use a socket pipeline). We proposed the digiKam way but it have been refused by GMicQt team in the past. So my solution works as expected under Linux, macOS, and Windows (it's not the case with the original solution). Another point: we provide 3 GmicQt plugin for digiKam : icon-view, BQM, and editor. The original solution only support the editor plugin. If you are curious about my patches against the original implementation from GmicQt look here : https://github.com/cgilles/digikam-gmic-qt -- You are receiving this mail because: You are watching all bug changes.
