https://bugs.kde.org/show_bug.cgi?id=368001

            Bug ID: 368001
           Summary: plugins menu entry empty without kipi-plugins
           Product: gwenview
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: gwenview-bugs-n...@kde.org
          Reporter: sit...@kde.org
                CC: myr...@kde.org

gwenview can be built with libkipi (kde applications), if kipi-plugins
(digikam) aren't installed there won't be anything to list though.

when built with libkipi a 'Plugins' menu entry becomes available, without
kipi-plugins however this entry has no nodes making it look broken.



Reproducible: Always



Expected Results:  
3 ways to solve this come to mind

# No plugins = No menu

When no plugins are available the menu doesn't get shown. So the visibility
condition changes from (builtWithLibKipi) to (builtWithLibKipi &&
!pluginsList.isEmpty). With this a user is expected to know that kipi-plugins
should be installed to gain additional features. Alternatively installing
digikam will also enhance gwenview's capabilities.

# Custom install rigging

When no plugins are available a "fake" menu entry is created which employs a
simple addon-install mechanic as seen in drkonqi to let distributions install
kipi-plugins on demand. Namely this would call an executable that is meant to
install kipi-plugins through whatever way necessary exitign either 0 or !0 from
which gwenview can deduce whether or not it needs to reload the plugin list.

# Install through appstream

Alternatively we could solve this through appstream by having kipi-plugins
provide a "global" metainfo file for "standard kipi plugins" or something
alike, from gwenview we still have a fake menu entry but instead of calling out
to some custom code it simply runs appstream://org.kde.kipi-plugins.desktop,
which will bring up the desktop's software center to install kipi plugins.

# We always want them

kipi-plugins should be considered as a runtime requirement, to communicate this
to distributors a runtime dependency information should be included in
gwenview's cmake output.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to