52

Hello!

I think that saving desktop's plasmoid's configuration would be much easier and more organized if the configuration of each plasmoid were written in its own configuration file. Thus, instead of having plasma-desktop-appletsrc file with stored configuration of all desktop's plasmoid, we would have plasma-desktop-appletsrc folder which will contain a lot of configuration files - each one for each plasmoid.

This would enable configuration synchronization of some plasmoids among different computers.

The idea has been triggered by a thread in which is discussed the possibility of synchronizing Notes plasmoid's contents among different computers in local network.

Yes. This could also make it possible to backup individual plasmoid information I think... right?

nerdopolis wrote:Yes. This could also make it possible to backup individual plasmoid information I think... right?

Yes.

And it would make .kde/share/config folder much cleaner and tidier.

I even think this would make KDE plasma code cleaner and tidier because the plasmoid configuration parsing algorithm would be simpler (maybe even faster). Correct me if I'm wrong.

+1
Also, if something goes wrong with one plasmoid you can delete one file to restore default values, which is quite different to find the right line on a big file...

I was already forgot that plasmarc included all the plasma desktop configurations and plasma widgets configurations.

As too many times I have got in the problems when one official widget has started to act wrong way and caused plasma desktop to crash. Thats why I have needed to delete whole plasmarc file instead finding the problematic widget from it. And so on my configuration has gone totally from different desktops.

We really would need different folders for every virtual desktop and every activity. And then moving a widget from activity/desktop to another would be simple as moving the that specific widget config file to another folder.

And in case someone wants same widget setup as what we have, we can just compress the wanted configs and told them to extract them to correct place.

Fri13 wrote:We really would need different folders for every virtual desktop and every activity. And then moving a widget from activity/desktop to another would be simple as moving the that specific widget config file to another folder.

And in case someone wants same widget setup as what we have, we can just compress the wanted configs and told them to extract them to correct place.

Or more simply: just build some simliks to the files: this way you can have the same plasmoid with the same config on all the activities.

RGB wrote:
Or more simply: just build some simliks to the files: this way you can have the same plasmoid with the same config on all the activities.

Yes if we would want same activity with same settings on different activities.

But not all widgets should be having same configs. Like having a same folder view on all activities ruines the whole purpose of them. But symlinking the activity file to other folders would be like sharing them to other activities.