Bug 468499

Summary:	Make gwenview browsing UX compatible with dolphin / tighter integration
Product:	[Applications] gwenview	Reporter:	Reuben <kde>
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	idontfeelcomfygivingyoumyemail
Priority:	NOR
Version First Reported In:	23.03.90
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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?!!)

Comment 1 A Linux User 2025-08-21 00:44:10 UTC

Thanks for sharing this design proposal!
A better place to do this is in the Visual Design Group chatroom, because this isn't really a bug or a discrete feature request (it's more like a bunch of feature requests all mashed together). As such it would make more sense to discuss it in a group setting where existing design choices and constraints that may not be immediately obvious can be explained, and we can go over which elements of this proposal might make sense to integrate.
Check out https://community.kde.org/Get_Involved/Design.
Thanks for understanding!

Regarding the sorting, we have:
https://bugs.kde.org/show_bug.cgi?id=466836