Bug 412906

Summary: Feature to save current layout as a new Global Theme package
Product: [Applications] systemsettings Reporter: Nate Graham <nate>
Component: kcm_lookandfeelAssignee: Plasma Bugs List <plasma-bugs>
Status: CONFIRMED ---    
Severity: wishlist CC: kde, lv215bd5, mv.horizonv, postix
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Nate Graham 2019-10-13 13:58:51 UTC
This came up surrounding the discussion about https://phabricator.kde.org/D24223. It turns out that some people are hesitant to change global theme packages because if they don't like the new one, returning to a customized layout is annoying and time-consuming.

I think there's merit to this observation and I have had the same hesitancy myself. I'd like to propose that the KCM gain a feature to save the current layout as a new global theme package which would then appear in the KCM.

This would not only allow people to easily restore their prior settings if they don't like a particular global theme that they're trying, but it would also make it easily for people to export and share their own settings in the store.
Comment 1 David Edmundson 2019-10-13 16:54:29 UTC
See lookandfeelexplorer

Also, there's a task at T11746 which has a different proposed implementation of doing things which I think makes a lot more sense. Lets not split the discussion especially when this only represents one side of the comments.
Comment 2 postix 2019-10-13 17:56:58 UTC
> See lookandfeelexplorer
There's no way to save the current theme settings as a new global theme package, isn't it? What exactly should I look for?

> Also, there's a task at T11746 
I am not sure, why both should be mutual exclusive.
Comment 3 Nate Graham 2019-10-15 21:25:51 UTC
(In reply to David Edmundson from comment #1)
> See lookandfeelexplorer
As Postix implies, this doesn't really satisfy the request here. It doesn't actually have a "save current settings as a new theme" feature (or at least, not that I can find).

> Also, there's a task at T11746 which has a different proposed implementation
> of doing things which I think makes a lot more sense. Lets not split the
> discussion especially when this only represents one side of the comments.
Assuming you're referring to https://phabricator.kde.org/T11746#202374, I can accept that, and we can keep the conversation there.
Comment 4 David Edmundson 2019-10-15 22:21:19 UTC
It's maybe a bit obscure.

new theme -> fill in the details -> layout from current plasma setup
Comment 5 Nate Graham 2019-10-15 22:22:25 UTC
Thanks! That is quite obscure and could do with some UI polish IMO. Still it's there, so that's nice.
Comment 6 postix 2019-10-16 07:19:40 UTC
> lookandfeelexplorer -> new theme 

Sorry, I still don't find it. :-(
Can you please point me to the lookandfeelexplorer, maybe show me a screenshot? 
The only buttons I find at the look and feel section are for downloading a new theme or to install a theme by a file.
Comment 7 Christoph Feck 2019-10-16 08:30:55 UTC
You need to install 'plasma-sdk'.

https://cgit.kde.org/plasma-sdk.git/tree/
Comment 8 postix 2019-10-16 08:41:38 UTC
Thanks! Unfortunately it was not preinstalled on my distro (Manjaro) and so I could not find it. Nevertheless I would have expected in a different place, namely in the system settings, anyway.

That's why I suggest to integrate it into the system settings, to overhaul its UI and to add an option to only create a theme for a local installation (currently an email and website is required to create a new theme for example). 

But maybe let's discuss it here: https://phabricator.kde.org/T11746 :)
Comment 9 Nate Graham 2021-06-08 21:24:15 UTC
*** Bug 437963 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2021-06-08 21:25:25 UTC
Work on https://phabricator.kde.org/T11746 has stalled; re-opening this since another person has asked for it as well and I still think it's a reasonable request. :)
Comment 11 Nate Graham 2022-10-10 21:54:15 UTC
*** Bug 460210 has been marked as a duplicate of this bug. ***