CONTEXT ------- Folder Color is a way to change quickly change the colour of folders: http://foldercolor.tuxfamily.org/ There is an extension also for Dolphin: https://github.com/jsmitar/dolphin-folder-color A few themes have support for such large folder colours, including all "special" folders that colourised, see e.g. Papirus: https://github.com/PapirusDevelopmentTeam/papirus-icon-theme FEATURE INTEREST ---------------- Having access to such large panel of colours, including all the "special" (image, document, etc.) is extremely nice to set up a more mnesic-friendly hierarchy were typical folders (and folder structures) can be easily muscle-memorised using a combination of special icon and colour to easily spot each folder. It vastly increases the possibilities for the user to set up such easy-to-spot folders, while current Breeze is only limited to EITHER special folders OR colours. IMPLEMENTATION -------------- I am in no way expert in how Breeze works, but as far as I understand, I believe this feature could be relatively easy to implement. Breeze can be made able to dynamically apply colours to folders: https://store.kde.org/p/1160457/ As, for example, Papirus does with a script to generate the folder icons it ships to be compatible with Color Folder: https://github.com/PapirusDevelopmentTeam/papirus-folders#script-usage CAVEATS ------- To be sure, I am not proposing Breeze to follow Color Folder, nor Dolphin to implement "dolphin-folder-color" by default (though both would be nice, of course). My main point here is more humbly to extend the folder colours to match e.g. Papirus extant in variety.
As a global thing, this would be fixed by fixing Bug 395569; marking as a duplicate of that. On a per-folder basis, you can already change the colors to whatever you want: Right-click on folder > Properties > click on icon > choose new icon. Among those icons are colored folder icons that you can use. *** This bug has been marked as a duplicate of bug 395569 ***
I was not clear enough it seems. I did not mean for this to be a global, as Rainbow Folders are, so it is a per-folder basis indeed. As such, I don't think this bug is a duplicate of #395569 (although the two subjects are technologically related I believe, since the existence of Rainbow Folders means it's possible to generate coloured icons automatically relatively easily). I know there are coloured folders icons in Breeze, but what is missing are coloured "special" folders. Maybe an example will be clearer. What I mean is that Breeze is missing the equivalent of the following Papirus (which I am currently using) icons for example: https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/blob/master/Papirus/32x32/places/folder-deeporange-development.svg https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/blob/master/Papirus/32x32/places/folder-grey-private.svg https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/blob/master/Papirus/32x32/places/folder-bluegrey-templates.svg Having access to those icons allows me (us!) to make a "visual code", for example a colour for some folders that repeated in my hierarchy (say "script", "report", etc.) which I have to detect rapidly using a combination of such colour and their associated icons/emblems ("dev" for script and "document" for report, for example). I can then associate other colours to other kinds of folder, while still distinguishing among them using their "emblems" (by this, I mean the little icon within the folder icon). Now, I realise this might be too niche, I can accept that, I just thought the technology to generate such a wider panel of icons seem relatively easy to implement (maybe I am wrong on that), and it would be a nice extension to Breeze.
Oh I see, you want to be able to tint folders (whatever their base icon happens to be) with a color. That's tracked in a general way by Bug 37300. I'd like that too. *** This bug has been marked as a duplicate of bug 37300 ***
Yes, it would solve the core issue, although the proposal here was less elaborate: just directly ship those coloured icons. But leave the link to the duplicated bug if you want, it's sensible enough! Thank you for your time.