Bug 468499 - Make gwenview browsing UX compatible with dolphin / tighter integration
Summary: Make gwenview browsing UX compatible with dolphin / tighter integration
Status: REPORTED
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 23.03.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-14 10:48 UTC by Reuben
Modified: 2023-04-14 10:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Reuben 2023-04-14 10:48:37 UTC
SUMMARY

This may not be a gwenview issue, but filing here as a start.

The experience of double clicking on an image in dolphin, and then browsing images that are side by side with it, is jarring. I would bet that this is how 90% of kde users encounter gwenview, 90% of the time. 

Issues:

a) Sort order not preserved between dolphin and gwenview.
b) When you press escape / close the full image, you end up back in gwenview's browser, not dolphin. This is highly confusing.
c) If you browsed through a few dozen images, when you go back to dolphin you are located where you originally invoked gwenview, not where you finished.

I also think gwenview's edit tools sidebar should show by default (since, while the button is there on the toolbar, it's not completely discoverable), and that in addition it should have an "edit with" cta, listing whatever image editing tools are installed. It could even always feature KDE suite tools (krita, ...) to drive installation/usage, if not already installed. Rationale for the latter is that the context menu/"open with" submenu is hard to find, and contains irrelevant entries anyway (chrome, imagemagick?!!)